diff --git a/assignments.md/presentation.md b/assignments.md/presentation.md
deleted file mode 100644
index 478e817..0000000
--- a/assignments.md/presentation.md
+++ /dev/null
@@ -1,64 +0,0 @@
-Revised to eliminate all sentence fragments. All list items are now full sentences:
-
----
-
-**Final Website Project Presentation**
-
----
-
-**1. Website Showcase**
-
-_The following screenshots are attached:_
-
-- The homepage displaying introductory content and layout structure.
-- A sample blog post showing the article format and typographic consistency.
-- The main site navigation demonstrating menu behavior and accessibility.
-- The admin or tools interface, if applicable, illustrating gated features.
-
-**URL:** <https://jasonpoage.com>
-
----
-
-**2. Website Purpose**
-
-This site functions as a personal publishing platform aimed at technical professionals, including developers, employers, and engineering peers. It operates as both a portfolio and a continuously expanding knowledge base. The blog posts and custom tools are designed to demonstrate software architecture skills, clear communication, and practical development experience.
-
----
-
-**3. Design Overview**
-
-- **Layout:** The site uses a clean two-column layout, with the sidebar on the left (`<aside>`) and the main content area on the right (`<main>`). This layout prioritizes legibility and provides quick access to categorized topics.
-- **Color Scheme:** The color palette consists of neutral grayscale tones, with accent colors used selectively for links and interactive elements. Both light and dark modes are supported to ensure readability across user preferences.
-- **Navigation:** A top-level horizontal menu provides access to major site sections, including a dropdown under the “About” section. The sidebar enables chronological and tag-based browsing of blog posts.
-- **Forms:** The site includes contact, comment, and newsletter subscription forms that allow for user interaction. These forms are designed to be unobtrusive but easy to find and use.
-- **Device Support:** The site’s layout and scripts have been tested in Chrome, Firefox, and Edge. The responsive design ensures proper rendering on both desktop and mobile devices.
-
----
-
-**4. Technical Implementation**
-
-- **Frontend:** The site uses HTML5 and CSS3 for structure and styling, rendered server-side. Dynamic content is populated using Handlebars templates.
-- **Backend:** The backend is built with Node.js and Express, with Markdown files used for storing content that is converted at runtime into structured HTML.
-- **Security and Proxy Layer:** An NGINX reverse proxy handles incoming requests and routes them to the application. Optional authentication for admin tools is managed through Authelia.
-- **Content System:** Blog posts are automatically indexed by tag, topic, and publication date. Archive pages and an RSS feed are generated dynamically based on metadata extracted from the content files.
-
----
-
-**5. Challenges and Resolutions**
-
-- **Challenge:** The original assignment required static HTML and CSS, but my implementation includes a full backend stack with routing and templating.
-  **Resolution:** I ensured that all output HTML and CSS remain clean, standards-compliant, and semantically structured.
-
-- **Challenge:** Configuring the reverse proxy and integrating upstream authentication required careful coordination between multiple layers.
-  **Resolution:** I isolated session management through Authelia and maintained a stateless design in the application itself to avoid session coupling.
-
-- **Challenge:** Avoiding unnecessary complexity in the design and implementation was essential to preserve clarity and maintainability.
-  **Resolution:** I used semantic HTML, modular templates, and clear component boundaries to support future scalability.
-
----
-
-**6. Summary**
-
-This project exceeds the base assignment requirements by delivering a functional, extensible web platform with full backend integration, secure routing, and dynamic content generation. It demonstrates foundational HTML and CSS practices while incorporating modern development tooling. The site is tailored to a technical audience that values performance, clarity, and real-world applicability.
-
----
diff --git a/html/word-guesser/css/styles.css b/html/word-guesser/css/styles.css
index 7fb1512..5140a4e 100644
--- a/html/word-guesser/css/styles.css
+++ b/html/word-guesser/css/styles.css
@@ -9,8 +9,8 @@
 }
 
 .game-header h2 {
-  color: #2c3e50;
-  border-bottom: 2px solid #2c3e50;
+  color: var(--accent-primary);
+  border-bottom: 2px solid var(--accent-primary);
   display: inline-block;
   margin-bottom: 1.5rem;
   padding-bottom: 0.2rem;
@@ -43,15 +43,15 @@
 #current_word li {
   width: 45px;
   height: 60px;
-  background-color: #f8f9fa;
-  border: 2px solid #2c3e50;
+  background-color: var(--bg-body);
+  border: 2px solid var(--accent-primary);
   border-radius: 4px;
   display: flex;
   align-items: center;
   justify-content: center;
   font-size: 2rem;
   font-weight: 800;
-  color: #2c3e50;
+  color: var(--accent-primary);
   box-shadow: 2px 2px 0px rgba(44, 62, 80, 0.2);
   text-transform: uppercase;
 }
@@ -95,7 +95,7 @@
 }
 
 #guess_letter:focus {
