On Thu, Jul 2, 2026 at 8:00 AM Daniel P. Berrangé <[email protected]> wrote: > > On Thu, Jul 02, 2026 at 07:57:01AM -0400, Neal Gompa wrote: > > On Thu, Jul 2, 2026 at 7:55 AM Daniel P. Berrangé <[email protected]> > > wrote: > > > > > > On Thu, Jul 02, 2026 at 07:46:59AM -0400, Neal Gompa wrote: > > > > Contributing to a wiki is significantly easier than contributing to a > > > > git controlled document that requires a separate rendering process. > > > > > > > > Now, as for Fedora Changes? That is a different story. That said, the > > > > main beef people seem to have with Changes is that they are written in > > > > wikitext rather than markdown. I rather like the real-time editing and > > > > drafting capability our wiki gives, it's particularly great for > > > > collaborating with others on a jointly submitted document. But yes, > > > > I'd prefer a markup I use more frequently than wikitext. > > > > > > Editting the wikitext format is only part of the story. The use of > > > wikitext creates the interoperability problem when we then copy the > > > change text into discourse, with formatting repeatedly getting > > > mangled. We need a format that is common across all tools used in > > > the change process, and/or limit storage of the change to a single > > > tool such that lossy/errorprone format conversions are not required > > > > > > > Well, the obvious one is HTML, no? But aside from that, extending our > > wiki to accept Markdown would probably help a lot there. > > We don't really need the power of HTML most of the time. That's the > appeal of Markdown - it is good enough for 95% of docs needs, and you > can drop in fragments of HTML inline if really needed. >
Markdown isn't really designed for documentation. It's an ill-defined typesetting format meant for humans to comprehend plain text emails. CommonMark tries to fix some of it, but it's still not great in this regard. That said, even across our services, we don't use pure CommonMark. Discourse, Element, Bodhi, Forgejo, and Pagure all use different flavors of it with different features. So even if we "consolidate" on Markdown, it's still going to be challenging to transpose without loss unless we extend all services to support the same Markdown features. -- 真実はいつも一つ！/ Always, there's only one truth! -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
