diff --git a/astro.config.mjs b/astro.config.mjs
index 3b8ec31..9e974a9 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -1,16 +1,21 @@
 // @ts-check
 
 import tailwindcss from '@tailwindcss/vite';
+import remarkDirective from 'remark-directive';
+import remarkAlert from 'remark-github-beta-blockquote-admonitions';
 import { defineConfig } from 'astro/config';
-
 import react from '@astrojs/react';
 
-// https://astro.build/config
 export default defineConfig({
   site: "http://blog.yorisoft.dev/",
   vite: {
-      plugins: [tailwindcss()],
-	},
-
+    plugins: [tailwindcss()],
+  },
+  markdown: {
+    remarkPlugins: [
+      remarkDirective,
+      remarkAlert,
+    ],
+  },
   integrations: [react()],
 });
\ No newline at end of file
diff --git a/package-lock.json b/package-lock.json
index f786470..952fa5e 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -30,6 +30,8 @@
         "lucide-react": "^0.562.0",
         "react": "^19.2.3",
         "react-dom": "^19.2.3",
+        "remark-directive": "^4.0.0",
+        "remark-github-beta-blockquote-admonitions": "^3.1.2",
         "tailwind-merge": "^3.4.0",
         "tailwindcss": "^4.1.18"
       },
@@ -268,7 +270,6 @@
       "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.28.6.tgz",
       "integrity": "sha512-H3mcG6ZDLTlYfaSNi0iOKkigqMFvkTKlGUYlD8GW7nNOYRrevuA46iTypPyv+06V3fEmvvazfntkBU34L0azAw==",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@babel/code-frame": "^7.28.6",
         "@babel/generator": "^7.28.6",
@@ -1021,7 +1022,6 @@
       "resolved": "https://registry.npmjs.org/@fortawesome/fontawesome-svg-core/-/fontawesome-svg-core-7.1.0.tgz",
       "integrity": "sha512-fNxRUk1KhjSbnbuBxlWSnBLKLBNun52ZBTcs22H/xEEzM6Ap81ZFTQ4bZBxVQGQgVY0xugKGoRcCbaKjLQ3XZA==",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@fortawesome/fontawesome-common-types": "7.1.0"
       },
@@ -3108,7 +3108,6 @@
       "resolved": "https://registry.npmjs.org/@types/react/-/react-19.2.8.tgz",
       "integrity": "sha512-3MbSL37jEchWZz2p2mjntRZtPt837ij10ApxKfgmXCTuHWagYg7iA5bqPw6C8BMPfwidlvfPI/fxOc42HLhcyg==",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "csstype": "^3.2.2"
       }
@@ -3118,7 +3117,6 @@
       "resolved": "https://registry.npmjs.org/@types/react-dom/-/react-dom-19.2.3.tgz",
       "integrity": "sha512-jp2L/eY6fn+KgVVQAOqYItbF0VY/YApe5Mz2F0aykSO8gx31bYCZyvSeYxCHKvzHG5eZjc+zyaS5BrBWya2+kQ==",
       "license": "MIT",
-      "peer": true,
       "peerDependencies": {
         "@types/react": "^19.2.0"
       }
@@ -3160,7 +3158,6 @@
       "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.15.0.tgz",
       "integrity": "sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==",
       "license": "MIT",
-      "peer": true,
       "bin": {
         "acorn": "bin/acorn"
       },
@@ -3327,7 +3324,6 @@
       "resolved": "https://registry.npmjs.org/astro/-/astro-5.16.9.tgz",
       "integrity": "sha512-gJvoZv0v8xCcKBcsxz1ZfXqoJ7sJJcyoKP8bUTjkuD4vDShLe0N26em4LQxitVv/2HLOpldQg67bEHB/qGoxJA==",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "@astrojs/compiler": "^2.13.0",
         "@astrojs/internal-helpers": "0.7.5",
@@ -3564,7 +3560,6 @@
         }
       ],
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "baseline-browser-mapping": "^2.9.0",
         "caniuse-lite": "^1.0.30001759",
@@ -4870,7 +4865,6 @@
       "resolved": "https://registry.npmjs.org/jiti/-/jiti-2.6.1.tgz",
       "integrity": "sha512-ekilCSN1jwRvIbgeg/57YFh8qQDNbwDb9xT/qu2DAHbFFZUicIl4ygVaAvzveMhMVr3LnpSKTNnwt8PoOfmKhQ==",
       "license": "MIT",
-      "peer": true,
       "bin": {
         "jiti": "lib/jiti-cli.mjs"
       }
@@ -4931,7 +4925,6 @@
       "resolved": "https://registry.npmjs.org/lightningcss/-/lightningcss-1.30.2.tgz",
       "integrity": "sha512-utfs7Pr5uJyyvDETitgsaqSyjCb2qNRAtuqUeWIAKztsOYdcACf2KtARYXg2pSvhkt+9NfoaNY7fxjl6nuMjIQ==",
       "license": "MPL-2.0",
-      "peer": true,
       "dependencies": {
         "detect-libc": "^2.0.3"
       },
@@ -5258,6 +5251,27 @@
         "url": "https://opencollective.com/unified"
       }
     },
+    "node_modules/mdast-util-directive": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-directive/-/mdast-util-directive-3.1.0.tgz",
+      "integrity": "sha512-I3fNFt+DHmpWCYAT7quoM6lHf9wuqtI+oCOfvILnoicNIqjh5E3dEJWiXuYME2gNe8vl1iMQwyUHa7bgFmak6Q==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "@types/unist": "^3.0.0",
+        "ccount": "^2.0.0",
+        "devlop": "^1.0.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0",
+        "parse-entities": "^4.0.0",
+        "stringify-entities": "^4.0.0",
+        "unist-util-visit-parents": "^6.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
     "node_modules/mdast-util-find-and-replace": {
       "version": "3.0.2",
       "resolved": "https://registry.npmjs.org/mdast-util-find-and-replace/-/mdast-util-find-and-replace-3.0.2.tgz",
@@ -5620,6 +5634,25 @@
         "micromark-util-types": "^2.0.0"
       }
     },
+    "node_modules/micromark-extension-directive": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-directive/-/micromark-extension-directive-4.0.0.tgz",
+      "integrity": "sha512-/C2nqVmXXmiseSSuCdItCMho7ybwwop6RrrRPk0KbOHW21JKoCldC+8rFOaundDoRBUWBnJJcxeA/Kvi34WQXg==",
+      "license": "MIT",
+      "dependencies": {
+        "devlop": "^1.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-factory-whitespace": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0",
+        "parse-entities": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
     "node_modules/micromark-extension-gfm": {
       "version": "3.0.0",
       "resolved": "https://registry.npmjs.org/micromark-extension-gfm/-/micromark-extension-gfm-3.0.0.tgz",
@@ -6609,7 +6642,6 @@
       "resolved": "https://registry.npmjs.org/react/-/react-19.2.3.tgz",
       "integrity": "sha512-Ku/hhYbVjOQnXDZFv2+RibmLFGwFdeeKHFcOTlrt7xplBnya5OGn/hIRDsqDiSUcfORsDC7MPxwork8jBwsIWA==",
       "license": "MIT",
-      "peer": true,
       "engines": {
         "node": ">=0.10.0"
       }
@@ -6619,7 +6651,6 @@
       "resolved": "https://registry.npmjs.org/react-dom/-/react-dom-19.2.3.tgz",
       "integrity": "sha512-yELu4WmLPw5Mr/lmeEpox5rw3RETacE++JgHqQzd2dg+YbJuat3jH4ingc+WPZhxaoFzdv9y33G+F7Nl5O0GBg==",
       "license": "MIT",
-      "peer": true,
       "dependencies": {
         "scheduler": "^0.27.0"
       },
@@ -6885,6 +6916,22 @@
         "url": "https://opencollective.com/unified"
       }
     },
