Published
Cloud Engineer publishing platform
Turn technical notes into a repeatable publishing system.
Built a MkDocs technical documentation site with local builds, GitHub Actions deployment, Firebase Hosting, and a custom domain.
- My role
- I built the documentation site and its publishing workflow.
- Result & status
- Published a technical documentation site with a repeatable update process.
No readership, adoption, or commercial outcome is stated in the public account.
The problem
How can technical writing move from local notes to a maintainable public site?
Structured source
MkDocs keeps technical pages navigable and maintainable.
Repeatable release
GitHub Actions builds and deploys from version-controlled content.
Public delivery
Firebase Hosting and a custom domain serve the documentation.
Approach
Put documentation in source control.
Organized content in MkDocs, set up a version-controlled build and deployment workflow in GitHub Actions, and published through Firebase Hosting.
Engineering
Build a release path for the writing.
Documentation structure, local rendering, CI/CD, hosting, and domain configuration form one publishing path.
Validation
Check the build and deployment path.
The existing project account describes local build checks and an automated deployment path. A public source or live URL is not currently linked for inspection.
MkDocs · GitHub Actions · Firebase Hosting · Google Cloud