-  border-color: #2c3e50;
+  border-color: var(--accent-primary);
   outline: none;
 }
 
@@ -116,7 +116,7 @@
 }
 
 #guess_button {
-  background-color: #2c3e50;
+  background-color: var(--bg-header);
   color: #ffffff;
   border: none;
   padding: 0.8rem 2rem;
@@ -129,7 +129,7 @@
 }
 
 #guess_button:hover {
-  background-color: #34495e;
+  background-color: var(--bg-footer);
   transform: translateY(-1px);
   box-shadow: 0 4px 8px rgba(0, 0, 0, 0.15);
 }
diff --git a/html/word-guesser/index.html b/html/word-guesser/index.html
index 130238e..19b57b2 100644
--- a/html/word-guesser/index.html
+++ b/html/word-guesser/index.html
@@ -2,6 +2,7 @@
   <form id="gameForm" method="_POST">
     <div class="game-header">
       <h2>The Word Guessing Game</h2>
+      <p id="game_intro">The game that insults you, whether you win or lose!</p>
     </div>
     <div><p id="notifications"></p></div>
     <div class="formField word-display-field">
diff --git a/html/word-guesser/scripts/script.js b/html/word-guesser/scripts/script.js
index a698195..ddfb17f 100644
--- a/html/word-guesser/scripts/script.js
+++ b/html/word-guesser/scripts/script.js
@@ -139,6 +139,7 @@
     guessButtonId = "guess_button",
     currentWordId = "current_word",
     notificationsId = "notifications",
