11 KiB
title, summary, type, client, project, status, priority, created, tags, aliases
| title | summary | type | client | project | status | priority | created | tags | aliases | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AI Resume - Content Organization Plan | Plan for organizing resume content across Docker containers on .35 | note | sam | ai-resume | active | 5 | 2026-06-19 |
|
AI Resume - Content Organization Plan
Goal
Organize my skills, projects, and interests across the Docker containers on 192.168.20.35 to present a comprehensive AI-powered resume showcasing a broad range of capabilities. Gitea on .13 handles all code — this plan is purely about what content goes where.
Container Assignment Strategy
1. BookStack — Primary Resume / Portfolio Hub
Best for: Structured, professional documentation with chapters and books.
Content:
- Book: "About Me" — Personal background, philosophy, approach to technology
- Book: "Skills & Technologies" — Organized by category (Backend, DevOps, AI/ML, IoT, Web Dev, Data Analysis)
- Book: "IoT Projects" — Dedicated shelf for all IoT projects (MQTT, sensors, Home Assistant, ESP32, etc.)
- Book: "AI Projects" — LangChain, RAG, Airflow pipelines, scraping systems, LiteLLM, Langfuse, knowledge-service
- Book: "DevOps & Infrastructure" — Docker, NixOS, networking, monitoring (LibreNMS, UptimeKuma, Grafana), backups, security
- Book: "Web Development" — Frontend/backend projects, T3 stack, React
- Book: "Data Analysis" — Data pipelines, scraping, analysis projects
Why: BookStack's book → chapter → page hierarchy is ideal for a structured professional presentation. It looks polished, supports images well, and is publicly presentable. This is the public-facing centerpiece.
2. WikiJS (Wiki2) — Technical Knowledge Base & How-To Guides
Best for: Interlinked technical documentation with a modern editor and search.
Content:
- Deep-dive technical write-ups that reference each other (e.g., "How NixOS multi-machine deployment works with .13 and .35")
- Docker container explainers — what each container does, why it's set up the way it is
- Architecture decision records — why ChromaDB, why Airflow, why this stack
- Network topology & infrastructure — the whole home lab setup
- Cross-linking between topics (skills ↔ projects ↔ infrastructure)
Why: WikiJS is better for dense, interlinked technical content where you want bidirectional links and powerful search. It complements BookStack's structured narrative with a more wiki-style reference layer. Good for showing depth.
3. DokuWiki — Gardening Journal & Knowledge Base
Best for: Structured topical wiki, already in use.
Content: Continue current gardening use. This is a great example of a living hobby project that shows you apply technical tools to diverse interests.
Why: Already established. No need to migrate. Shows long-term maintenance and real-world usage — a point in your favor for showing you don't just set things up and abandon them.
4. Hedgedoc — Collaborative Blog / Living Articles
Best for: Markdown-based editable pages with real-time collaboration potential.
Content:
- Politics, Economics, International Relations articles and essays
- Art, Philosophy, Literature reflections and analysis
- Opinion pieces and commentary that show depth of thought beyond tech
- These can be more informal, blog-style, updateable
Why: Hedgedoc is great for blogging because it renders Markdown beautifully and has a clean, minimal reading experience. Showing serious engagement with social sciences, philosophy, and arts makes for a far more interesting resume than just technical content. Use the Canvas feature for visual/political maps or diagrams.
5. SilverBullet — Second Brain / Research Notes
Best for: Personal knowledge management with queryable, linked notes.
Content:
- Raw research notes for all the above platforms
- Scraping results and data notes from your Python/Airflow scraping pipelines
- Learning notes on new technologies, courses, reading
- Quick capture before content gets polished and moved to BookStack/WikiJS
Why: SilverBullet is excellent as a "staging area." Notes get captured, linked, queried, then promoted to the public-facing platforms. It shows you have a mature knowledge management workflow. Its query features are great for dynamic content views.
6. Trilium — Project Journals & Structured Notes (Restart)
Best for: Hierarchical, note-rich project documentation with attributes and relations.
Content:
- IoT project documentation — each project as a subtree with specs, wiring diagrams (as images), code snippets, lessons learned
- Skiing, Hiking, Camping logs — trip reports with photos, routes, gear notes
- Cooking recipe collection with notes and modifications
- Movie reviews and ratings — structured with attributes (genre, rating, year)
Why: Trilium's strength is hierarchical notes with rich attributes and relations. Since the data was lost, it's a clean start. It's project/hobby-focused rather than public-facing — more of a private reference. Great for organizing complex projects with lots of sub-topics.
7. FlatNotes — Quick Project Notes / Lightweight Journal
Best for: Simple, fast Markdown notes with tagging.
Content:
- Ongoing project quick-notes — brief updates, ideas, troubleshooting logs
- Flat project journal entries tagged by project area
- Meeting-like notes for when you're working through technical problems
Why: FlatNotes is intentionally simple. It's your "notepad" — the place you jot things down quickly before they get organized elsewhere. Shows you're methodical about capturing information at the point of discovery.
8. Vikunja — Project Roadmap & Task Management
Best for: Kanban-style project and task tracking.
Content:
- AI Resume project itself — tasks for writing up each section (IoT write-up, DevOps write-up, etc.)
- Content publishing pipeline — draft → review → publish workflows for each platform
- Project backlog for all IOT, AI, web dev projects
- Personal goals and milestones (completing write-ups, setting up portfolios)
Why: Vikunja demonstrates project management skills. Nothing shows competence like a well-organized task board showing you can plan and execute complex multi-domain projects. Can be referenced in the resume as "how I work."
9. Affine — Visual Workspace / Whiteboard
Best for: Visual, whiteboard-style documents with mixed media.
Content:
- Visual project maps — network diagrams, architecture drawings, system topology
- Resume mind maps — how skills connect to projects connect to interests
- Timeline visualizations — project history, technology evolution in your setup
- Mixed-media pages combining text, images, drawings for complex topics
Why: Affine's whiteboard + document hybrid is great for visual content that doesn't fit well in text-only platforms. Architecture diagrams, system overviews, and visual storytelling add variety to how you present. It shows you think visually as well as in code.
Content Flow / Workflow
Raw info & research Refined drafts Public presentation
┌──────────────────┐
SilverBullet / ──► Trilium / ──► │ BookStack │
FlatNotes FlatNotes │ (Portfolio Hub)│
(raw capture) ──► (structured ──► ├──────────────────┤
notes) │ WikiJS │
│ (Tech Reference)│
Scraping / ──► SilverBullet ──► ├──────────────────┤
Airflow / Python (review & tag) │ Hedgedoc │
│ (Blog/Essays) │
└──────────────────┘
Vikunja tracks it all
Affine for visuals
Gotchas & Notes
- Only use .35 containers for public-facing content; .13 is infrastructure-only
- Gitea on .13 handles all source code — don't duplicate
- Immich on .35 is already available for photo/video management (skiing, hiking, cooking photos could live here and be referenced)
- Jellyfin can host video content if you want to include video walkthroughs of projects
- DokuWiki stays as-is (gardening) — example of real long-term usage
- Trilium needs to be set up fresh — old data is gone
- Don't worry about Caddy/reverse proxy config — that's handled separately
Priority Order for Setup
- BookStack — Public portfolio hub, highest impact (write IoT & DevOps sections first since you mentioned having a lot)
- WikiJS — Technical depth, cross-linked reference (populate with architecture decisions, infrastructure docs)
- Trilium — Restart and begin IoT project documentation + hobby logs
- SilverBullet — Research and staging area (start capturing raw notes)
- Hedgedoc — Begin blog-style content on politics/economics/arts
- Affine — Visual additions (architecture diagrams, mind maps)
- Vikunja — Set up the content-creation project board to track progress
- FlatNotes — Lightweight capture (start using immediately for daily notes)
Subjects → Platform Matrix
| Subject | Primary Platform | Secondary Platform |
|---|---|---|
| IoT Projects | BookStack | Trilium (detailed), WikiJS (how-to) |
| AI/ML Projects | BookStack | SilverBullet (research) |
| DevOps & Infrastructure | BookStack | WikiJS (architecture) |
| Web Development | BookStack | WikiJS |
| Data Analysis & Scraping | BookStack | SilverBullet |
| Politics & Economics | Hedgedoc | — |
| International Relations | Hedgedoc | — |
| Art, Philosophy, Literature | Hedgedoc | — |
| Gardening | DokuWiki | Trilium (logs) |
| Skiing / Hiking / Camping | Trilium | Immich (photos) |
| Cooking | Trilium | Hedgedoc (recipes as blog posts) |
| Movies | Trilium | — |
| Travel | Trilium | Hedgedoc (travel essays) |
| Visual/Diagram Content | Affine | — |
| Quick/Daily Notes | FlatNotes | SilverBullet |
| Project Management | Vikunja | — |
| Code | Gitea (.13) | BookStack (code write-ups reference Gitea) |