From 2f5caaf01a701fe9e4d93918b4cd2cc9c074fb9c Mon Sep 17 00:00:00 2001
From: Izan Gil <66965250+SrIzan10@users.noreply.github.com>
Date: Wed, 8 May 2024 21:46:49 +0200
Subject: [PATCH] fix: background stretched
---
public/blog/atom.xml | 34 ++++++++++++++++++++++++++++++-
public/blog/feed.json | 11 ++++++++++
public/blog/rss.xml | 30 ++++++++++++++++++++++++++-
src/app/_css/RandomBackground.css | 3 +++
4 files changed, 76 insertions(+), 2 deletions(-)
diff --git a/public/blog/atom.xml b/public/blog/atom.xml
index 5905f09..e3ec0b7 100644
--- a/public/blog/atom.xml
+++ b/public/blog/atom.xml
@@ -2,7 +2,7 @@
This is probably the last time I'm going to make a blog. I've made a few in the past, but I've never really stuck to them. I'm hoping that this time will be different. PD: I need some help for making the blog text look good and readable, so hit me up on my Discord if you have any ideas.
This one was made entirely from scratch using React and Markdown, initially trying to use MDX, but it was a pain to set up, and it didn't end up working in the end.
I'm hoping to post about my projects, and maybe some other stuff too. I'm not sure yet, but I'll figure it out as I go along.
Anyways, thank you for reading. I hope you enjoyed my UX/UI for this one!
And, welp, that's what I just did with my github bot Automata.
Automata v1 was a real mess. We were supposed to publish a next.js website, a jobs system to make our lives easier, and a large etc.
+Now, I've been working on this for quite a while (about a year) and I felt like I wasn't going anywhere. So I just thought about it we could run the automation scripts on Github Actions, right?
+And in 4 days I got the whole thing working. I'm really proud of it.
+We send API requests to Github whenever we want to trigger a workflow, on demand, by using the webhook system and handling everything from there.
As a bonus I also added a command, so we could merge on a more controlled way, specially on larger PRs.
There were some bugs on launch.
+PORT environment variable (commit)That last one was a real pain, as I detected the bug in production, on the most important PR of the week, if not the month: the website's move to starlight docs.
+

Wow, a project with good DevEx? SIGN ME UP!
+PD: I created a next.js template with my preferred tech stack, make sure to check it out! link
]]>As once our lord and savior Terry A. Davis said, "An idiot admires complexity, a genius admires simplicity."
And, welp, that's what I just did with my github bot Automata.
Automata v1 was a real mess. We were supposed to publish a next.js website, a jobs system to make our lives easier, and a large etc.
\nNow, I've been working on this for quite a while (about a year) and I felt like I wasn't going anywhere. So I just thought about it we could run the automation scripts on Github Actions, right?
\nAnd in 4 days I got the whole thing working. I'm really proud of it.
\nWe send API requests to Github whenever we want to trigger a workflow, on demand, by using the webhook system and handling everything from there.
As a bonus I also added a command, so we could merge on a more controlled way, specially on larger PRs.
There were some bugs on launch.
\nPORT environment variable (commit)That last one was a real pain, as I detected the bug in production, on the most important PR of the week, if not the month: the website's move to starlight docs.\n

Wow, a project with good DevEx? SIGN ME UP!
\nPD: I created a next.js template with my preferred tech stack, make sure to check it out! link
\n", + "url": "https://srizan.dev/blog/5", + "title": "Releasing sern Automata v2", + "date_modified": "2024-05-08T18:46:01.405Z", + "author": { + "name": "Sr Izan", + "url": "https://srizan.dev" + } } ] } \ No newline at end of file diff --git a/public/blog/rss.xml b/public/blog/rss.xml index 80b228e..330a677 100644 --- a/public/blog/rss.xml +++ b/public/blog/rss.xml @@ -4,7 +4,7 @@This is probably the last time I'm going to make a blog. I've made a few in the past, but I've never really stuck to them. I'm hoping that this time will be different.
This one was made entirely from scratch using React and Markdown, initially trying to use MDX, but it was a pain to set up, and it didn't end up working in the end.
I'm hoping to post about my projects, and maybe some other stuff too. I'm not sure yet, but I'll figure it out as I go along.
Anyways, thank you for reading. I hope you enjoyed my UX/UI for this one!
PD: I need some help for making the blog text look good and readable, so hit me up on my Discord if you have any ideas.
+]]>Automata v1 was a real mess. We were supposed to publish a next.js website, a jobs system to make our lives easier, and a large etc.
+Now, I've been working on this for quite a while (about a year) and I felt like I wasn't going anywhere. So I just thought about it we could run the automation scripts on Github Actions, right?
+And in 4 days I got the whole thing working. I'm really proud of it.
+We send API requests to Github whenever we want to trigger a workflow, on demand, by using the webhook system and handling everything from there.
As a bonus I also added a command, so we could merge on a more controlled way, specially on larger PRs.
There were some bugs on launch.
+PORT environment variable (commit)That last one was a real pain, as I detected the bug in production, on the most important PR of the week, if not the month: the website's move to starlight docs.
+

Wow, a project with good DevEx? SIGN ME UP!
+PD: I created a next.js template with my preferred tech stack, make sure to check it out! link
]]>