Editing posts

_posts/2022-11-27-new-blog.md

@@ -1,5 +1,5 @@
 ---
-title: Wordpress, It's Not You, It's Me, Kinda
+title: New Blog Platform
 date: 2022-11-26 12:01:00 -500
 categories: [Jekyll, Blog]
 tags: [blog,github,azure,jekyll,employers]     #TAG names should always be lowercase
@@ -13,7 +13,7 @@ tags: [blog,github,azure,jekyll,employers]     #TAG names should always be lower
 
 <br>
 
-The previous blog used WordPress. Some of you are rolling your eyes. I don't blame you! Hear me out though! My reasoning for picking WordPress was ease-of-use, something I could get up and running quickly. I am not a front-end engineer. I did not want to spend my time learning front-end things. So, yeah, WordPress.
+The previous blog used WordPress. I know, Wordpress. My reasoning for picking WordPress was ease-of-use and something I could get up and running quickly. I am not a front-end engineer. I did not want to spend my time learning front-end things. So, yeah, WordPress.
 
 I have a lot of patience, but my patience is finite. I used WordPress for over a year. Posting became... not fun. Posting became a chore. Posting was a slow process. Posting, the back-end portion, was **painfully slow**. A few weeks ago, I started looking for an alternative.
 
@@ -31,27 +31,28 @@ The tech chosen for the new blog needed to meet some key requirements.
 
 I ran across a post on [HackerNews](news.ycombinator.com) where SSGs (Static Site Generators) were being discussed. SSGs are not new. Specifically, SSGs were not a new, shiny, cool thing, to me, so I glossed over that option.
 
-After some research, I started with Eleventy. Then Gatsby. Then Hugo. This blog came very close to being built with Hugo. I learned a lot ~~experimenting~~ trying and failing. Tears, coffee and busted keys.
+After some research, I started with Eleventy. Then Gatsby. Then Hugo. This blog came very close to being built with Hugo. I learned a lot ~~experimenting~~ trying and failing.
 
 <br>
 
 <img src="https://i.imgur.com/OjdUc71.png" alt="Too Far Down" width="100%" />
+_Down the rabbit hole_
 
 <br>
 
+At the tail end of a Hugo marathon, I remember looking at my screen, eyes glazed over and thinking, "This is too much. Too much front-end work. I am doing something wrong."
 
+I decided to regroup and go hands-off for a day and do more research. I ran across a [video](https://www.youtube.com/watch?v=F8iOU1ci19Q) by [Techno Tim](https://www.youtube.com/@TechnoTim). In the video, he went from start-to-finish in setting up a site based on [Jekyll](https://jekyllrb.com/) using the [Chirpy](https://chirpy.cotes.page/) theme. 
 
-At the tail end of a Hugo marathon, I remember looking at my screen, eyes glazed over and thinking, "This is too much. Too much front-end work. I am doing something wrong." Going down a rabbit hole is fine. If you find yourself saying, "Oh, dear. I do wish I hadn't cried so much" or "It would be so nice if something made sense for a change" then you have gone too far.
-
-I decided to regroup and go hands-off for a day and do more research. I ran across a [video](https://www.youtube.com/watch?v=F8iOU1ci19Q) by Techno Tim. In the video, he went from start-to-finish in setting up a site based on Jekyll. I liked what he had done and was able to replicate it.
+I liked what he had done and was able to replicate it.
 
 ## Azure, Jekyll & GitHub
 
-With the prototype meeting all the requirements, the last thing was finding a hosting solution.
+With the prototype meeting all the requirements, the last thing was hosting.
 
 Hosting was something I had been thinking about. During my research I had run across some stuff on Azure Static Web Apps. Gatsby and Hugo are one of the **Build Presets** offered when creating an Azure Static Web App. Jekyll was not. One of the things I am currently studying is [Azure](https://learn.microsoft.com/en-us/certifications/exams/az-104) so this seemed like the perfect opportunity to **make** the new Jekyll site work as an Azure Static Web App.
 
-I used a Custom Build Preset for Jekyll when creating the Azure Static Web App. Figuring out Azure, GitHub, GitHub Action Runs, VSCode, etc. was much easier than my week working with Eleventy/Gatsby/Hugo, Node, JS, etc. The final process for managing the site and posting also met my requirements.
+I used a Custom Build Preset for Jekyll when creating the Azure Static Web App. Figuring out Azure, GitHub, GitHub Action Runs, VSCode, etc. was much easier than working with Eleventy/Gatsby/Hugo, Node, JS, etc. The final process for managing the site and posting also met my requirements.
 
 ## Conclusion
 
@@ -62,4 +63,7 @@ I am not a master of Azure Static Web Apps, GitHub or Jekyll. There is probably
 3. Monitor/Verify GitHub Action Run
 4. Confirm changes on Live site
 
-A future post will go over (re)creating the Jekyll site as an Azure Static Web App. This will be documentation for me and hopefully help someone else out there. For now, I am very pleased with the result. **BONUS: Forgot to mention that using a Azure Static Web App is**free**. Hosting costs reduced by 100%.**
+A future post will go over (re)creating the Jekyll site as an Azure Static Web App. This will be documentation for me and hopefully help someone else out there. For now, I am very pleased with the result. 
+
+>Using Azure Static Web Apps is**free**. Hosting costs reduced by 100%.
+{: .prompt-info}