My personal engineering knowledge base, built with MkDocs Material and deployed to nectar.ibtisam-iq.com. 200+ pages across Kubernetes, AWS, CI/CD, GitOps, and DevSecOps, continuously growing as I learn.

flowchart TD
    A(["❓ I don't understand\nsomething"])
    B(["🔧 I run it for real"])

    C["First-principles learning\nDeep mental model"]
    D["Full implementation\nDebugging & experiments"]

    NECTAR[("📚 Nectar")]

    E(["💡 It becomes clear\n& repeatable"])
    F["Reusable manifests\nScripts & IaC"]
    SILVER[("⚙️ SilverStack")]

    G(["🏗️ Multiple components\nform a platform"])
    H["System view\n& architecture"]
    PROJECTS[("🚀 Projects")]

    I(["📋 Execution steps\ndocumented in place"])
    J["Commands, failures,\nresolutions captured"]
    RUNBOOK[("📋 Runbook")]

    K(["✍️ I explain\nthe practical path"])
    L["Distilled, problem-oriented\nwrite-up"]
    BLOG[("📖 Blog")]

    A --> C --> NECTAR
    B --> D --> NECTAR
    NECTAR --> E --> F --> SILVER
    NECTAR --> G --> H --> PROJECTS
    NECTAR --> I --> J --> RUNBOOK
    NECTAR --> K --> L --> BLOG

    style NECTAR   fill:#1f5fce,color:#fff,stroke:#1f5fce
    style SILVER   fill:#3fb27f,color:#fff,stroke:#3fb27f
    style PROJECTS fill:#9c6bde,color:#fff,stroke:#9c6bde
    style RUNBOOK  fill:#4b9de0,color:#fff,stroke:#4b9de0
    style BLOG     fill:#e6813a,color:#fff,stroke:#e6813a

Three jobs, each scoped to what it needs.

nectar/
├── .github/workflows/pages.yml     # build, preview, deploy
├── docs/
│   ├── images/                     # favicon and logo
│   ├── javascripts/extra.js        # reading-progress bar
│   ├── overrides/                  # 404.html, main.html
│   └── stylesheets/extra.css       # custom design system
├── mkdocs.yml                      # site config, plugins, extensions
├── requirements.txt                # pinned Python dependencies
├── index.md                        # home page
├── about.md                        # about page
├── cloud-infrastructure/
├── containers-orchestration/
├── delivery/
├── observability-security/
├── operations/
├── servers/
└── technical-grounding/

python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
mkdocs serve -a 0.0.0.0:8000

Build the static site:

mkdocs build

act push -W .github/workflows/pages.yml

Artifact uploads, PR deploys, CNAME write, and the GitHub Pages deploy are skipped locally via env.ACT != 'true' guards. The build and link-check steps run as normal.

I didn't come from a CS background. But I recognized something in myself early on: I think in systems, I need to understand the why before a what makes sense to me, and I can't let confusion sit unresolved. Those traits pulled me toward engineering, not the other way around.

That mindset shaped how I learn. I can't just follow a tutorial and move on. If I don't understand why something works, I won't know what to do when it stops working. So I document everything, in my own words, structured the way my brain actually processes it, until the confusion is gone.

That habit, sustained over time, is what this repository is.

The early entries reflect where I started. The recent ones reflect where I am now. Both belong here, because this repository is not a finished product. It grows every time I learn something new, and it will keep growing.