Add Jekyll site structure and GitHub Pages deployment workflow

.github/workflows/pages-deploy.yml

@@ -0,0 +1,50 @@
+name: Build and Deploy GitHub Pages
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+
+      - name: Build with Jekyll
+        uses: actions/jekyll-build-pages@v1
+        with:
+          source: ./
+          destination: ./_site
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: ./_site
+
+  deploy:
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.pymarkdown.json

@@ -7,6 +7,14 @@
       "allowed_elements": [
         "br"
       ]
+    },
+    "md041": {
+      "enabled": false
+    }
+  },
+  "extensions": {
+    "front-matter": {
+      "enabled": true
     }
   }
 }

README.md

@@ -6,6 +6,14 @@ and fenced code blocks to improve readability and collaboration.
 
 ## Repository layout
 
+The repository now follows a GitHub Pages-friendly Jekyll content model:
+- `_docs/` for evergreen cheat sheets.
+- `_posts/` for dated blog entries.
+- `_projects/` for platform engineering case studies.
+- `index.md` as the homepage with clear paths to Cheat Sheets and Blog.
+
+Legacy topic folders remain in place during the transition and can be gradually moved or aliased into `_docs/`.
+
 Cheat sheets are organized by topic. Each directory contains one or more
 `*.md` files.
 
@@ -43,3 +51,19 @@ Markdown linting is enforced in two ways:
 Install the linter with `pip install pymarkdownlnt` or via `pre-commit`'s
 managed environments. Running the checks keeps the cheat sheets consistently
 formatted and ready for publishing.
+
+## CI/CD
+
+GitHub Actions now uses two workflows:
+
+- `Markdown lint` (`.github/workflows/markdown-lint.yml`) for Markdown quality checks on pushes and pull requests.
+- `Build and Deploy GitHub Pages` (`.github/workflows/pages-deploy.yml`) to build the Jekyll site on pull requests and deploy to GitHub Pages on pushes to `main`.
+
+## GitHub Pages domain
+
+This repository is configured to use the default GitHub Pages domain pattern (no custom `CNAME`).
+
+- User site repo URL: `https://<username>.github.io/`
+- Project site repo URL: `https://<username>.github.io/<repository>/`
+
+For this repository, expect the project-site URL pattern to apply unless it is published from a dedicated user-site repository.

_config.yml

@@ -1 +1,28 @@
-theme: jekyll-theme-architect
+title: System Engineer Cheat Sheets
+description: Practical cheat sheets, platform engineering projects, and blog updates.
+theme: jekyll-theme-architect
+
+collections:
+  docs:
+    output: true
+    permalink: /cheat-sheets/:name/
+  projects:
+    output: true
+    permalink: /projects/:name/
+
+defaults:
+  - scope:
+      path: ""
+      type: docs
+    values:
+      layout: default
+  - scope:
+      path: ""
+      type: projects
+    values:
+      layout: default
+  - scope:
+      path: ""
+      type: posts
+    values:
+      layout: default

_data/navigation.yml

@@ -0,0 +1,10 @@
+- title: Home
+  url: /
+- title: Cheat Sheets
+  url: /cheat-sheets/
+- title: Projects
+  url: /projects/
+- title: Blog
+  url: /blog/
+- title: About
+  url: /about/

_docs/getting-started.md

@@ -0,0 +1,20 @@
+---
+layout: default
+title: Getting Started with the Docs Collection
+permalink: /cheat-sheets/getting-started/
+tags:
+  - docs
+  - migration
+categories:
+  - cheat-sheets
+---
+
+# Getting Started with `_docs/`
+
+Use this collection for evergreen content that should remain stable over time.
+
+## Migration guidance
+
+1. Keep the original topic file in place initially.
+2. Create or update a canonical page in `_docs/`.
+3. Add links between old and new pages until migration is complete.

_layouts/default.html

