Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Shapash documentation from Sphinx to MkDocs #630

Open
guillaume-vignal opened this issue Mar 21, 2025 · 0 comments
Open

Migrate Shapash documentation from Sphinx to MkDocs #630

guillaume-vignal opened this issue Mar 21, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@guillaume-vignal
Copy link
Collaborator

Description:

Currently, the Shapash documentation is built using Sphinx and hosted on ReadTheDocs. While this setup works, it may be beneficial to migrate the documentation to MkDocs, for the following reasons:

Why MkDocs?

  • Markdown-based: MkDocs uses Markdown files instead of reStructuredText, which is simpler and more commonly used by contributors.
  • Better GitHub integration: MkDocs can be easily deployed via GitHub Pages, allowing the documentation to be fully integrated into the GitHub ecosystem.
  • Modern UI: Themes like mkdocs-material offer a clean, responsive, and user-friendly interface out of the box.
  • Simpler configuration: Compared to Sphinx, MkDocs has a more straightforward configuration and build process.

Suggested Actions

  1. Set up a basic MkDocs structure with mkdocs.yml and docs/ directory.
  2. Migrate existing documentation from .rst to .md format.
  3. Choose and configure an appropriate MkDocs theme (e.g. mkdocs-material).
  4. Set up GitHub Actions or another CI tool for automatic deployment on GitHub Pages.
  5. Update contribution guidelines with new documentation instructions.

Optional

  • Add versioning support using mike or similar tools.
  • Integrate search functionality (native or via plugins).
@guillaume-vignal guillaume-vignal added the documentation Improvements or additions to documentation label Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant