About This Site
This page describes the tools, services, and hosting infrastructure used to build and deliver the Docsible documentation site.
🛠️ Site Stack & Tools
The Docsible site is built using:
- MkDocs - static site generator
- mkdocs-material - theme and layout framework
- Python Markdown - Markdown rendering engine
- Jinja2 - used internally for template rendering in Docsible-generated files
- GitHub Pages - used to host and serve the static site (https://docsible.github.io/)
🌍 External Services Used
Some assets are delivered using public CDNs:
| Resource | Use | Source |
|---|---|---|
| Google Fonts (Inter, Share Tech Mono) | For typography | fonts.googleapis.com |
| Mermaid.js | For task flow diagrams and playbook graphs | cdn.jsdelivr.net |
These assets are loaded directly in the site and do not track or collect analytics. They are included only to enhance visual display and graph rendering.
Data Usage & Privacy
🚫 No Data Collection
Docsible is a fully local CLI tool. It does not send any data to remote servers. There are:
- ❌ No tracking
- ❌ No telemetry
- ❌ No analytics
- ❌ No cookies or storage mechanisms
Everything generated by Docsible happens on your machine, unless you choose to publish or push the output manually.
📂 Hosting Transparency
The site and source code are open source and hosted publicly:
- GitHub Repo - full source code
- GitHub Pages - static site delivery only
This means:
- You can inspect or audit all code and site logic
- You can run your own fork or version if needed
- The site does not and will never require or collect user information
🧘 Open By Design
Docsible was built with a focus on:
- Transparency
- Simplicity
- Respect for developer autonomy
You own your docs, your data, and your build pipeline. Always.