@@ -0,0 +1,33 @@
+<!DOCTYPE html>
+<html lang="{{ site.lang | default: 'en-US' }}">
+  <head>
+    <meta charset="UTF-8">
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+    <meta name="viewport" content="width=device-width, initial-scale=1">
+    {% seo %}
+    <link rel="stylesheet" href="{{ '/assets/css/style.css' | relative_url }}">
+    <style>
+      .top-nav { margin: 1rem 0 2rem; }
+      .top-nav ul { display: flex; flex-wrap: wrap; gap: 0.8rem; list-style: none; padding: 0; margin: 0; }
+      .top-nav a { font-weight: 700; text-decoration: none; }
+    </style>
+  </head>
+  <body>
+    <header>
+      <p><a href="{{ '/' | relative_url }}">{{ site.title }}</a></p>
+      <p>{{ site.description }}</p>
+      <nav class="top-nav" aria-label="Top navigation">
+        <ul>
+          {% for item in site.data.navigation %}
+          <li><a href="{{ item.url | relative_url }}">{{ item.title }}</a></li>
+          {% endfor %}
+        </ul>
+      </nav>
+    </header>
+
+    <main id="content" role="main">
+      <h1>{{ page.title | default: site.title }}</h1>
+      {{ content }}
+    </main>
+  </body>
+</html>

_posts/2026-04-19-site-structure-update.md

@@ -0,0 +1,12 @@
+---
+layout: default
+title: Site Structure Update
+date: 2026-04-19 00:00:00 +0000
+tags:
+  - blog
+  - migration
+categories:
+  - updates
+---
+
+This post marks the transition to a Jekyll structure with dedicated docs, projects, and blog content paths.

_projects/platform-engineering-case-study.md

@@ -0,0 +1,18 @@
+---
+layout: default
+title: Platform Engineering Case Study Template
+permalink: /projects/platform-engineering-case-study/
+tags:
+  - projects
+  - platform-engineering
+categories:
+  - case-study
+---
+
+# Platform Engineering Case Study Template
+
+- **Problem:**
+- **Constraints:**
+- **Approach:**
+- **Outcome:**
+- **Follow-up work:**

about.md

@@ -0,0 +1,9 @@
+---
+layout: default
+title: About
+permalink: /about/
+tags: [about, metadata]
+categories: [site]
+---
+
+This site documents practical system engineering operations, from evergreen cheat sheets to platform project case studies and time-based blog notes.

blog.md

@@ -0,0 +1,13 @@
+---
+layout: default
+title: Blog
+permalink: /blog/
+tags: [blog, posts]
+categories: [navigation]
+---
+
+{% for post in site.posts %}
+
+- [{{ post.title }}]({{ post.url | relative_url }}) — {{ post.date | date: "%B %-d, %Y" }}
+
+{% endfor %}

cheat-sheets.md

@@ -0,0 +1,24 @@
+---
+layout: default
+title: Cheat Sheets
+permalink: /cheat-sheets/
+tags: [docs, cheat-sheets]
+categories: [navigation]
+---
+
+These pages come from the `_docs/` collection and are intended to be evergreen references.
+
+{% assign sorted_docs = site.docs | sort: 'title' %}
+{% for doc in sorted_docs %}
+
+- [{{ doc.title }}]({{ doc.url | relative_url }})
+
+{% endfor %}
+
+## Legacy topic folders
+
+The original topic directories are preserved during transition:
+
+- `Automation/`, `Backup/`, `Docker/`, `Firewall/`, `High Availability/`, `Load Balancing/`, `NTP/`, `SSH/`, `Tunning kernel/`, `Utils/`, `Web Services/`
+
+As documents are modernized, corresponding pages will be moved or aliased into `_docs/`.

index.md

@@ -0,0 +1,16 @@
+---
+layout: default
+title: Home
+permalink: /
+tags: [home, navigation]
+categories: [site]
+---
+
+Use the two primary paths below to get started quickly:
+
+- [Cheat Sheets]({{ '/cheat-sheets/' | relative_url }}) — Evergreen, task-oriented operational references stored in the docs collection.
+- [Blog]({{ '/blog/' | relative_url }}) — Time-based updates, release notes, and short operational writeups.
+
+## Transitional note
+
+Legacy topic folders remain available during migration. New and refreshed material will be published in `_docs/` and linked from this site structure.

projects.md

@@ -0,0 +1,14 @@
+---
+layout: default
+title: Projects
+permalink: /projects/
+tags: [projects, case-studies]
+categories: [navigation]
+---
+
+{% assign sorted_projects = site.projects | sort: 'title' %}
+{% for project in sorted_projects %}
+
+- [{{ project.title }}]({{ project.url | relative_url }})
+
+{% endfor %}