msys2 / msys2/msys2.github.io

Proposal: Migrate the MSYS2 Website to Sphinx for Localization

Open
#407 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
3.3k
Forks
446
Avg merge
2h 16m
Merged PRs (30d)
1

Description

Proposal

Migrate the MSYS2 Website to Sphinx for Localization

About Us

Hello MSYS2 Team,

I am the author of the @localizethedocs organization, which focuses on creating l10n projects for open-source documentation. Currenlty, I have already established a comprehensive localization infrastructure applicable to almost all Sphinx-based documentation, and have successfully created l10n projects for several major open-source projects. For example:

For every l10n project, translations are contributed via the Crowdin platform, automatically synchronized with the GitHub repository, and can be previewed on GitHub Pages.

Motivation

I noticed an existing issue where users expressed a desire for the MSYS2 website to support multiple languages:

Currently, the MSYS2 team's solution appears to be the automatic generation of translations via Google Translate. However, I always believe that even as machine or AI translation matures, the final decision on whether to adopt those translations must be made by humans. Therefore, I do not consider the current approach to be an ideal long-term solution.

Since MkDocs itself has not yet implemented an "Internationalization with Gettext" feature comparable to Sphinx's, I am currently unable to create a similar localization infrastructure for MkDocs documentation. However:

If the MSYS2 website is migrated from MkDocs to Sphinx, I would be able to immediately leverage my existing infrastructure to create the msys2-site-l10n project.

Additional Information

If the MSYS2 team decides to migrate the website to Sphinx and wishes to maintain a theme and layout consistent with the current MkDocs-based website, I recommend considering sphinx-immaterial. Here are a few projects that use the sphinx-immaterial theme for reference:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the current MkDocs-based MSYS2 website and the related localization request in issue 275. Compare the proposed Sphinx migration and sphinx-immaterial theme with the existing site, and treat a team decision on scope, migration feasibility, and localization support as the completion point.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, localization, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.