+    "node_modules/remark-directive": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/remark-directive/-/remark-directive-4.0.0.tgz",
+      "integrity": "sha512-7sxn4RfF1o3izevPV1DheyGDD6X4c9hrGpfdUpm7uC++dqrnJxIZVkk7CoKqcLm0VUMAuOol7Mno3m6g8cfMuA==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "mdast-util-directive": "^3.0.0",
+        "micromark-extension-directive": "^4.0.0",
+        "unified": "^11.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
     "node_modules/remark-gfm": {
       "version": "4.0.1",
       "resolved": "https://registry.npmjs.org/remark-gfm/-/remark-gfm-4.0.1.tgz",
@@ -6903,6 +6950,15 @@
         "url": "https://opencollective.com/unified"
       }
     },
+    "node_modules/remark-github-beta-blockquote-admonitions": {
+      "version": "3.1.2",
+      "resolved": "https://registry.npmjs.org/remark-github-beta-blockquote-admonitions/-/remark-github-beta-blockquote-admonitions-3.1.2.tgz",
+      "integrity": "sha512-4t5uhMnhXp9/B0RdI+seIO8v9KCsOcoua+7MX5naDq2RTJDr4VsRZ8RgB0URCATvLlayoAl0rAU/SxFpcuna4g==",
+      "license": "Apache-2.0",
+      "dependencies": {
+        "unist-util-visit": "^5.0.0"
+      }
+    },
     "node_modules/remark-mdx": {
       "version": "3.1.1",
       "resolved": "https://registry.npmjs.org/remark-mdx/-/remark-mdx-3.1.1.tgz",
@@ -7334,8 +7390,7 @@
       "version": "4.1.18",
       "resolved": "https://registry.npmjs.org/tailwindcss/-/tailwindcss-4.1.18.tgz",
       "integrity": "sha512-4+Z+0yiYyEtUVCScyfHCxOYP06L5Ne+JiHhY2IjR2KWMIWhJOYZKLSGZaP5HkZ8+bY0cxfzwDE5uOmzFXyIwxw==",
-      "license": "MIT",
-      "peer": true
+      "license": "MIT"
     },
     "node_modules/tapable": {
       "version": "2.3.0",
@@ -7952,6 +8007,7 @@
       "os": [
         "aix"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -7968,6 +8024,7 @@
       "os": [
         "android"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -7984,6 +8041,7 @@
       "os": [
         "android"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8000,6 +8058,7 @@
       "os": [
         "android"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8016,6 +8075,7 @@
       "os": [
         "darwin"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8032,6 +8092,7 @@
       "os": [
         "darwin"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8048,6 +8109,7 @@
       "os": [
         "freebsd"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8064,6 +8126,7 @@
       "os": [
         "freebsd"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8080,6 +8143,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8096,6 +8160,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8112,6 +8177,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8128,6 +8194,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8144,6 +8211,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8160,6 +8228,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8176,6 +8245,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8192,6 +8262,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8208,6 +8279,7 @@
       "os": [
         "linux"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8224,6 +8296,7 @@
       "os": [
         "netbsd"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8240,6 +8313,7 @@
       "os": [
         "netbsd"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8256,6 +8330,7 @@
       "os": [
         "openbsd"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8272,6 +8347,7 @@
       "os": [
         "openbsd"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8288,6 +8364,7 @@
       "os": [
         "openharmony"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8304,6 +8381,7 @@
       "os": [
         "sunos"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8320,6 +8398,7 @@
       "os": [
         "win32"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8336,6 +8415,7 @@
       "os": [
         "win32"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8352,6 +8432,7 @@
       "os": [
         "win32"
       ],
+      "peer": true,
       "engines": {
         "node": ">=18"
       }
@@ -8362,6 +8443,7 @@
       "integrity": "sha512-HyNQImnsOC7X9PMNaCIeAm4ISCQXs5a5YasTXVliKv4uuBo1dKrG0A+uQS8M5eXjVMnLg3WgXaKvprHlFJQffw==",
       "hasInstallScript": true,
       "license": "MIT",
+      "peer": true,
       "bin": {
         "esbuild": "bin/esbuild"
       },
@@ -8532,7 +8614,6 @@
       "resolved": "https://registry.npmjs.org/zod/-/zod-3.25.76.tgz",
       "integrity": "sha512-gzUt/qt81nXsFGKIFcC3YnfEAx5NkunCfnDlvuBSSFS02bcXu4Lmea0AFIUwbLWxWPx3d9p8S5QoaujKcNQxcQ==",
       "license": "MIT",
-      "peer": true,
       "funding": {
         "url": "https://github.com/sponsors/colinhacks"
       }
diff --git a/package.json b/package.json
index f85cf14..666fdd1 100644
--- a/package.json
+++ b/package.json
@@ -31,6 +31,8 @@
     "lucide-react": "^0.562.0",
     "react": "^19.2.3",
     "react-dom": "^19.2.3",
+    "remark-directive": "^4.0.0",
+    "remark-github-beta-blockquote-admonitions": "^3.1.2",
     "tailwind-merge": "^3.4.0",
     "tailwindcss": "^4.1.18"
   },
diff --git a/public/images/black_beard.png b/public/images/black_beard.png
new file mode 100644
index 0000000..33d1453
Binary files /dev/null and b/public/images/black_beard.png differ
diff --git a/public/images/black_beard_thumbnail.png b/public/images/black_beard_thumbnail.png
new file mode 100644
index 0000000..2099087
Binary files /dev/null and b/public/images/black_beard_thumbnail.png differ
diff --git a/public/images/puppeteer.png b/public/images/puppeteer.png
new file mode 100644
index 0000000..376ddfe
Binary files /dev/null and b/public/images/puppeteer.png differ
diff --git a/src/components/ProjectEntryCard.astro b/src/components/ProjectEntryCard.astro
index fbc10c9..2b2c178 100644
--- a/src/components/ProjectEntryCard.astro
+++ b/src/components/ProjectEntryCard.astro
@@ -10,7 +10,7 @@
 //   } from "@/components/ui/card";
 import { Card, CardContent, CardHeader, CardDescription, CardTitle, CardFooter } from '@/components/ui/card'
 import { Button } from "@/components/ui/button";
-const { title, pubDate, description, url, thumbnail, technologies } = Astro.props;
+const { title, pubDate, description, url, projURL, thumbnail, technologies } = Astro.props;
 ---
 <div class="flex items-center rounded-lg">
   <img
@@ -19,20 +19,20 @@ const { title, pubDate, description, url, thumbnail, technologies } = Astro.prop
     class="h-full w-50 object-cover rounded-none shrink-0 bg-destructive-foreground"
   />
 
-  <Card className="flex-1 bg-card rounded-none border-0 shadow-none bg-card border-0 border-b-4 border-slate-600 shadow-xl shadow-black/20">
-    <CardHeader className="p-0 pl-4">
-      <CardTitle>{title}</CardTitle>
-      <CardDescription>{pubDate}</CardDescription>
+  <Card className="h-full flex-1 bg-card rounded-none border-0 shadow-none bg-card border-0 border-b-4 border-slate-600 shadow-xl shadow-black/20 gap-0 p-0">
+    <CardHeader className="space-y-1 pt-2">
+      <CardTitle className="mb-0">{title}</CardTitle>
+      <!-- <CardDescription>{pubDate}</CardDescription> -->
     </CardHeader>
 
-    <CardContent className="flex flex-col flex-1  border-0 shadow-none rounded-non">
+    <CardContent className="flex flex-col border-0 shadow-none rounded-non">
       <p>{description}</p>
-      <p class="text-xs text-muted-foreground pt-2">{technologies}</p>
+	  <img class="w-50 pt-4" src={`https://skillicons.dev/icons?i=${technologies.join(",")}`} />
     </CardContent>
 
-    <CardFooter className="mt-auto gap-3">
+    <CardFooter className="mt-auto gap-3 pt-4">
         <Button size="sm">
-            <a href={url}>Explore The Project</a>
+            <a href={projURL}>Explore The Project</a>
         </Button>
 
         <Button size="sm" variant="outline">
diff --git a/src/content/project/0.kwin-project-intro/index.md b/src/content/project/0.kwin-project-intro/index.md
deleted file mode 100644
index c9e8d60..0000000
--- a/src/content/project/0.kwin-project-intro/index.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: GSoC 2025 Project Blog Intro - Improving Game Controller Support in KWin
-authors:
-  -  yorisoft
-date: 2025-05-12
-description: project description - foo
-url: https://foo.co
-thumbnail: https://foo.png
-technologies: 
-    - cpp
-    - java
-    - go
-    - python 
-    - qt
-    - cmake
----
-
-# Hello KDE Community! 
-
-My name is Yelsin ['yorisoft'](https://invent.kde.org/yorisoft) Sepulveda. I'm an engineer with experience in DevOps, and Cloud Computing. I joined KDE as part of the GSoC application process early last month and have been contributing to a few projects ever since. Miraculously, my GSoC proposal has been selected! ❤️ *Hallelujah!* Which means over this summer **I'll be working on implementing game controller input recognition into KWin.**
-
-## About the Project
-
-Currently, applications directly manage controller input, leading to inconsistencies, the inability of the system to recognize controller input for power management, and unintentionally enabling/disabling "lizard mode" in certain controllers. This project proposes a solution to unify game controller input within KWin by capturing controller events, creating a virtual controller emulation layer, and ensuring proper routing of input to applications. This project aims to address the following issues:
-- **System Power Management**: KWin lacks controller input recognition, preventing activity reporting and causing premature system sleep.
-- **"Lizard Mode"**: When KWin opens a file descriptor for certain gaming controller devices (like the Steam Controller and Steam Deck Controller), this disables those controllers' lizard mode (keyboard and mouse input emulation), since the controller detects that a program is now handling input?even if KWin isn't actively using it.
-- **Decentralized Input Handling**: Individual application input handling results in inconsistent input parsing and limited remapping capabilities.
-
-## Project Goals
-
-The primary goals of this project are to:
-- Enable KWin to capture and process game controller input events.
-- Implement a virtual controller emulation layer within KWin.
-- Route physical controller input 1:1 to emulated devices, including haptics.
-- Prevent system sleep during active controller use.
-- Manage "lizard mode" for compatible controllers.
-- Establish a foundation for future features: global remapping, haptics settings, and advanced Wayland protocols.
-
-## About Me
-
-I often spend my time surfing the internet learning new things, spending quality time with family and friends, or picking up new hobbies and skills-such as music! You could say I'm someone who likes to jump between multiple hobbies and interests. As of late, I'm learning a new [snare solo](https://youtu.be/q887A3B0tZQ?si=WNsSR2d4Me2TTU3o) and how to build an online brand.
-
-I started my career as a DevOps Engineer and SRE where I learned tools like Jenkins, Docker, and Terraform. I then transitioned to a Solutions Architect role where I worked with many different cloud technologies and helped other companies design their cloud architecture. I am relatively new to contributing to open-source projects but have been an avid user of Linux and open-source tools for over 4 years, and am committed to learning and growing in this community. Check me out on [GitHub](https://github.com/Yorisoft).
diff --git a/src/content/project/1.kwin-project-week-1-2/index.md b/src/content/project/1.kwin-project-week-1-2/index.md
deleted file mode 100644
index 238e664..0000000
--- a/src/content/project/1.kwin-project-week-1-2/index.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: "GSoC'25 Kwin Project Blog Post: Week 1-2"
-authors:
-  -  yorisoft
-date: 2025-06-24
-description: project description foo
-url: https://foo.co
-thumbnail: /images/games.svg
-technologies: 
-    - cpp
-    - java
-    - go
-    - python 
-    - qt
-    - cmake
----
-
-These past few week’s my focus was on exploring input device detection and event handling mechanisms in Linux, with a particular emphasis on game controllers and their potential integration into KWin. 
-I also spent time reading through KWin’s input-related source code to understand how it currently manages devices, and began reviewing documentation for various Linux input subsystems—including `evdev`, HID, and `/dev/input/jsX` in order to evaluate which layer would provide the most reliable and straight forward support for integrating controller recognition. 
-The time was mostly spent learning how to use different libraries, tools and creating virtual controller prototype. 
-
-
-## Tools, Libraries, and Concepts Used
-
-### libevdev
-
-`libevdev` is a library for handling `evdev` devices. 
-It provides a higher-level interface over `/dev/input/event*` and abstracts much of the complexity of input event parsing.
-> `evdev` is the generic input event interface. This is the preferred interface for userspace to consume user input, and all clients are encouraged to use it. 
-> 
-> -The kernel development community.
-
-`libevdev` can be used to:
-- Detect physical game controllers.
-- Read input events (e.g., joystick, buttons).
-- Create virtual input device and write/forward events to it from physical game controller.
-
-### Useful functions:
-- `libevdev_new()`, `libevdev_set_fd(int fd, struct libevdev **dev)`: for opening physical devices.
-- `libevdev_next_event(struct libevdev *dev, unsigned int flags, struct input_event *ev)`: for polling events.
-- `libevdev_get_id_*(const struct libevdev *dev)`: to query device meta data.
-
-### uinput (User Input Subsystem)
-I used the Linux **uinput** subsystem to create a **virtual input device** that mirrors a physical controller input. 
-**uinput** is what allows us to make a virtual controller out of any evdev device by:
-- Opening a file discriptor for the input device that will be emulate (i.e. have it input event forwarded).
-- Forwarding the inputs from a `evdev` interface device to `/dev/uinput` (or `/dev/input/uinput`). 
-- **uinput** then creates a new node to expose the virtual device as a `evdev` interface device in `/dev/input/event*`
-
-From here the idea is that KWin or any other system component can treat the virtual controller as if it were an ordinary HID device.
-
-> uinput is a kernel module that makes it possible to emulate input devices from userspace.
-> By writing to /dev/uinput (or /dev/input/uinput) device, a process can create a virtual input device with specific capabilities. 
-> Once this virtual device is created, the process can send events through it, that will be delivered to userspace and in-kernel consumers.
-> 
-> -The kernel development community.
-
-### Useful functions:
-- `libevdev_uinput_create_from_device(const struct libevdev *dev, int uinput_fd, struct libevdev_uinput **uinput_dev)`:  
-  For creating a uinput device based on the given libevdev device. 
-- `libevdev_uinput_get_devnode (struct libevdev_uinput *uinput_dev)`:  
- 	Return the device node representing this uinput device. 
-- `libevdev_uinput_write_event (const struct libevdev_uinput *uinput_dev, unsigned int type, unsigned int code, int value)`:
- 	Post an event through the uinput device.
-  
-  
-Tools used:
-- `libevdev-uinput.h` for management of `uinput` devices via `libevdev`.
-- `/dev/uinput` opened with correct permissions.
-    - Ensuring the current user is in the `input` group.
-    - Verifying that the `uinput` kernel module is loaded (using `modprobe uinput`). Some distros (Ubuntu/Kubuntu) have it built in, not loaded as module, thus `modprobe uinput` command won't log anything.
-    - Opening `/dev/uinput` with `O_WRONLY | O_NONBLOCK` flags using `open()`, and ensuring no `EPERM` or `EACCES` errors were returned.
-    - Optional: Run program as sudo user.
-
-### force feedback detection/support
-
-Using `ioctl(fd, EVIOCGBIT(EV_FF, ...))` and tools like `fftest`, I examined:
-
-- How to query a device’s force feedback (FF) capabilities to figure out which effects are supported (e.g., rumble, sine wave).
-- How to upload ff effects to physical game controller and test rumble motors.
-    - This was key to understanding haptic capability support on physical devices. 
-
-> To enable force feedback, you have to:
-> 
-> have your kernel configured with evdev and a driver that supports your device.
-> 
-> make sure evdev module is loaded and /dev/input/event* device files are created.
-
-
-### Testing & Validation
-- Used `evtest` and `fftest`to test evdev devices and understand their capabilities - 
- `sudo evtest /dev/input/eventX`.
-- Used those same tools to test virtual devices creating using uinput -  
-`sudo fftest dev/input/eventX`. uinput creates a node device in `dev/input/eventX` for the virtual input.
-- Prototype logs validate that a virtual device can be created and events can properly be written to a that virtual device using `libevdev`.
-
----
-
-### **Takeaways**
-
-- Using `libevdev` and `libevdev-uinput` we can access physical controllers, create virtual controller and read/write low-level input events.
-- Understanding of the permission requirements to open `/dev/input/*` and `/dev/uinput` (use `udev` rules or run as root).
-- Tools to test:
-    - `evtest` and `fftest` (from `input-utils`)
-    - `udevadm info --name=/dev/input/eventX --attribute-walk`
-        - Shows the device hierarchy - how the device is connected to PC and any parent device it connects to.
-- Built a minimal proof-of-concept C++ program that routes an evdev devices input 1:1 to a virtual controller (via uinput).
-- Not all controllers support all force feedback types; some failed with `EINVAL` during upload.
-- `libevdev` does not handle FF upload directly — this remains kernel-level and typically involves `ioctl()`.
-
-
-### References and Documentation
-- **[Linux Input Subsystem Documentation](https://www.kernel.org/doc/html/latest/input/index.html) (kernel-level overview of evdev, HID, uinput, etc.)**
-- **[evdev interface documentation](https://www.kernel.org/doc/html/latest/input/event.html) (from the kernel source)**
-- **[uinput](https://www.kernel.org/doc/html/latest/input/uinput.html): User-level input device emulation**
-- **[Force Feedback programming on Linux](https://www.kernel.org/doc/html/latest/input/ff.html) (FF effect types and ioctl usage)**
-- **[libevdev](https://www.freedesktop.org/software/libevdev/doc/latest/) (Userspace abstraction for evdev devices)**
diff --git a/src/content/project/2.kwin-project-week-3-4/index.md b/src/content/project/2.kwin-project-week-3-4/index.md
deleted file mode 100644
index b05217a..0000000
--- a/src/content/project/2.kwin-project-week-3-4/index.md
+++ /dev/null
@@ -1,228 +0,0 @@
----
-title: "GSoC'25 KWin Project Blog Post: Week 3-4"
-discourse: yorisoft
-authors:
-  -  yorisoft
-date: 2025-09-15
-description: project description foo
-url: https://foo.co
-thumbnail: /images/kwin_plugin_gamepad_architecture_diagram_3.png
-technologies: 
-    - cpp
-    - java
-    - go
-    - python 
-    - qt
-    - cmake
----
-
-# KWin::Plugin::GamePadManager
-
-Picking up from weeks 1+2 ( research + prototypes with libevdev/uinput ), these two past weeks were about moving from “research-only mode” to turning ideas into programming logic that lives inside KWin to: detect gaming controllers and their input events, keeps Plasma awake on controller activity, handles hot-plug and pre-existing connections on startup, and lays down the first mappings from controller input to keyboard/mouse actions without stepping on other apps utilizing the controllers.
-
-From the start my mentors and I have had a general idea of the features we wanted to add but weren't too sure how to implement them. After some thinking and experimenting they advised me to start off with a KWin::Plugin. This would allow us to start introducing the gaming controller functionalities to KWin while avoiding having to edit the core or guts of KWin. It would also be a great entry point for current and future game controller input objectives, allowing us to start small with a 1st party KWin plugin, build on it, and possibly integrate it into core functionality. 
-
-When it comes to creating KWin plugins I had a few options:
-- Scripts: Written in QML/JavaScript and used for automating window management, tiling, shortcuts, etc.
-- Effects: Implement visual effects on windows, the desktop, or transitions.
-- Core/Native: These are built into KWin itself and extend KWin’s internal functionality.
-
-Since the plugin needs low-level device access, such as monitoring `/dev/input/event*`, listening to `udev` hotplugs, opening fds, and reacting to `evdev` events the best choice was to go with Core / Native plugin. As opposed to Effect and Script plugins which aren’t designed to open devices or do long-running I/O, most simply just live inside the rendering/scripting layers. 
-
-
-I started off by searching for an example of how to build a KWin plugin so I could start learning how to build my own. Thankfully my mentor @zamundaaa provided me with some great examples:
-- Example / Tutorial plugin located in `src/plugin/examples/plugin`
-- Screenshots plugin located in `src/plugins`
-
-Between both of these examples and mentoring I was able to piece together the scaffolding ( essential parts ) of a KWin plugin and was able to put together the first version of this plugin, `gamepad` plugin, located in: `kwin/src/plugins/gamepad`. At this point the plugin is structured as follows: 
-```
-main.cpp                // Entry point & Defines GamepadManagerFactory Class
-metadata.json           // Declares the plugin to KWin, define information about plugin
-CMakeLists.txt          // C++ Build/Installation/Logging wiring
-gamepadManager.{cpp/h}  // Plugin Logic: Defines GamepadManager Class
-gamepad.{cpp/h}         // Game Controller Object: Wrapper Class for Physical Controller
-```
-
-## Implementation notes  
-
-### GamepadManagerFactory  
-`GamepadManagerFactory` Class serves simply as the entry point for the plugin. It's a factory class, or a class used to create other classes / object types. Like the examples, it inherits from `PluginFactory` and declares it as its interface as well as pointing to the `metadata.json` file for this plugin. It initializes the plugin through its `create()` function which returns a `GamepadManager`.  
-  
-  
-### GamepadManager  
-`GamepadManager` class serves as the central coordinator (the “brain” or “hub”) of the entire project. While creating this I took a lot of inspiration from `src/backend/drm/drm_backend.{cpp/h}`, which itself is responsible for handling drm/gpu devices. `GamepadManager` covers many responsibilities. It owns and manages all gamepad devices, handles discovery (startup enumeration, hot-plug), lifecycle (adding/removing), and communication (signals when pads are added/removed, or when their state changes). Overall its responsible for keeping track of the current set of controllers and their status. 
-
-#### Detect hot-plug and pre-existing device detection:
-For this part many of the DRM backend pattern were used. The first thing the manager class does on initialization is create two `QMetaObject::Connection`s that monitor the current KWin session for `devicePaused` and `deviceResumed` signals. This helps **track devices when Plasma goes in and out of sleep/suspend** which causes devices to be Paused and Resumed. It then enumerates over all event devices located in `/dev/input/event*` to **handle any pre-existing connections to game controllers**. If it discovers an event device it adds the gamepad ( start tracking it and its input ).  
-```cpp
-// On init:
-// Enumerate current input nodes to filter and add ONLY event nodes
-QDir dir(QStringLiteral("/dev/input"));
-const auto files = dir.entryList({QStringLiteral("event*")}, QDir::Files | QDir::Readable | QDir::System);
-for (const QString &file : files) {
-    const QString path = dir.absoluteFilePath(file);
-    if (!isTracked(path)) {
-        addGamepad(path);
-    }
-}
-```
-  
-  
-  
-Finally using `udev` it monitors the subsystems and filter for only "input" subsystem events. It uses `QSocketNotifier` to produce signal notifications from `udev` events and creates a connections between that notifier and a memeber function, `handleUdevEvent`, that handles events coming from the `udev` monitor when an input device is detecetd. Some checks are performed to verify if the device is a gaming controller, such as expected input events and input event types. This include input events like `BTN_JOYSTICK` and `BTN_GAMEPAD`, which are commonly defined in gaming controllers. As well as checking for joystick or D-pad capabilities. If the checks pass the game controller is "added", or in other words, the device is wrapped in a `Gamepad` class, kept track of and its presence monitored.
-```cpp
-// setup udevMonitor
-if (m_udevMonitor) {
-    m_udevMonitor->filterSubsystemDevType("input");
-    const int fd = m_udevMonitor->fd();
-    if (fd != -1) {
-        m_socketNotifier = std::make_unique<QSocketNotifier>(fd, QSocketNotifier::Read);
-        connect(m_socketNotifier.get(), &QSocketNotifier::activated, this, &GamepadManager::handleUdevEvent);
-        m_udevMonitor->enable();
-    }
-}
-```
-
-  
-### Gamepad  
-`Gamepad` is a wrapper class. It's purpose is to be tied to a physical controller. One `Gamepad` object per physical game controller. This enables quick access/reference to the device and allows for the physical controller to be treated like an object. This class is also responsible for device input handling, Plasma Idle refresh, and button to keyboard/mouse mappings. In the future things might get split up into seperate files but as it is, it handles a lot. As with the `GamepadManager`, this class takes a lot of inspiration from DRM backend patterns. 
-
-#### Detect Input Events:
-Once a gaming controller device is detected it gets wrapped in a `Gamepad` class object. Which in turn wraps the controller in a `libevdev` object pointer.  This is the part that gives access to the controller through the `libevdev` API, making it easier to work with it and monitor its input events. Like `GamepadManager` the first thing this class does is use `QSocketNotifier` to produce notifications from the controllers `fd`, i.e monitor for input. It then creates a connections between that notifier and a member function, `handleEvdevEvent`, which **handles all incoming input events from that device**.
-```cpp
-libevdev *evdev = createEvDevice();
-if (evdev) {
-    m_evdev.reset(evdev);
-
-    m_notifier = std::make_unique<QSocketNotifier>(m_fd, QSocketNotifier::Read, this);
-    connect(m_notifier.get(), &QSocketNotifier::activated, this, &Gamepad::handleEvdevEvent);
-
-    qCDebug(KWIN_GAMEPAD) << "Connected to Gamepad ( new libevdev* ): " << libevdev_get_name(m_evdev.get()) << "at" << m_path;
-}
-```  
-  
-  
-#### Plasma Idle Refresh On Controller Activity  
-With the ability to monitor for all input events from the device, the plugin then uses that information to know when to reset Plasma idle timer. For this `Gamepad` imports/includes `input.h` file and makes a call to `input()->simulateUserActivity()` when an input event is detected from the controller. This causes Plasma idle timer to be reset and **prevents the system from going into sleep/suspend mode while using only gaming controller**.  
-```cpp
-// reset idle time
-input()->simulateUserActivity();
-```  
-
-  
-#### Controller -> Keyboard & Mouse Mapping
-`Gamepad` uses API function from `libevdev` to check for input events, identify the specific input event and map that to a keyboard or mouse input event. Using `libevdev_next_event()` it checks for the input event coming from that game controller. It then identifies the specific input event through its input event `type`, `code`, and `value`. To simulate a mouse and keyboard the `core/inputdevice.h` file is imported and used to declare `GenericInputDevice` which inherits from `InputDevice`. That `GenericInputDevice` effectively behaves like a virtual keyboard and mouse inside KWin’s input stack.  
-
-When specific `libevdev` input event are identified, such as `EV_KEY` + `BTN_SOUTH` ( A button press ) OR `EV_KEY` + `BTN_EAST` ( B button press ), it  call `InputDevice::sendKey()` to **simulate keyboard key press and inject the desired keys into KWin input pipeline**. In this case `Enter` for A ( `BTN_SOUTH` ) and `Escape` for B ( `BTN_EAST` ). To emulate mouse/pointer the plugin makes calls to `InputDevice::sendPointerButton()` for left and right mouse buttons, and `InputDevice::sendPointerMotionDelta()` for pointer movement.  
-
-![architecture_diagram_0](/images/kwin_plugin_gamepad_architecture_diagram_0.png) 
-![architecture_diagram_1](/images/kwin_plugin_gamepad_architecture_diagram_1.png) 
-![architecture_diagram_2](/images/kwin_plugin_gamepad_architecture_diagram_2.png) 
-![architecture_diagram_3](/images/kwin_plugin_gamepad_architecture_diagram_3.png) 
-
-Here is a list of all the buttons to keyboard/mouse mappings:  
-```
-Face Buttons
-------------
-BTN_SOUTH  → Enter (Qt::Key_Return)
-BTN_EAST   → Escape (Qt::Key_Escape)
-BTN_NORTH
-BTN_WEST
-
-Bumpers
--------
-BTN_TL     → Alt (Qt::Key_Alt)
-BTN_TR     → Tab (Qt::Key_Tab)
-
-Trigger Buttons
----------------
-ABS_Z      → Mouse Left Click
-ABS_RZ     → Mouse Right Click
-
-D-Pad
------
-BTN_DPAD_LEFT   → Arrow Left  (Qt::Key_Left)
-BTN_DPAD_RIGHT  → Arrow Right (Qt::Key_Right)
-BTN_DPAD_UP     → Arrow Up    (Qt::Key_Up)
-BTN_DPAD_DOWN   → Arrow Down  (Qt::Key_Down)
-
-Analog Sticks
--------------
-ABS_RX / ABS_RY → Pointer Motion
-
-Center Buttons
---------------
-BTN_SELECT → Show On-Screen Keyboard ( WIP )
-BTN_START  → Meta/Super (Qt::Key_Meta)
-
-```
-
-#### Prevent Stepping On Other Apps
-It's essential that the plugin doesn't emulate keyboard and mouse for the gaming controller when another app is reading from it. Most likely in such cases the device is being used for something else and not being used to navigate the desktop. To achieve this the `GamepadManager` class creates an instance of `inotify` object, and adds a `watch device` to the `fd` of each game controller that’s added as a `Gamepad`. Whenever `inotify` produces a notification a function, `GamepadManager::handleFdAccess`, is called which increments a counter in `Gamepad`,  `Gamepad::m_usageCount` by +1 if the event value is `IN_OPEN` or `Gamepad::m_usageCount` by -1 if the event value is `IN_CLOSE_WRITE | IN_CLOSE_NOWRITE`. The plugin will only attempt to emualte keyboard/mouse if `m_usageCount` is 0. This **prevents emulation of keyboard and mouse when other apps have the game controller opened / in use**.
-```cpp
-// Process all inotify events in the buffer
-for (char *ptr = buffer; ptr < buffer + length;) {
-    struct inotify_event *event = reinterpret_cast<struct inotify_event *>(ptr);
-
-    auto it = m_watchesToGamepads.find(event->wd);
-    if (it != m_watchesToGamepads.end()) {
-        Gamepad *pad = it.value();
-        if (event->mask & IN_OPEN) {
-            pad->countUsage(+1);
-        } else if (event->mask & (IN_CLOSE_WRITE | IN_CLOSE_NOWRITE)) {
-            pad->countUsage(-1);
-        }
-        qCDebug(KWIN_GAMEPAD) << "Device" << pad->path() << "in use by:" << pad->usageCount() << " other apps";
-    }
-    ptr += sizeof(struct inotify_event) + event->len;
-}
-```  
-  
-  
-#### Opt-In
-Many of the native plugins that ship with KWin are enabled by default but for our gaming controller plugin we will disable it by default and make it an opt-in option. This will allow users to start experimenting and benefiting from the plugin without risking the possibility of breaking current game controller input on their system.
-```json
-{
-    "KPlugin": {
-        "Category": "Input",
-        "Description": "Enable KWin game controller input detection",
-        "EnabledByDefault": false,     <---------- Not enabled by default. 
-        "License": "GPL",
-        "Name": "gamepad"
-    },
-    "X-KDE-ServiceTypes": ["KWin/Plugin"]
-}
-```
-   
-  
-   
-## Testing
-- Controller awareness at startup and hot-plugging: tested in development session, KWin logs show the plugin picking up controllers in both scenarios, works as expected. 
-- Preventing sleep/suspend: tested in development session. Set suspend timer to 1min, repeatedly press A and B back and forth, and at 5min no suspend was initiated, works as expected.  
-- USB and Bluetooth connectivity support: tested in development session, KWin logs show plugin picking up on the controllers in both scenarios, works as expected. 
-- Mapping from controller to keyboard and mouse: tested in development session, all buttons are map to expected keyboard and mouse, works as expected. 
-- Backoff On Grab: tested in development session. Verified mapping work, started Steam app, verify mapping no longer enabled. 
-
-Testing device: 8Bitdo Gaming Controller (USB/2.4h/Bluetooth)
-  
-   
-   
-#### What’s next from here
-- Integration into KWin Proper: Start pushing changes upstream for others to test.
-- Map to Virtual Keyboard: Allow users to navigate over and get input from a virtual keyboard. Might open the way for logging in using only game controller.  
-- Test Cases: As per best practices when developing for KWin.
-- KCM integration: A GUI option for users to toggle plugin ON/OFF. Ground work for more robust, user defined, button remapping. 
-- Use Config for Mapping: Using a config file to keep track of and read from all the button to keyboard/mouse button mapping. 
-
-
-#### Reference documentation:
-- Example / Tutorial KWin Plugin: https://invent.kde.org/plasma/kwin/-/tree/master/examples/plugin
-- Screenshots KWin Plugin: https://invent.kde.org/plasma/kwin/-/tree/33262fef1a6e4e3bcebc05181edbde2d9a72f38c/src/plugins/screenshot
-- DRM Backend: https://invent.kde.org/yorisoft/kwin/-/tree/master/src/backends/drm/drm_backend.cpp
-- Linux Input Subsystem (overview): https://www.kernel.org/doc/html/latest/input/index.html
-- Libevdev Library: https://www.freedesktop.org/software/libevdev/doc/latest/
-- Udev Library: https://man7.org/linux/man-pages/man7/udev.7.html
-- Inotify Library: https://man7.org/linux/man-pages/man7/inotify.7.html
-
-Checkout the source code here:
-KWin Gamepad Plugin: https://invent.kde.org/yorisoft/kwin/-/tree/work/yorisoft/gamepad-plugin/src/plugins/gamepad
diff --git a/src/content/project/black-beard/index.md b/src/content/project/black-beard/index.md
new file mode 100644
index 0000000..a5a62d9
--- /dev/null
+++ b/src/content/project/black-beard/index.md
@@ -0,0 +1,142 @@
+---
+title: "Black Beard"
+discourse: yorisoft
+authors:
+  -  yorisoft
+date: 2017-04-22
+description: Care Taking App for Bearded Dragon Lizards built for  Android
+url: https://github.com/Yorisoft/Black-Beard
+thumbnail: https://m.media-amazon.com/images/I/41axBUKxNLL.png
+technologies: 
+    - java
+    - android
+    - firebase
+    - androidstudio 
+---
+# 🦎 Black Beard: Lizard Care Taking Android App
+
+![Android](https://m.media-amazon.com/images/I/6156EObZC3L.png)
+
+[Amazon App Store](https://www.amazon.com/Yorisoft-Black-Beard/dp/B0717591CF)
+
+> **By a Bearded Dragon Owner, For Bearded Dragon Owners**
+
+<div style="display:flex; justify-content:center; gap:12px; flex-wrap:wrap;">
+  <img src="https://img.shields.io/badge/Android-3DDC84?style=for-the-badge&logo=android&logoColor=white" />
+  <img src="https://img.shields.io/badge/Java-ED8B00?style=for-the-badge&logo=openjdk&logoColor=white" />
+  <img src="https://img.shields.io/badge/Firebase-FFCA28?style=for-the-badge&logo=firebase&logoColor=black" />
+  <img src="https://img.shields.io/badge/Material%20Design-757575?style=for-the-badge&logo=material-design&logoColor=white" />
+</div>
+
+<div style="display:flex; justify-content:center; gap:12px; margin-top:8px; flex-wrap:wrap;">
+  <img src="https://img.shields.io/badge/Min%20SDK-16-blue" />
+  <img src="https://img.shields.io/badge/Target%20SDK-25-green" />
+  <img src="https://img.shields.io/badge/License-MIT-yellow" />
+</div>
+
+---
+
+## 🐉 What is Black Beard?
+
+**Black Beard** is an Android app designed to help bearded dragon owners care for their scaly companions with confidence. Owning an exotic pet comes with a steep learning curve — from setting up the perfect enclosure to understanding common behaviors. Black Beard puts trusted care knowledge in your pocket and helps you stay organized.
+
+Whether you're a first-time reptile owner or a seasoned keeper, Black Beard simplifies exotic pet care and daily routines.
+
+---
+
+## 💡 Why Black Beard?
+
+The reptile community has always been incredibly generous, sharing knowledge through blogs, forums, and videos. Black Beard was created to give back by consolidating trusted information into one easy-to-use app.
+
+All guidance in the app comes from extensive research and personal experience caring for bearded dragons, using sources long trusted by the community.
+
+---
+
+## ✨ Features
+
+### 📋 Pet Profile & Tracking
+Create a personalized profile and stay on top of important care activities:
+
+| Feature | Description |
+|--------|-------------|
+| Pet Profile | Store name, photo, age, weight, length, and gender |
+| Bath Tracking | Log baths and receive reminders |
+| Feeding Schedule | Track meals and diet routines |
+| Shedding Log | Monitor shedding cycles |
+| Bowel Movements | Track digestive health |
+| UVB Bulb Tracking | Get reminders for UVB replacement |
+| Vet Visit History | Record veterinary appointments |
+
+### 📚 Care Guide
+A pocket reference packed with essential knowledge:
+
+- Enclosure setup
+- Food and diet by life stage
+- Handling tips and bonding
+- Behavior guide:
+  - Black beard
+  - Arm waving
+  - Head bobbing
+  - Licking
+  - Mouth gaping
+  - Brumation
+- Extra tips including vet visits, lifespan expectations, and insect breeding
+
+### 🎯 Designed for Real Owners
+- Onboarding slider for quick setup
+- Intuitive navigation
+- Offline access to care information
+
+---
+
+## 🎨 Screenshots
+
+![Android](https://m.media-amazon.com/images/I/71lUo80RnUL.png)
+![Android](https://m.media-amazon.com/images/I/51WJBQY0C2L.png)
+![Android](https://m.media-amazon.com/images/I/8112vTdm1XL.png)
+![Android](https://m.media-amazon.com/images/I/81Nf68YI7TL.png)
+
+---
+
+## 🛠️ Built With
+
+- Language: Java  
+- Platform: Android (Min SDK 16 / Target SDK 25)  
+- Image Loading: Glide  
+- Analytics: Firebase  
+- UI: Material Design Components  
+- Data Storage: SharedPreferences  
+
+---
+
+## 🔮 Roadmap
+
+- Multiple pet profiles
+- Premium features
+- Smart notifications
+- Health journal with charts
+
+---
+
+## 📖 Resources & Credits
+
+- The Bearded Dragon  
+- BeardedDragon.org  
+- Bearded Dragon Care 101  
+- Pet Education  
+
+**YouTube Channels**
+- Raising Reptiles  
+- Michel Behrends  
+- Earthling1984  
+- DaltonsDragons  
+
+---
+
+## 📄 License
+
+MIT License — see the [LICENSE](LICENSE) file for details.
+
+<p align="center">
+  Made with ❤️ for the reptile community
+</p>
diff --git a/src/content/project/puppet-purchase/index.md b/src/content/project/puppet-purchase/index.md
new file mode 100644
index 0000000..b86535c
--- /dev/null
+++ b/src/content/project/puppet-purchase/index.md
@@ -0,0 +1,98 @@
+---
+title: "Puppet-Purchase: Auto Purchase Scripts"
+authors:
+  -  yorisoft
+date: 2010-01-10
+description: "Automated item purchasing bots to compat scalping."
+url: https://github.com/Yorisoft/puppet-purchase
+thumbnail: /images/puppeteer.png
+technologies: 
+    - js
+    - nodejs
+    - docker
+    - jenkins
+    - shell 
+---
+
+puppet-purchase is a bot that automates the process of purchasing an item from a few of the major online retailers. In attempt to combat scalping, I've created puppet-purchase bot and am making it publicly available with you all. Not perfect, but has helped me. Please share && contribute.  
+  
+## How Does it work?  
+
+These are scripts that automate the user flow of purchasing an item.  
+That flow of purchasing an item varies a bit from website to website, but in general it is as follows:
+- Navigate to site  
+- Sign-in to the account  
+- Navigate to item listing page
+- If no is stock available:
+    Switches store and refresh page until it finds available stock.
+- Adds item to cart  
+- Checks-out cart   
+
+
+### Connecting it to your account
+
+To run these scripts, setting up an online account with one of the retailers is required. To ensure  the scripts execute with no errors, be sure to plug in your account information. Each bot uses the **.env.userInfo** file located in _**scripts/< bot >/userInfo/.env.userInfo**_ to define user specific information.
+
+> [!CAUTION] 
+> _**Do not include your payment information.**_  
+> All payment information should be setup by using your web browser, logging into the account, and adding a payment option. Not in the scripts.  
+> Avoid checking in personal account information to this project if you decide to contribute by adding _**env.userInfo**_  to  _**gitignore**_.
+> Or even better, by creating a new a _**env.**_ file and pointing to it in _**scripts/< bot >/myInfo.js**_
+
+
+## Installation
+
+To run these script use [node.js](https://nodejs.org/en/) in order to install the required node modules. Navigate to the project directory and install npm. 
+
+```node
+npm i
+```
+Because of the way that the environment variables are defined, a version of [WSL](https://docs.microsoft.com/en-us/windows/wsl/) will need to be installed on your machine if running on windows machine. Alternatively, and perhaps an easier method for some, installing [Git](https://git-scm.com/downloads) and running the program using _**Git Bash**_
+
+## Usage
+Once npm finishes installing all the required node modules, the scripts are ready to go! Try filling out the necessary account info in _**scripts/< bot >/userInfo/.env.userInfo**_, then running one of the bots to see it in action. 
+```node
+npm run target-bot
+```
+A full list of available scripts can be found in _**package.json**_. We recommend running one of the bot-test to ensure everything is working properly. 
+
+## Test
+Running one of the bot-tests is the best way of making sure that the program is properly installed and running correctly. The bot-tests _**DO NOT**_ perform the last step - clicking the 'place order' button. Bot-tests are also a great way of making sure that your account has all the required information for a speedy checkout.
+
+When running the bot-tests, test-user information will need to be added as environment variables instead of being added to _**env.userInfo**_ file. This is the list of all test-user variable 
+
+```node
+export TEST_USER_EMAIL= \
+    TEST_USER_PASSW= \
+    TEST_USER_INBOX_PASSW= \
+    TEST_USER_PHONE= \
+    TEST_USER_LOC= \
+    TEST_USER_CVV= \
+    TEST_USER_LISTING_URL= \
+```
+Use 'export' if you're on Linux or 'SET' if you're on Windows.
+
+Some environment variables are not required for all of the bot-test, such as TEST_USER_INBOX_PASSW && TEST_USER_LOC. Look inside the _**env.userInfo**_ file that pertains to the specific bot inorder to know what variables the program is expecting. 
+
+We find it easier to export all of the variables, and just change the TEST_USER_LISTING_URL variable depending on what bot-tests is we expect to run. 
+
+
+## Docker
+Alternatively, you can run the program inside a docker container. Use the _**Dockerfile**_ provided to make a docker image and then run it inside a docker container. 
+```node
+docker build -t puppet-purchase .
+docker run -p 5901:5901 -d puppet-purchase
+```
+
+## VNC
+Use [VNC Viewer](https://www.realvnc.com/en/connect/download/viewer/) to look inside the container and view the process. By default it is running on port 5901. Feel free to change the default port by editing the -p flag and the  _**Dockerfile**_
+```node
+# Inside Dockerfile, add this
+EXPOSE [new_port_number]
+```
+default password: puppeteer
+
+## Contributing
+Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
+
+Please make sure to update tests as appropriate.
diff --git a/src/content/project/redero-dex/index.md b/src/content/project/redero-dex/index.md
new file mode 100644
index 0000000..04a2a6f
--- /dev/null
+++ b/src/content/project/redero-dex/index.md
@@ -0,0 +1,167 @@
+---
+title: "RetroDex"
+authors:
+  -  yorisoft
+date: 2024-01-19
+description: A Pokedex app built from scratch for MiyooMini 
+url: https://github.com/Yorisoft/pokedex_miyoo
+thumbnail: https://github.com/user-attachments/assets/7080b6cd-66a1-4a10-88d9-bf5364bdd3cc
+technologies: 
+    - cpp
+    - cmake
+    - sqlite
+    - bash
+    - docker
+---
+#  <img align="center" width="400" src="https://github.com/user-attachments/assets/98177822-b80d-4bb4-838e-54ce235cdd4e"/>
+
+<p align="center">
+<img align="center" width="400" src="https://github.com/user-attachments/assets/7080b6cd-66a1-4a10-88d9-bf5364bdd3cc"/>
+</p>
+
+</br>
+</br>
+
+<p align="center">This app was made from scratch for the MiyooMini devices running OnionOS. The goal is to design a pokedex that targets generations 1 - 5.  </p>
+
+
+### PLEASE READ! This is not yet stable - this is a work in progress - there are bugs - install at your own peril.
+
+</br>
+
+## Install on Miyoo Mini
+
+1. Connect the Miyoo Mini device to a computer.
+    - Refer to the OnionOS wiki for the various ways to do this, e.g., FTP, Webserver, Samba, etc…
+2. Copy `App/Retrodex` to `/mnt/SDCARD/App` on the Miyoo Mini. Restart the device if it's turned off.
+3. On the Miyoo Mini, navigate to Apps list.
+    - Refresh App list by using the 'search' function - press `x`
+4. Navigate to the `Retrodex` app and launch it. 
+
+</br>
+
+## Install locally
+
+1. Install cmake: \
+   `apt-get install cmake`
+2. Install SDL2 dependencies: \
+   `apt-get install ibsdl2-dev ibsdl2-ttf-dev libsdl2-mixer-dev libsdl2-image-dev`
+3. Install sqlite amalgamation 
+   - Download [here](https://www.sqlite.org/download.html). Learn about sqlite amalgamation [here](https://www.sqlite.org/amalgamation.html)
+   - Place sqlite amalgamation folder in `Source/union-miyoomini-toolchain/workspace/retrodex/core/include/sqlite` \
+       Make sure sqlite folder contains the following
+   ```
+       sqlite
+       ├── sqlite3.h
+       └── sqlite3.c
+   ```
+4. Create a symlink from to res: 
+   ```
+   cd Source/union-miyoomini-toolchain/workspace/retrodex
+   ln -s ../../../../App/Retrodex/res res
+   ```
+   - This contains the app resource like sprites, icons, db, etc..
+5. Copy CMakeList.txt to projet dir:
+   ```
+   cp -v targets/local/CMakeLists.txt .
+   ```
+5. Run cmake: 
+   ```
+       mkdir build
+       cd build
+       cmake ..
+       make
+   ```
+6. Binary should be in `build/bin`. Copy it to `retrodex/` and run: \
+   `./retrodex`
+
+</br>
+
+## Compiling on union-miyoomini-toolchain
+
+1. Clone, navigate to `Source/union-miyoomini-toolchain`, and start the docker container for the union-miyoomini-toolchain. 
+   - Read the `README.md` located in the `Source/union-miyoomini-toolchain` directory for instructions on how to get started with union-miyoomini-toolchain, or refer to their GitHub README. [union-miyoomini-toolchain repo](https://github.com/MiyooMini/union-toolchain/tree/main)
+2. Run `mksdl2.sh` script to build SDL2 dependencies.
+    ```
+    ./mksdl2.sh
+    ```
+3. Compile the Retrodex program using the provided CMakeList and Toolchain files:
+    ```
+    cd retrodex 
+    cp -v targets/miyoo/* . 
+    mkdir build 
+    cd build 
+    cmake .. -DCMAKE_TOOLCHAIN_FILE=../Toolchain.cmake 
+    make
+    ```
+4. The executable should be located in `workspace/retrodex/build/`
+    - `retrodex`
+
+Copy `retrodex` executable to App/Retrodex for testing. 
+
+</br>
+
+### Directory Structure
+```
+# tree
+.
+├── App
+│   └── Retrodex
+└── Source
+    └── union-miyoomini-toolchain
+       ├── support
+       └── workspace
+           └── retrodex
+              ├── build
+              ├── include
+              ├── res -> symlink
+              └── target
+                   └── local
+                   └── miyoo
+```
+
+## Current Status
+
+The app is currently in the early stages. At the moment, it contains:
+- Game version menu
+- Pokedex list
+- Pokemon Views ( Basic Info, Stats, Moves, Encounters, Evolutions) 
+
+
+### The primary objective is to get a stable app with pleasent UI, more features may come in the future. 
+
+Possible Roadmap:
+- [ ] Support for animated Pokemon sprites. 
+- [ ] Support for Gen 6-9. Require collecting Gen 5 style sprites for Gen 6-9. 
+
+</br>
+</br>
+
+## Contributions, Acknowledgements
+
+Toolchain Docker Image: [union-miyoomini-toolchain](https://github.com/shauninman/union-miyoomini-toolchain).
+
+Database: [veekun_pokedex](https://github.com/veekun/veekun-pokedex).
+
+Pokemon Sprites: [pokemondb.net](https://pokemondb.net/).
+
+SDL2 Library Install Script: [XK9274](https://github.com/XK9274).
+
+Special Thanks to the folks over at #Retro Game Handhelds [Discord](https://discord.gg/retro-game-handhelds-529983248114122762)! 
+
+
+</br>
+</br>
+
+
+## Contributing
+
+Contributions are more than welcomed! 
+If you encounter any bugs or have any questions about the app, please open an issue.
+
+For code change suggestions, fork repo and create pr. 
+
+</br>
+</br>
+
+Made with :heart: and C++
diff --git a/src/pages/Projects.astro b/src/pages/Projects.astro
index c83722c..c5892aa 100644
--- a/src/pages/Projects.astro
+++ b/src/pages/Projects.astro
@@ -24,11 +24,12 @@ const projects = await getCollection('project');
           .split("T")[0]; 
 
           return (
-            <ProjectEntryCard slot="project-posts" 
+            <ProjectEntryCard slot="project-posts" client:load 
                 title={project.data.title}
                 pubDate={pubDate}
                 description={project.data.description}
                 url={`/project/${project.id.split('/')[0]}`}
+                projURL={project.data.url}
                 thumbnail={project.data.thumbnail}
                 technologies={project.data.technologies}
             />