Skip to content

Which projects will continue using Sphinx or migrate to another SSG? #15396

Description

@hwhsu1231

Hello @ipython maintainers,

I have submitted a Jupyter Foundation Funding Proposal (jupyter-governance/funding-proposals#38), which is currently under review. The proposal aims to establish continuous, automated documentation localization infrastructure for key projects across the Jupyter ecosystem under the @localizethedocs initiative. As part of the proposal, I have listed the following candidate projects, all of which are currently based on Sphinx:

However, I’ve observed that several projects within the Jupyter ecosystem are gradually migrating from Sphinx (Jupyter Book v1) to MySTMD (Jupyter Book v2). Since MySTMD does not yet implement full gettext-based i18n support (jupyter-book/mystmd#2980), migrating a project away from Sphinx midway may pause localization maintenance after the l10n projects are published.

Therefore, I would like to confirm: which of these candidate projects will continue using Sphinx, and which have already decided to migrate to another SSG (static site generator)? This will help ensure that the proposal and any future localization work reflect the projects’ plans.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions