Personal Wiki Build¶
Summary¶
This site is itself a project: a public technical portfolio built with MkDocs, Material for MkDocs, GitHub, and Cloudflare Pages.
It documents my projects, career positioning, technical notes, and lessons learned in a way that can be shared publicly.
Problem¶
Technical work gets lost when it only exists in chat threads, screenshots, local folders, and memory.
A public wiki creates a durable place to organize project work, explain technical decisions, show evidence, and connect hands-on work to career value.
Approach¶
The site is built as a static documentation project:
- Write pages in Markdown.
- Organize projects by category.
- Store screenshots with the project pages.
- Version the site in GitHub.
- Deploy through Cloudflare Pages.
- Keep the site public-safe and professional.
Tools and Concepts¶
- MkDocs
- Material for MkDocs
- Markdown
- Git
- GitHub
- Cloudflare Pages
- Static site deployment
- Technical writing
- Portfolio design
What This Demonstrates¶
- Documentation discipline
- Git-based workflow
- Static site deployment
- Public technical communication
- Project organization
- Professional presentation
- Ability to turn hands-on work into a clear portfolio
Outcome¶
The site provides a central place to present technical work, project evidence, career positioning, and public-facing documentation.
Screenshot Opportunities¶
| Screenshot | What It Proves |
|---|---|
| Local MkDocs preview | Shows development workflow |
| GitHub repository | Shows version control |
| Cloudflare deployment success | Shows static hosting |
| Live site homepage | Shows public result |
| Project page with screenshots | Shows portfolio maturity |
Screenshot Folder¶
Save screenshots here:
docs/assets/images/projects/personal-wiki/
Recommended filenames:
local-preview.pnggithub-repo.pngcloudflare-deployment.pnglive-homepage.pngproject-page.png