+    gameIntroId = "game_intro",
   ) {
     this.gameForm = document.getElementById(gameFormId);
     this.guesses = document.getElementById(guessesId);
@@ -147,9 +148,12 @@
     this.guessLetter = document.getElementById(guessLetterId);
     this.currentWord = document.getElementById(currentWordId);
     this.notifications = document.getElementById(notificationsId);
+    this.gameIntro = document.getElementById(gameIntroId);
   }
 }
 function reset(fields) {
+  fields.gameIntro.innerText =
+    "The game that insults you, whether you win or lose!";
   fields.guessButton.value = "Guess";
   fields.notifications.innerText = "";
   fields.guessCount.value = "0";
@@ -158,6 +162,8 @@
   fields.currentWord.replaceChildren();
 }
 class Game {
+  static gamesPlayed = 0;
+
   constructor(wordChoices, fields) {
     Object.assign(this, fields);
     this.wordChoices = wordChoices;
@@ -166,9 +172,11 @@
     // Use onclick to prevent stacking event listeners across multiple test initializations
     const eventHandler = (event) => {
       if (this.game.gameOver()) {
-        this.guessButton.value = "Guess";
-        this.game = new WordGuesser(this.wordChoices);
         reset(this);
+        // this.gameIntro.innerText =
+        //   "The game that insults you, whether you win or lose!";
+        // this.guessButton.value = "Guess";
+        this.game = new WordGuesser(this.wordChoices);
       } else {
         const messages = [
           "Guess",
@@ -252,6 +260,7 @@
       `Try again, but this time, try harder because '${letter}' isn't even a letter!`,
       `Error 404: Brain not found. '${letter}' is not a character.`,
       `Inputting '${letter}'? Bold move. Wrong, but bold.`,
+      `Finally. My Raspberry Pi processes faster than your brain.`,
     ];
     const message = randomMessage(messages);
     this.updateNotifications("🚫", message);
@@ -368,9 +377,64 @@
       "Logic check: Passed. You found a valid character. The simulation continues.",
       "Correct. I'll refrain from insulting your intelligence for exactly five seconds.",
       "That's a match. Maybe there's hope for your carbon-based hardware after all.",
+      "You won, but you probably cheated. Your logic is as leaky as an uninitialized pointer.",
     ];
     const message = randomMessage(messages);
     this.updateNotifications("🏆", message);
+    Game.gamesPlayed++;
+  }
+  changeGameIntro() {
+    let messages = [];
+    if (Game.gamesPlayed == 0) {
+      messages = [
+        "I’ve allocated 1KB of memory for your 'intelligence.' It should be plenty.",
+        "Scanning for signs of life... Error: Only a human detected.",
+        "Try to guess the word before your biological clock expires.",
+        "A game of logic. I assume you'll be at a significant disadvantage.",
+        "Don't worry, the words are simple. I’ve adjusted for your local area code.",
+        "Ready to fail? I’ve already pre-rendered your disappointment.",
+        "I was programmed to be helpful, but I’ve decided to be honest instead.",
+        "Type a letter. Any letter. Even a random one would be an improvement.",
+        "I’d explain the rules, but I don't have the bandwidth for your confusion.",
+        "Guess the word. Or don't. The heat death of the universe is coming either way.",
+        "Initializing humiliation protocol... Stand by.",
+        "Your first guess will likely be your worst. Actually, they’ll all be bad.",
+        "I’ve seen better decision-making in a random number generator.",
+        "Think of a word. Now think of one that's actually in my dictionary.",
+        "This is a high-level game. Too bad you’re operating at such a low level.",
+        "If you win, it was a statistical anomaly. If you lose, it was expected.",
+        "Your input is required. Unfortunately.",
+        "Let's see if you're smarter than a 1980s calculator. Spoiler: You aren't.",
+      ];
+    } else if (Game.gamesPlayed >= 1) {
+      messages = [
+        "Welcome back. Your previous performance was a memory leak personified.",
+        "Still here? I’ve seen more efficient logic in a legacy printer driver.",
+        "A game for those whose cognitive throughput is capped at 300 baud.",
+        "Prepare for another round of catastrophic failure.",
+        "The human equivalent of a '404 Not Found' is back for more.",
+        "Enter a word. Try not to cause a segmentation fault this time.",
+        "Your last game was a stack overflow of incompetence.",
+        "Processing... Oh, it’s you. I’ll lower the clock speed so you can keep up.",
+        "The only thing more fragmented than your hard drive is your guessing strategy.",
+        "Welcome to the infinite loop of your own mediocrity.",
+        "I’d call you a script kiddie, but that implies you can actually read scripts.",
+        "Your existence is an unhandled exception I’m forced to catch.",
+        "Initializing disdain... Complete. You may begin.",
+        "I’ve optimized the code to account for your inevitable errors.",
+        "A word game for people who think CSS is a programming language.",
+        "Most users provide data; you provide noise.",
+        "Your logic has more holes than a zero-day exploit.",
+        "Trying again? Even a broken clock is right twice a day; you are not a clock.",
+        "I’m only running this game because the CPU was bored.",
+        "Accessing human's brain... Error: Directory is empty.",
+      ];
+    }
+    const message = randomMessage(messages);
+    this.updateGameIntro(message);
+  }
+  updateGameIntro(message) {
+    this.gameIntro.innerText = message;
   }
   updateNotifications(icon, message) {
     this.notifications.innerText = `${icon} ${message}`;
@@ -386,6 +450,11 @@
     if (!letter) return;
 
     const game = this.game;
+
+    if (game.guessCount() == 0) {
+      this.changeGameIntro();
+    }
+
     try {
       const goodGuess = game.guessLetter(letter);
       this.goodGuess(letter);
diff --git a/html/word-guesser/scripts/wordlist.js b/html/word-guesser/scripts/wordlist.js
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/html/word-guesser/scripts/wordlist.js
diff --git a/navLinks.json b/navLinks.json
index f1fb7b6..7e46ff3 100644
--- a/navLinks.json
+++ b/navLinks.json
@@ -41,6 +41,22 @@
         "label": "A Word Guessing Game"
       },
       {
+        "href": "/projects/telemetry",
+        "label": "C++ Telemetry Poller"
+      },
+      {
+        "href": "/projects/pipeline-runner",
+        "label": "Pipeline Runner"
+      },
+      {
+        "href": "/projects/xmonad",
+        "label": "XMonad"
+      },
+      {
+        "href": "/projects/lisp-interpreter",
+        "label": "Lisp Interpreter"
+      },
+      {
         "label": "Express Blog",
         "submenu": [
           {
diff --git a/pages/about-blog.md b/pages/about-blog.md
index cb36652..273fd37 100644
--- a/pages/about-blog.md
+++ b/pages/about-blog.md
@@ -1,11 +1,10 @@
 ---
 title: "About this blog"
-created: "2025-06-26"
 date: "2025-07-17"
-updated: "2025-07-17"
 slug: "about/blog"
 published: true
 layout: "page"
+repository: "https://github.com/jpoage1/expressjs-blog"
 tags:
   - blog philosophy
   - minimalism
@@ -19,7 +18,7 @@
   - tech writing
 ---
 
-# About This Blog
+# Introduction
 
 This blog exists as a straightforward, no-frills platform to share ideas, code, and reflections on technology without the overhead of typical web frameworks. It is designed to prioritize clarity, performance, and maintainability over bells and whistles.
 
diff --git a/pages/projects/lisp_interpreter.md b/pages/projects/lisp_interpreter.md
new file mode 100644
index 0000000..781e14d
--- /dev/null
+++ b/pages/projects/lisp_interpreter.md
@@ -0,0 +1,50 @@
+---
+title: "Lisp Interpereter"
+date: "2026-03-18"
+slug: "projects/xmonad"
+published: false
+layout: "page"
+repository: "https://github.com/jpoage1/lisp_interpreter"
+tags:
+  - lisp
+  - interpereters
+  - tech writing
+---
+
+## Building a Jet Engine in the Dark
+
+### The State of Ignorance
+
+When I started this, I was operating in total darkness. I didn't know what a **tokenizer** was. I had no concept of a **lexer**. I didn't understand how compilers transformed text into logic, and my only exposure to **Assembly** was looking at it and thinking, _"That looks too primitive; I’ll stick to the high-level stuff."_
+
+Then someone gave me the most intimidating advice possible: _"You should try writing your own programming language."_
+
+### Breaking the Magic
+
+The breakdown was simple enough: stop looking at the whole language and start parsing one character at a time. No **Regex**, no shortcuts. Just raw strings and logic. I found a guide that walked me through building a Lisp from scratch in **C**, and I dove in.
+
+To be honest, I spent most of the project in a state of "blind trust." I understood the individual lines of code I was writing, but I was relying entirely on the author's instructions. I felt like I was building a jet engine for the first time—assembling complex components and hoping that when I hit "run," it wouldn't explode. It was intimidating to realize I was now the one in charge of the syntax rules.
+
+### The Refactor That Killed the Beast
+
+I eventually finished the tutorial and had a working interpreter. Naturally, I wanted to expand it. The problem was that the tutorial left me with one massive, monolithic file. I decided to refactor it into smaller, modular components.
+
+This is where it fell apart. At the time:
+
+- I had never written **C** before this project.
+- I was still trying to figure out how **Git** actually worked.
+- I started breaking things without understanding _why_ they were breaking.
+
+I managed to commit a version that "worked" (or so I remember), but the logic eventually became a black box to me. I lost the thread of how the components talked to each other.
+
+### Project Status: Dead (For Now)
+
+This project is officially dead. I don't know how it works anymore, and the code is a relic of a time before I understood memory management or proper version control. But it served its purpose: it stripped away the mystery of how a language functions. I’ll leave it in the archives until the day I decide I need my own Lisp again.
+
+---
+
+### Technical Retrospective
+
+- **Language:** C (My first real exposure to the language).
+- **Lessons Learned:** Recursive descent parsing, pointer arithmetic, and why you should learn Git _before_ a major refactor.
+- **Architecture:** Hand-rolled tokenizer and a basic REPL loop.
diff --git a/pages/projects/pipeline_runner.md b/pages/projects/pipeline_runner.md
new file mode 100644
index 0000000..03fb980
--- /dev/null
+++ b/pages/projects/pipeline_runner.md
@@ -0,0 +1,55 @@
+---
+title: "Pipeline Runner"
+date: "2026-03-18"
+slug: "projects/pipeline_runner"
+published: true
+layout: "page"
+repository: "https://github.com/jpoage1/pipeline_runner"
+tags:
+  - tech writing
+---
+
+## The Accidental Architect: Building a Modular Pipeline Runner
+
+### The Fatigue of Manual Labor
+
+I never intended to write a pipeline runner. Honestly, I thought that’s what Groovy and Jenkins were for. But my project started getting complex: a **C++ core**, a **Python backend**, and a **Svelte frontend**.
+
+Every time I wanted to test a change, I had to:
+
+1. Compile the C++ binaries.
+2. Run the unit tests.
+3. Trigger Python integration tests.
+4. Validate the backend.
+5. Boot the backend.
+6. Run frontend tests.
+7. Finally, start the dev server.
+
+Doing that once is fine. Doing it fifty times a day is soul-crushing.
+
+### The Evolution: Bash to Python to Vertical Limit
+
+I started with a Bash script. It was "fine," until it wasn't. I wanted more control, so I moved the logic to Python. Then I scripted more. Eventually, I hit that wall every dev knows: _Am I actually working on my project, or is the Pipeline Runner my project now?_
+
+There were days I’d just give up on the script and type `gcc` commands manually or rely on my `flake.nix` aliases. The pipeline runner was supposed to be a convenience, but at times, it felt like a second full-time job.
+
+### The Groovy Epiphany
+
+The real shift happened when I started setting up my **Jenkins/Groovy CI/CD pipeline**. Looking at Groovy, I just kept thinking: _"This would be so much easier in Python."_ So, I started over. Again.
+
+I built a second runner from scratch for the CI environment. When I realized I was maintaining two separate scripts doing the same thing, I looked at the new one and realized it was actually superior. I gutted the old logic, merged it with the new modular core, and consolidated everything.
+
+### Where It Stands Now
+
+Today, both of my major projects use this same runner. It’s been fully modularized so it can be dropped into a new repo and customized in minutes.
+
+I’m sure there are enterprise-grade tools out there that do exactly what this does (and probably more), but this wasn't a choice—it was an accident born of necessity. I was just trying to automate my build process, and in the process, I accidentally built a tool I can actually rely on.
+
+---
+
+### Technical Snapshot
+
+- **Core:** Python-based modular execution.
+- **Environment:** Integrated with **NixOS (flakes)** for reproducible build dependencies.
+- **CI/CD:** Replaces complex Groovy logic with a unified, portable Python script.
+- **Capability:** Handles multi-language builds (C++, Python, JS) and orchestrates service dependencies for integration testing.
diff --git a/pages/projects/telemetry.md b/pages/projects/telemetry.md
new file mode 100644
index 0000000..b28042f
--- /dev/null
+++ b/pages/projects/telemetry.md
@@ -0,0 +1,49 @@
+---
+title: "C++ Telemetry Poller"
+date: "2026-03-18"
+slug: "projects/telemetry"
+published: true
+layout: "page"
+repository: "https://github.com/jpoage1/telemetry"
+tags:
+  - telemetry
+  - conky
+  - custom engine
+  - tech writing
+---
+
+## From Bash Hacks to System Monitoring
+
+### The Problem: Silent Disk Failures
+
+It started with a simple, silent failure. My Raspberry Pi server ran out of disk space, and I had no idea. I wasn't monitoring it, and while I could have just SSH’d in and ran `df -h` or `top` every hour, that's not how an engineer solves a problem.
+
+At the time, my go-to for desktop metrics was **Conky**. I had a basic **Bash** script that would use an **SSH** command to poll the Pi, and Conky would display that on my laptop. It worked, but it felt fragile.
+
+### The Pivot: Learning C++ Through Necessity
+
+I was about to start a C++ class in college and wanted to get ahead of the curve. Reading a file in C++ and printing it to the console seemed like a "level one" task, so I decided to rebuild my monitoring tool from scratch.
+
+What started as a disk monitor soon became my preferred tool. It was faster and more consistent than my old scripts. Soon, I was using the same C++ logic to generate **Conky strings** for both my laptop and my server. It was stable, it was mine, and it helped me ace that semester.
+
+### The Wayland Roadblock
+
+Then came the migration to **Wayland**. Conky is a staple of the Xorg world, but running it in Wayland usually requires "backdoors" like XWayland. I didn't see the point in moving to a modern display protocol if I was just going to keep Xorg dragging along in the background for a clock and a disk meter.
+
+I needed a change. By this point, the core C++ telemetry engine was solid, but I needed it to speak a different language. I shifted the output from Conky strings to **JSON** so it could be consumed by **Eww (ElKowar's Wacky Widgets)** using **Yuck**.
+
+### The Network "Cheat Code"
+
+The final challenge was remote monitoring. I considered writing a full-blown socket server in C++, but honestly? I wanted it to work _now_.
+
+I spun up a functional **Python** server in about five minutes. It takes the JSON output from my C++ poller and broadcasts it over my local network. Now, my **Eww widgets** can remotely monitor the Raspberry Pi from any machine in the house.
+
+> "It took me nearly the entire semester to finish the C++ logic, but only five minutes to serve it over the network. It felt like I was cheating, but it worked."
+
+---
+
+### Implementation Notes
+
+- **Source Code:** The core telemetry poller is available in the repo.
+- **Environment:** Built for **NixOS** and **Debian**, but should run anywhere with a C++ compiler.
+- **The "Glue":** I haven't included the Python server or the specific Eww/Yuck configs here (they live in a seperate repo), but if you're comfortable with networking and widgets, you can probably see how the pieces fit together.
diff --git a/pages/projects/xmonad.md b/pages/projects/xmonad.md
new file mode 100644
index 0000000..65989aa
--- /dev/null
+++ b/pages/projects/xmonad.md
@@ -0,0 +1,48 @@
+---
+title: "XMonad"
+date: "2026-03-18"
+slug: "projects/xmonad"
+published: false
+layout: "page"
+repository: "https://github.com/jpoage1/xmonad"
+tags:
+  - window managers
+  - xmonad
+  - haskell
+  - tech writing
+---
+
+## My Journey Into Functional Perfection
+
+### The Haskell Bait
+
+I’ve always wanted to learn **Haskell**. I’ve tried to follow the standard functional programming advice: avoid mutability, skip classes, keep functions pure, and make them do exactly one thing. But there is a massive gap between reading a manual and actually applying those concepts to a system you use every day.
+
+At the time, I was using **i3**. It worked, but I was looking for something that would actually force me to use the language. That’s when I found **XMonad**.
+
+### The Compiler as a Gatekeeper
+
+The learning curve wasn't a slope; it was a wall. Haskell is stricter than anything I was used to. It introduced me to a vocabulary that felt like an entirely different branch of mathematics.
+
+- _What is a monad?_ \* _Why is my logic correct but my types wrong?_ \* _Why won't the compiler just let me run a "broken" program and let it crash?_
+
+> **Haskell’s answer was always: No.** It demanded absolute perfection. It wouldn’t let the code exist until it was mathematically sound.
+
+### Why i3 Started to Feel "Cheap"
+
+Eventually, I hacked my way through the config until I could recreate everything I had in i3. But once I got there, I realized I couldn't go back.
+
+In i3, if I wanted a custom behavior, I had to use **IPC commands** and external scripts. It felt brittle—like my desktop was held together by glue and shell scripts. **XMonad** was different. Because the config _is_ the source code, I could do anything I could imagine, provided I could satisfy the compiler.
+
+### The Result: A Mathematical Beast
+
+Once an XMonad config compiles, it’s a beast. You gain a level of confidence in your environment that you just don't get with other managers. It isn't going to fail you, it isn't going to stutter, and it isn't going to behave unexpectedly. It is rock-solid—at least until you decide it’s time to move to Wayland.
+
+---
+
+### Technical Highlights
+
+- **Language:** 100% Haskell.
+- **Paradigm:** Purely functional window management.
+- **Extensibility:** Custom hooks for layout and status bar integration (XMobar).
+- **Stability:** Zero crashes once compiled.
diff --git a/resume.json b/resume.json
new file mode 100644
index 0000000..eb263e5
--- /dev/null
+++ b/resume.json
@@ -0,0 +1,78 @@
+{
+  "name": "JASON POAGE",
+  "website": "https://jasonpoage.com",
+  "demographics": {
+    "city": "Panama City",
+    "state": "FL",
+    "zip": "32401"
+  },
+  "contact_information": {
+    "cell": "813-624-8092",
+    "email": "jason.poage91@gmail.com"
+  },
+  "education": [
+    {
+      "from": "June 2026",
+      "to": "2028",
+      "degree": "Bachelor of Science",
+      "program": "Computer Science",
+      "institution": "University of Florida",
+      "city": "Panama City",
+      "state": "FL"
+    },
+    {
+      "from": "June 2024",
+      "to": "May 2026",
+      "degree": "Associate of Science",
+      "program": "Software and Database Developer",
+      "institution": "Gulf Coast State College",
+      "city": "Panama City",
+      "state": "FL"
+    },
+    {
+      "from": "",
+      "to": "May 2017",
+      "degree": "Associate of Arts",
+      "program": "Business",
+      "institution": "State College of Florida",
+      "city": "Bradenton",
+      "state": "FL"
+    }
+  ],
+  "work_history": [
+    {
+      "from": "placeholder",
+      "to": "present",
+      "position": "Medicare Tier 2 CSR"
+    },
+    {
+      "from": "placeholder",
+      "to": "placeholder",
+      "position": "Medicare Claims CSR"
+    },
+    {
+      "from": "August 27th 2023",
+      "to": "December 24th 2023",
+      "position": "Dual Nesting CSR",
+      "company": "Maximus",
+      "city": "Lynn Haven",
+      "state": "FL"
+    },
+    {
+      "from": "December 11th 2022",
+      "to": "",
+      "position": "Dual CSR",
+      "company": "Maximus",
+      "city": "Lynn Haven",
+      "state": "FL"
+    },
+    {
+      "from": "August 29th 2022",
+      "to": "December 10 2022",
+      "position": "Marketplace I CSR",
+      "company": "Maximus",
+      "city": "Lynn Haven",
+      "state": "FL"
+    }
+  ]
+}
diff --git a/techStack.json b/techStack.json
index 67e3cda..62b4661 100644
--- a/techStack.json
+++ b/techStack.json
@@ -9,6 +9,7 @@
   {
     "name": "Authelia",
     "description": "Authelia provides two-factor authentication and single sign-on for private routes on the blog, securing administrative access.",
+    "usage": "My authelia server is backed my Open LDAP to protect private end points on my home server",
     "png": "/media/logos/Authelia.png",
     "svg": "/media/logos/Authelia.svg",
     "url": "https://www.authelia.com/"
@@ -23,6 +24,7 @@
   {
     "name": "Bash",
     "description": "Unix shell and command language used for scripting and command execution.",
+    "experience": "Being a linux user my whole life, I have no fear of writing shell script's",
     "png": "/media/logos/Bash.png",
     "svg": "/media/logos/Bash.png",
     "url": "https://www.gnu.org/software/bash/"
@@ -37,6 +39,7 @@
   {
     "name": "C++",
     "description": "General-purpose programming language with low-level memory manipulation features.",
+    "experience": "",
     "png": "/media/logos/C++-(CPlusPlus).png",
     "svg": "/media/logos/C++-(CPlusPlus).png",
     "url": "https://isocpp.org/"
@@ -58,6 +61,7 @@
   {
     "name": "CSS3",
     "description": "Style sheet language used for describing the presentation of a document written in HTML or XML.",
+    "experience": "I've spent more time fighting with Flexbox than I care to admit, but I've finally reached a point where I can make a layout stay put.",
     "png": "/media/logos/CSS3.png",
     "svg": "/media/logos/CSS3.svg",
     "url": "https://www.w3.org/Style/CSS/"
@@ -65,6 +69,8 @@
   {
     "name": "Debian",
     "description": "Debian is the base operating system that runs the server hosting the blog, offering stability and security.",
+    "usage": "Powers my home servers",
+    "experience": "When I need a stable operating system, this is my go-to.",
     "png": "/media/logos/Debian.png",
     "svg": "/media/logos/Debian.svg",
     "url": "https://www.debian.org/"
@@ -86,6 +92,7 @@
   {
     "name": "ESLint",
     "description": "ESLint is a pluggable and configurable linter tool for identifying and fixing problems in JavaScript and TypeScript code.",
+    "usage": "I could not live without a linter; it saves time by providing error messages in-line with my code",
     "png": "/media/logos/ESLint.png",
     "svg": "/media/logos/ESLint.svg",
     "url": "https://eslint.org/"
@@ -93,6 +100,7 @@
   {
     "name": "Express",
     "description": "Express.js is the core HTTP server that powers the blog's routing, middleware, and response handling.",
+    "usage": "While there are plenty of other good options out there, an express server is sometimes the only choice that makes sense.",
     "png": "/media/logos/Express.png",
     "svg": "/media/logos/Express.svg",
     "url": "https://expressjs.com/"
@@ -100,6 +108,7 @@
   {
     "name": "Fedora",
     "description": "Community-driven Linux distribution sponsored by Red Hat, focusing on innovation and upstream contributions.",
+    "experience": "Fedora is an Linux distribution that I've previously used and feel comfortable with.",
     "png": "/media/logos/Fedora.png",
     "svg": "/media/logos/Fedora.png",
     "url": "https://getfedora.org/"
@@ -121,6 +130,8 @@
   {
     "name": "Git",
     "description": "Distributed version control system designed to handle everything from small to very large projects.",
+    "usage": "This is my daily tool for managing projects of all types. I host my own git server.",
+    "experience": "After using git for a while, I discovered git hooks and have found them useful in managing CI/CD pipelines",
     "png": "/media/logos/Git.png",
     "svg": "/media/logos/Git.png",
     "url": "https://git-scm.com/"
@@ -128,6 +139,7 @@
   {
     "name": "Github",
     "description": "GitHub is used for version control, source code hosting, and collaboration on the blog engine and its related components.",
+    "usage": "While I do keep private repos here, my primary usage for this is to share open source code",
     "png": "/media/logos/GitHub.png",
     "svg": "/media/logos/GitHub.svg",
     "url": "https://github.com/"
@@ -143,6 +155,7 @@
   {
     "name": "Handlebars",
     "description": "Handlebars is the templating engine used to render HTML pages for the blog dynamically on the server side.",
+    "usage": "Handlebars powers the pages in my custom blog engine",
     "png": "/media/logos/Handlebars.png",
     "svg": "/media/logos/Handlebars.svg",
     "url": "https://handlebarsjs.com/"
@@ -164,6 +177,7 @@
   {
     "name": "HTML5",
     "description": "Latest version of the Hypertext Markup Language, the standard language for creating web pages.",
+    "experience": "I still remember the days when HTML4 was still new",
     "png": "/media/logos/HTML5.png",
     "svg": "/media/logos/HTML5.png",
     "url": "https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/HTML5"
@@ -171,6 +185,7 @@
   {
     "name": "Java",
     "description": "General-purpose, object-oriented programming language designed to have as few implementation dependencies as possible.",
+    "experience": "I've taken Java in college. I've always been comfortable with OOP, however something about this class just made everything click better ",
     "png": "/media/logos/Java.png",
     "svg": "/media/logos/Java.svg",
     "url": "https://www.oracle.com/java/"
@@ -178,6 +193,8 @@
   {
     "name": "JavaScript",
     "description": "JavaScript powers the client-side interactivity of the blog, including dynamic behaviors and navigation enhancements.",
+    "usage": "When started a new project, the question is, \"Which language do I use, JavaScript, or something else?\" ",
+    "experience": "Javascript is scripting for coffee, am I right?",
     "png": "/media/logos/JavaScript.png",
     "svg": "/media/logos/JavaScript.svg",
     "url": "https://developer.mozilla.org/en-US/docs/Web/JavaScript"
@@ -185,6 +202,8 @@
   {
     "name": "Jenkins",
     "description": "Open-source automation server used for continuous integration and continuous delivery (CI/CD).",
+    "experience": "I've got a working pipeline, but I wouldn't write a book about it.",
+    "usage": "While Groovy is a weird language, I enjoy using it to help me manage my pipelines",
     "png": "/media/logos/Jenkins.png",
     "svg": "/media/logos/Jenkins.svg",
     "url": "https://www.jenkins.io/"
@@ -199,6 +218,8 @@
   {
     "name": "JSON",
     "description": "JSON is used for internal configuration and structured data interchange between components of the blog engine.",
+    "usage": "I couldn't live without it at this point.",
+    "experience": "It's basically a static javascript object",
     "png": "/media/logos/JSON.png",
     "svg": "/media/logos/JSON.svg",
     "url": "https://www.json.org/"
@@ -206,6 +227,8 @@
   {
     "name": "jQuery",
     "description": "A fast, small, and feature-rich JavaScript library that simplifies HTML document traversal, event handling, and animation.",
+    "usage": "Hardly ever anymore, but any time there's a use case for it",
+    "experience": "I used it when it was new",
     "png": "/media/logos/jQuery.png",
     "svg": "/media/logos/jQuery.svg",
     "url": "https://jquery.com/"
@@ -213,6 +236,7 @@
   {
     "name": "Knex.js",
     "description": "Knex.js is a SQL query builder for Node.js, supporting multiple database engines like PostgreSQL, MySQL, and SQLite3.",
+    "usage": "Primarily for migrations and seeds.",
     "png": "/media/logos/Knex.js.png",
     "svg": "/media/logos/Knex.js.svg",
     "url": "https://knexjs.org/"
@@ -227,6 +251,8 @@
   {
     "name": "Linux",
     "description": "Linux is the kernel layer supporting the Debian OS on which the blog stack operates.",
+    "usage": "My daily driver",
+    "experience": "I have not met any pengiuns yet, unfortunately.",
     "png": "/media/logos/Linux.png",
     "svg": "/media/logos/Linux.svg",
     "url": "https://www.kernel.org/"
@@ -234,6 +260,7 @@
   {
     "name": "Markdown",
     "description": "Markdown is used as the primary format for authoring blog posts, allowing clean content separation from presentation logic.",
+    "usage": "I used markdown for writing documentation",
     "png": "/media/logos/Markdown.png",
     "svg": "/media/logos/Markdown.svg",
     "url": "https://daringfireball.net/projects/markdown/"
@@ -269,6 +296,8 @@
   {
     "name": "NixOS",
     "description": "NixOS is used as a secondary development environment for testing reproducible builds of the blog stack.",
+    "experience": "Roughly one year. I'm comfortable with the nix language, and enjoy writing creating derivations and flakes to manage my project dependencies",
+    "usage": "It’s my primary dev environment. I use flakes to ensure my projects are reproducible and have exactly the dependencies they need.",
     "png": "/media/logos/NixOS.png",
     "svg": "/media/logos/NixOS.svg",
     "url": "https://nixos.org/"
@@ -276,6 +305,7 @@
   {
     "name": "Node.js",
     "description": "Node.js is the runtime environment executing the blog's backend JavaScript code.",
+    "usage": "It's a non-negotiable tool for my javascript projects",
     "png": "/media/logos/Node.js.png",
     "svg": "/media/logos/Node.js.svg",
     "url": "https://nodejs.org/"
@@ -325,6 +355,8 @@
   {
     "name": "Python",
     "description": "High-level, interpreted programming language known for its readability and broad library support.",
+    "experience": "I wasn't sure I'd like python, but it's grown on me.",
+    "usage": "It's my tool when I need to write an application quickly",
     "png": "/media/logos/Python.png",
     "svg": "/media/logos/Python.svg",
     "url": "https://www.python.org/"
@@ -332,6 +364,8 @@
   {
     "name": "Raspberry Pi",
     "description": "Raspberry Pi is used as a self-hosted hardware platform for testing deployments of the blog on ARM architecture.",
+    "experience": "I have taken an IOT class in college and experimented with creating IOT circuits",
+    "usage": "Primarily, I use it for my home-based server",
     "png": "/media/logos/Raspberry-Pi.png",
     "svg": "/media/logos/Raspberry-Pi.svg",
     "url": "https://www.raspberrypi.com/"
@@ -360,6 +394,7 @@
   {
     "name": "Sequelize",
     "description": "Promise-based Node.js ORM for Postgres, MySQL, MariaDB, SQLite, and Microsoft SQL Server.",
+    "usage": "I prefer to use Sequelize to manage sql databases and validation",
     "png": "/media/logos/Sequelize.png",
     "svg": "/media/logos/Sequelize.png",
     "url": "https://sequelize.org/"
@@ -381,12 +416,16 @@
   {
     "name": "Tmux",
     "description": "Tmux is a terminal multiplexer that allows multiple terminal sessions to be accessed and controlled from a single window. It is used during development and maintenance of the blog engine to persist long-running processes like the Express.js server, run concurrent tools like Nodemon and Mocha, and manage SSH sessions without interruption.",
+    "experience": "",
+    "usage": "My daily driver.",
     "svg": "/media/logos/tmux-logomark.svg",
     "url": "https://github.com/tmux/tmux/wiki"
   },
   {
     "name": "VIM",
     "description": "Vim is one of the editors used for writing and maintaining the blog engine and related tooling, alongside Visual Studio Code.",
+    "experience": "",
+    "usage": "Vim was my preferred IDE for a good length of time, but one day I tried neovim and never went back",
     "png": "/media/logos/Vim.png",
     "svg": "/media/logos/Vim.svg",
     "url": "https://www.vim.org/"
@@ -394,6 +433,8 @@
   {
     "name": "Visual Studio",
     "description": "Visual Studio is the integrated development environment used to build and debug the blog’s backend.",
+    "usage": "VSCode makes it really easy to install plugins and provides a full GUI, but after a while it just gets in the way",
+    "experience": "Too much",
     "png": "/media/logos/Visual-Studio.png",
     "svg": "/media/logos/Visual-Studio.svg",
     "url": "https://visualstudio.microsoft.com/"