Repository files navigation

• Getting Started
• Contributing
• Roadmap
• License
• .NET Foundation

Build your technical documentation site with docfx, with landing pages, markdown, API reference docs for .NET, REST API and more.

As you may have heard docfx has been transitioned to be a .NET Foundation project. Microsoft Learn no longer uses docfx and do not intend to support the project since Nov 2022.

Docfx is planned to continue as a community-driven project. We hope to produce future releases with new features and enhancements to support existing and new use cases. We also would like to invite any interested parties to be involved in this project. If you'd like to contact the community team please open a discussion thread.

1. Install docfx as a global tool:

   dotnet tool install -g docfx

2. Create and start a website locally:

   docfx init -ydocfx build docfx_project\docfx.json --serve

3. Go tohttps://localhost:8080 to see the sample site.

For more information, refer toGetting Started.

UseDiscussions for questions and general discussions.UseIssues to report bugs and proposing features.

We welcome code contributions through pull requests, issues tagged ashelp-wanted are good candidate to start contributing code.

• InstallVisual Studio 2022 (Community or higher) and make sure you have the latest updates.
• Install.NET SDK 8.x and 9.x.
• Install NodeJS (22.x.x).

• Build site templates intemplates directory:
  • Runnpm install to restore npm dependencies.
  • Runnpm run build to build the templates.
• Rundotnet build to build the project or use Visual Studio to builddocfx.sln.
• Rundotnet test to test the project or use Visual Studio test explorer.
  • Rungit lfs checkout to checkout files for snapshot testing

Themain branch is the default branch for pull requests and most other development activities. We occasionally usefeature/* branches for epic feature development.

Releases are based on a stablemain branch commit usingGitHub Releases. Use ofConventional Commit is encouraged.

Docfx isnot released under a regular cadence, new versions arrive when maintainers see enough changes that warrant a new releases. Sometimes we use prereleases to dogfood breaking changes and get feedbacks from the community.

We useMilestones to communicate upcoming changes docfx:

• Working Set are features being actively worked on. Not every features in this bucket will be committed in the next release but they reflect top of minds of maintainers in the upcoming period.

• Backlog is a set of feature candidates for some future releases, but are not being actively worked on.

This project is licensed under theMIT License.

This project is supported by the.NET Foundation.

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community.For more information see the.NET Foundation Code of Conduct.