Getting Started with DocFX
1. What is DocFX
DocFX is an API documentation generator for .NET, and currently it supports C# and VB. It generates API reference documentation from triple-slash comments in your source code. It also allows you to use Markdown files to create additional topics such as tutorials and how-tos, and to customize the generated reference documentation. DocFX builds a static HTML website from your source code and Markdown files, which can be easily hosted on any web servers (for example, github.io). Also, DocFX provides you the flexibility to customize the layout and style of your website through templates. If you are interested in creating your own website with your own styles, you can follow how to create custom template to create custom templates.
DocFX also has the following cool features:
- Integration with your source code. You can click "View Source" on an API to navigate to the source code in GitHub (your source code must be pushed to GitHub).
- Cross-platform support. We have both exe version that runs under Windows and a .NET Core version that runs cross platform.
- Integration with Visual Studio. You can seamlessly use DocFX within Visual Studio.
- Markdown extensions. We introduced DocFX Flavored Markdown(DFM) to help you write API documentation. DFM is 100% compatible with GitHub Flavored Markdown(GFM) with some useful extensions, like file inclusion, code snippet, cross reference, and yaml header. For detailed description about DFM, please refer to DFM.
2. Use DocFX as a command-line tool
Alternatively, you can download and unzip docfx.zip from https://github.com/dotnet/docfx/releases, extract it to a local folder, and add it to PATH so you can run it anywhere.
Step2. Create a sample project
docfx init -q
This command generates a default project named
Step3. Build the website
docfx docfx_project\docfx.json --serve
Now you can view the generated website on http://localhost:8080.
3. Use DocFX with a Build Server
DocFX can be used in a Continuous Integration environment.
Most build systems do not checkout the branch that is being built, but
detached head for the specific commit. DoxFX needs the the branch name to implement the
View Source link in the API documentation.
Setting the environment variable
DOCFX_SOURCE_BRANCH_NAME tells DocFX which branch name to use.
Many build systems set an environment variable with the branch name. DocFX uses the following:
BUILD_SOURCEBRANCHNAME- Visual Studio Team Services
CI_BUILD_REF_NAME- GitLab CI
Known issue in AppVeyor: Currently
platform: Any CPU in appveyor.yml causes
docfx metadata failure. https://github.com/dotnet/docfx/issues/1078
4. Build from source code
As a prerequisite, you need:
git clone https://github.com/dotnet/docfx.git to get the latest code.
build.cmd under root folder.
artifacts folder to nuget source by in IDE:
Tools > NuGet Package Manager > Package Manager Settings > Package Sources
Step4. Follow steps in #2, #3, #4 to use DocFX in command-line, IDE or .NET Core.
6. A seed project to play with DocFX
Here is a seed project https://github.com/docascode/docfx-seed. It contains
- A basic C# project under
- Several conceptual files under
- An overwrite file to add extra content to API under
toc.ymlunder root folder. It renders as the navbar of the website.
docfx.jsonunder root folder. It is the configuration file that
It is a good practice to separate files with different type into different folders.
- Q: How do I quickly reference APIs from other APIs or conceptual files?
- Q: What is
uidand where do I find
uid? A: Refer to Cross Reference section in DFM.
- Q: How do I quickly find
uidin the website? A: In the generated website, hit F12 to view source, and look at the title of an API. You can find