Restructured content, remove wp-content folder

content/post/2023-05-21-hilger-grading-portal/index.md

@@ -18,13 +18,13 @@ That system was in production for 5 years or so with minimal updates and maintan
 
 This is the page listing all teachers in the system and whether or not they have admin privileges. Any admin user can grant other admin users this privilege. There is also a button to send the teacher a password reset email (via Postmark API integration) and an option that allows admin users to impersonate other users for troubleshooting and diagnostic purposes.
 
-![](/wp-content/uploads/2024/03/hilger-portal-all-teachers-1024x514.webp)The data is all coming from the KeystoneJS backend GraphQL API. I am using [urql](https://www.npmjs.com/package/urql) for fetching the data and handling mutations. This is the page that displays students. It is filterable and searchable. Teachers also have the ability to mark a student as active or inactive for the semester as well as delete them from the system.
+![](/images/hilger-portal-all-teachers-1024x514.webp)The data is all coming from the KeystoneJS backend GraphQL API. I am using [urql](https://www.npmjs.com/package/urql) for fetching the data and handling mutations. This is the page that displays students. It is filterable and searchable. Teachers also have the ability to mark a student as active or inactive for the semester as well as delete them from the system.
 
-![](/wp-content/uploads/2024/03/hilger-portal-all-students-1-1024x513.webp)Clicking on a student takes the teacher/admin to an edit course screen where they can add and remove courses for each student. A teacher can add as many courses as they need. If multiple teachers have added courses for this student, the user will only see the courses they have entered.
+![](/images/hilger-portal-all-students-1-1024x513.webp)Clicking on a student takes the teacher/admin to an edit course screen where they can add and remove courses for each student. A teacher can add as many courses as they need. If multiple teachers have added courses for this student, the user will only see the courses they have entered.
 
-![](/wp-content/uploads/2024/03/hilger-portal-edit-student-1024x514.webp)There is another page that allows admin users to view and manage all of the parents in the system. It allows them to easily send a password reset email to the parents as well as to view the parent portal.
+![](/images/hilger-portal-edit-student-1024x514.webp)There is another page that allows admin users to view and manage all of the parents in the system. It allows them to easily send a password reset email to the parents as well as to view the parent portal.
 
-![](/wp-content/uploads/2024/03/hilger-portal-parents-1024x513.webp)---
+![](/images/hilger-portal-parents-1024x513.webp)---
 
 ## Technologies used
 

content/post/2023-07-12-hoots-wings/index.md

@@ -3,7 +3,7 @@ author: Mike Conrad
 categories:
 - Software Engineering
 date: "2023-07-12T11:32:44Z"
-image: /wp-content/uploads/2024/03/hoots-locations-min.webp
+image: /images/hoots-locations-min.webp
 tags:
 - Portfolio
 title: Hoots Wings
@@ -12,11 +12,11 @@ title: Hoots Wings
 
 While working for [Morrison](https://morrison.agency/) I had the pleasure of building a website for [Hoots Wings.](https://hootswings.com) The CMS was [Perch](https://grabaperch.com/) and it was mostly HTML, CSS, PHP and JavaScript on the frontend, however I built out a customer store locator using NodeJS and VueJS.
 
-![](/wp-content/uploads/2024/03/hoots-home.webp)I was the sole frontend developer responsible for taking the designs from SketchUp and translating them to the site you see now. Most of the blocks and templates are built using a mix of PHP and HTML/SCSS. There was also some JavaScript for things like getting the users location and rendering popups/modals.
+![](/images/hoots-home.webp)I was the sole frontend developer responsible for taking the designs from SketchUp and translating them to the site you see now. Most of the blocks and templates are built using a mix of PHP and HTML/SCSS. There was also some JavaScript for things like getting the users location and rendering popups/modals.
 
 The store locator was a separate piece that was built in Vue2.0 with a NodeJS backend. For the backend I used [KeystoneJS](https://keystonejs.com/) to hold all of the store information. There was also some custom development that was done in order to sync the stores added via the CMS with [Yext](https://www.yext.com/) and vice versa.
 
-![hootswings.com screenshot](/wp-content/uploads/2024/03/hoots-locations-min-1024x522.webp)For that piece I ended up having to write a custom integration in Perch that would connect to the NodeJS backend and pull the stores but also make sure that those were in sync with Yext. This required diving into the Yext API some and examining a similar integration that we had for another client site.
+![hootswings.com screenshot](/images/hoots-locations-min-1024x522.webp)For that piece I ended up having to write a custom integration in Perch that would connect to the NodeJS backend and pull the stores but also make sure that those were in sync with Yext. This required diving into the Yext API some and examining a similar integration that we had for another client site.
 
 Unfortunately I don’t have any screen grabs of the admin side of things since that is proprietary but the system I built allowed a site admin to go in and add/edit store locations that would show up on the site and also show up in Yext with the appropriate information.
 
@@ -26,8 +26,8 @@ Here are some full screenshots of the site.
 
 Homepage
 
-![hootswings.com homepage screenshot](/wp-content/uploads/2024/03/hootswings-home-full-635x1024.webp)Menu Page
+![hootswings.com homepage screenshot](/images/hootswings-home-full-635x1024.webp)Menu Page
 
-![](/wp-content/uploads/2024/03/hootswings-menu-page-550x1024.png)Locations Page
+![](/images/hootswings-menu-page-550x1024.png)Locations Page
 
-![](/wp-content/uploads/2024/03/hootswings-locations-page-432x1024.png)
+![](/images/hootswings-locations-page-432x1024.png)

content/post/2024-01-03-roll-your-own-authenticator-app-with-keystonejs-and-react/index.md

@@ -157,10 +157,10 @@ $ keystone dev
 
 Our server should be running on localhost:3000 so let’s check it out! The first time we open it up we will be greeted with the initialization screen. Go ahead and create an account to login:
 
-![](/wp-content/uploads/2024/03/keystone-init-min.webp)Once you login you should see a dashboard similar to this:
+![](/images/keystone-init-min.webp)Once you login you should see a dashboard similar to this:
 
-![](/wp-content/uploads/2024/03/keystone-dashboard-min-1024x607.webp)You can see we have Users and Tokens that we can manage. The beauty of KeystoneJS is that you get full CRUD functionality out of the box just by defining our schema! Go ahead and click on Tokens to add a token:
+![](/images/keystone-dashboard-min-1024x607.webp)You can see we have Users and Tokens that we can manage. The beauty of KeystoneJS is that you get full CRUD functionality out of the box just by defining our schema! Go ahead and click on Tokens to add a token:
 
-![](/wp-content/uploads/2024/03/create-token-min-1024x572.webp)For this example I just entered some random text as an example. This is enough to start testing out our TOTP functionality. Click ‘Create Token’ and you should see a list displaying existing tokens:
+![](/images/create-token-min-1024x572.webp)For this example I just entered some random text as an example. This is enough to start testing out our TOTP functionality. Click ‘Create Token’ and you should see a list displaying existing tokens:
 
-![](/wp-content/uploads/2024/03/display-token-dashboard-min-1024x275.webp)We are now ready to jump into the frontend. Stay tuned for pt 2 of this series.
+![](/images/display-token-dashboard-min-1024x275.webp)We are now ready to jump into the frontend. Stay tuned for pt 2 of this series.