build: migrate to ProperDocs - #1345
Open
iBotPeaches wants to merge 1 commit into
Open
Conversation
iBotPeaches
force-pushed
the
migrate-to-properdocs
branch
from
August 17, 2026 00:26
9a60282 to
933c044
Compare
iBotPeaches
marked this pull request as ready for review
August 17, 2026 00:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
mkdocs has some maintainer drama. I don't want to recap it - this article does a good job - https://fpgmaas.com/blog/collapse-of-mkdocs/. The future of fastlane docs probably isn't mkdocs, but in the meantime lets move to a fork of it that is not abandoned.
Solution
ProperDocs is a drop-in replacement led by a previous maintainer of mkdocs. We never used the Material theme of mkdocs which would have led our choice to MaterialX / Zensical, so ProperDocs is our route.