Skip to content

Conversation

@matthewbbrandt
Copy link

@matthewbbrandt matthewbbrandt commented Jul 15, 2025

Description

This PR updates the documentation system to use Material for Mkdocs. Overall, this PR aims to simplify the documentation system by reducing dependencies and updating to a well-maintained build tool which generates visually-appealing and user-friendly documentation. Some lesser-used features are also removed (e.g., docs can no longer be exported to a Latex document).

Future work could include:

  • Finishing the type map, which maps between a type and the user-friendly string that is rendered (e.g., "FLOAT" -> "number"). As of this PR, only a few types have been added to the map.
  • Evaluating if the Python dependency should be moved to the parent CSE directory, rather than living only in the doc folder.
  • Implementing a coverage check, which is available in the current documentation system but has not yet been implemented for the new system.
  • Deploying multiple versions of the docs, so users can review both the latest and pervious versions of the documentation. This is supported by Material for Mkdocs for GitHub pages using mike as the versioning provider.

Author Progress Checklist:

  • Open draft pull request
    • Make title clearly understandable in a standalone change log context
    • Assign yourself the issue
    • Add at least one label (enhancement, bug, or maintenance)
    • Link the issue(s) addressed by this PR (under "Development" in the sidebar menu)
  • Make code changes (if you haven't already)
  • Self-review of code
    • My code follows the style guidelines of this project
    • I have added comments to my code, particularly in hard-to-understand areas
    • I have only committed the necessary changes for this fix or feature
    • I have made corresponding changes to the documentation
    • My changes generate no new warnings
    • I have ensured that my fix is effective or that my feature works as intended by:
      • exercising the code changes in the test framework, and/or
      • manually verifying the changes (as explained in the the pull request description above)
    • My changes pass all local tests
    • My changes successfully passes CI checks
    • Add any unit test for proof and documentation.
    • Merge in main branch and address resulting conflicts and/or test failures.
  • Move pull request out of draft mode and assign reviewers
  • Iterate with reviewers until all changes are approved
    • Make changes in response to reviewer comments
    • Merge in main branch and address resulting conflicts and/or test failures.
    • Re-request review in GitHub

Reviewer Checklist:

  • Read the pull request description
  • Perform a code review on GitHub
  • Confirm all CI checks pass and there are no build warnings
  • Pull, build, and run automated tests locally
  • Perform manual tests of the fix or feature locally
  • Add any review comments, if applicable
  • Submit review in GitHub as either
    • Request changes, or
    • Approve
  • Iterate with author until all changes are approved

Matthew Brandt added 30 commits February 20, 2025 21:45
- Adds uv for python environment and dependencies.
- Removes all ruby/pandoc content.
- Begins adding configuration for Mkdocs based on other BLS Mkdocs projects.
- Remaining work includes fixing internal links, tables, and probes.
I previously had prettier running on save, but it made several undesired changes, such as sometimes replacing "member_table" with "member*table".
Can these be deleted?
We may decide to revert this in the future, depending on how/when we build the docs for deployment to gh-pages.
@nealkruis nealkruis marked this pull request as ready for review October 14, 2025 14:54
@nealkruis nealkruis merged commit d299460 into main Oct 14, 2025
3 checks passed
@nealkruis nealkruis deleted the feature/migrate-to-mkdocs branch October 14, 2025 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documentation system support for arbitrary hyperlinks

4 participants