Skip to content

Markdown support - #712

Merged
acolombier merged 2 commits into
mixxxdj:mainfrom
JoergAtGithub:markdown_support
Mar 26, 2026
Merged

Markdown support#712
acolombier merged 2 commits into
mixxxdj:mainfrom
JoergAtGithub:markdown_support

Conversation

@JoergAtGithub

@JoergAtGithub JoergAtGithub commented Jan 7, 2025

Copy link
Copy Markdown
Member

The example-setups page in this PR is generated from MarkDown syntax instead of RST syntax: https://deploy-preview-712--mixxx-manual.netlify.app/chapters/example_setups

@JoergAtGithub
JoergAtGithub changed the base branch from 2.5 to main January 7, 2025 19:19
@JoergAtGithub
JoergAtGithub requested a review from Holzhaus January 8, 2025 19:35
@daschuer

Copy link
Copy Markdown
Member

This is a nice summary:
https://nikhilakki.in/markdown-vs-restructured-text

@daschuer

Copy link
Copy Markdown
Member

What is the status here? Is this only about getting cross link check working?

@acolombier

Copy link
Copy Markdown
Member

Looks like the links are actually working, only seems to get this false positive on the CI, perhaps some settings to tweak?

@JoergAtGithub

Copy link
Copy Markdown
Member Author

What is the status here? Is this only about getting cross link check working?

This was a prove of concept how to use MarkDown as manual source for mapping pages instead of RST.
For the PoC I selected a page with many different elements and cross links from and to it. This is more than a mapping page will have (usually only links to other manual page but not in the opposite direction). As you can see, most RST formattings could be translated to MD syntax, but not all. The links work, but there I warnings, which I don't understood.

The idea in our monthly call was to store the MD files next to the controller mapping files, that the contributor needs only one PR to one single Repo. This MD file would than be syncronized to the manual repo, using the same process that we've already to get the changelog into the manual.

@acolombier

Copy link
Copy Markdown
Member

Circling back on this, I have submitted a PR to make the Markdown version exactly equivalent to the look to the RST version and prove we can keep exact same feature (callout block, labels, glossary terms, ...)

I think this could be enough to merge this as is, so we can start consolidating the documentations allowing Markdown as alternative, and for example migrate the left over documentation from the Mixxx Github Wiki with a least amount of effort, using the Wiki repo (git@github.com:mixxxdj/mixxx.wiki.git)

Wdyt?

@acolombier acolombier mentioned this pull request Mar 21, 2026
3 tasks
@acolombier

Copy link
Copy Markdown
Member

There is some issue with Netlify, hopefully will be fixed soon

@acolombier

Copy link
Copy Markdown
Member

Okay, Netlify fixed there issue. Preview is available here and reference page can be viewed in there

Note that the build is failing on unrelated warning.

@JoergAtGithub
JoergAtGithub marked this pull request as ready for review March 25, 2026 21:26
@JoergAtGithub JoergAtGithub changed the title [POC] Markdown support Markdown support Mar 25, 2026
@JoergAtGithub

Copy link
Copy Markdown
Member Author

Now everything is working!

@acolombier

Copy link
Copy Markdown
Member

Do you want to squash the fixups? I think this ready to go otherwise!

@JoergAtGithub

Copy link
Copy Markdown
Member Author

Done!

@acolombier
acolombier merged commit e5de2df into mixxxdj:main Mar 26, 2026
8 of 9 checks passed
@JoergAtGithub
JoergAtGithub deleted the markdown_support branch March 26, 2026 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants