diff --git a/xavishobbies/content/web_development/building_with_hugo.md b/xavishobbies/content/web_development/building_with_hugo.md
new file mode 100644
index 0000000..cb32644
--- /dev/null
+++ b/xavishobbies/content/web_development/building_with_hugo.md
@@ -0,0 +1,65 @@
+---
+title: "Building_with_Hugo"
+date: 2023-03-06T00:00:00-08:00
+description: Web Development - Hugo
+categories: ["Top_of_the_Stack"]
+tags: ["Web Development","Hugo"]
+---
+
+As much as I started to enjoy playing around and styling with *html/css*, it did, at times, become slightly annoying to quickly document progress on projects **[which is hard enough to do as it is]**. This was especially true when trying to structure the site to reference identical posts on multiple pages **[ie. on the [tots](https://xavishobbies.org/categories/top_of_the_stack/) page as well on the associated hobby page]**. A solution that I have been mulling from the beginning is a *static site generator*.
+
+What I was looking for was an environment that was *extensible* enough to eliminate redundant code while also *malleable* enough to execute the initial vision I had for the website **[i know, surprising this website had any vision given the look]**. Static site generators enable this by, essentially, copying identical html across multiple pages through *templates*. This maintains the benefits of a static site while addressing one of it's biggest drawbacks. After some research **[googling "best static site generator"]**, [Hugo](https://gohugo.io/) seemed to check the boxes I had in mind while also seeming relatively simple to implement **[which is something a lazy person like me really values]**.
+
+*Hugo* is structured hierarchically and has a couple main directories where content is pulled to generate pages. *Content*, where the actual content of a *post* is stored, *layouts*, where *templates* and other *code snippets* are defined, and *static*, where things like *images* referenced in posts and *style sheets* are contained.
+
+New content posts can be created with `hugo new section_name/post.md` which creates a new file under *content/section_name/post.md*. For example this post was created with `hugo new web_development /building_with_hugo.md`. Section landing pages can be created by adding a *_index.md* file under the section directory with `hugo new section_name/_index.md` **[these will call the *list* template, if you don't know what that means, *read on!*]**.
+
+Hugo posts are written in [Markdown](https://www.markdownguide.org/basic-syntax/) which, basically, is a way to define the format of text through some pretty straightforward syntax **[trust me, it's really easy to pick up]**. If Markdown's default behavior is not cutting it for you, it can also be redefined under */layouts/_defaults/_markup*.
+
+However, sometimes *Markdown* doesn't have all the functionality that *html* would allow. In these cases *shortcodes* can be used to *inject html* into a content page by calling the shortcode with `{{* $name_of_shortcode $arg0 $arg1 $arg2 */>}}`. For example, I have a shortcode to format an image correctly in a post under */layouts/shortcodes/image_sc.html*.
+
+``` html
+
+
{{ .Content }}
+ +