DocsForge creates and hosts documentation for your open source projects.
It supports both manual documentation pages, and code auto-documentation to create public API pages.
Adding a New Project
When you add a new project, you provide a few basic parameters:
A url to where your repository is located.
The main programming language of your project (github or bitbucket).
(Optional) Docs directory where you have manually written documentation files.
(Optional) Source code directory that you wish to extract code auto-documentation.
We then link to your repository, extract documentation files that were written manually, and auto-document your source code.
Each project has a configuration file that defines how to build the documentation. The configuration file format is written in YAML.
When you add a new project, we create a configuration file to get you started.
An example configuration file:
sidebar: Basic Tutorial: - Getting Started: readme.md - Installation: docs/readme.md Advanced Tutorial: - Frequently Asked Questions: docs/faq.md - Advanced Topics: docs/advanced.md - Code Example 1: src/my_example.cpp - Contact us: http://example.com/contact-us/ Important API: - my_important_function1: api/my_important_class/my_important_function1 - my_important_function2: api/my_important_function2 autodocSettings: Public API: baseUrl: api language: cpp INPUT: src EXCLUDE: tests examples excludeApi: - an_unimportant_public_class - an_unimportant_public_func documentSingleUnderscore: true documentStatic: true documentProtected: true
The configuration file has 2 main parts:
sidebar- defines the documentation layout - which sections and pages will appear in your sidebar. Pages can either be text files (.txt, .md, .rst) or API pages (created automatically).
autodocSettings- defines which parts of your public API will be displayed - which source files to document, which to exclude, whether to document names that start with a single underscore, etc...
The full public API can be very large and daunting. Focus users to look into the most used API as was done in
Important API section. Any auto-generated API page can be added to any section.
Improving your documentation
Anyone reading your documentation can suggest edits and improvements.
Every page in your documentation is linked to your git repo, so any edits will go directly to github or bitbucket.
This includes documentation created from your source code - when you try to edit a public API page, you will be sent to the lines of code that created this documentation.
Each project can have several documentation versions, for different release tags or branches of your project.
You can also define which version is the
latest stable - the version which the end users should see by default.