I’d like to put this forward as a request for enhancement: to provide an API on galaxy to return the HTML that galaxy would render for a submitted blob of markdown. The discussion cited above, part of which is quoted below, shows how to use the equivalent API on both github and gitlab. Such a feature on galaxy would facilitate README.md and other *.md creation and editing by providing a mechanism for maintainers to see how their documentation renders before committing to publication.
This sounds like a cool idea @utoddl, thanks for proposing!
We’ve got it added to our roadmap* for scoping and inclusion in a future milestone. The team is a bit at capacity with our current shorter term roadmap of enhancements and fixes to galaxy right now. In short, we probably won’t be able to dedicate a dev to this feature until sometime next year at the earliest.
That being said, if you or anyone else is interested in working on this enhancement in the shorter term, we’d be happy to work through a potential PR for inclusion.
*the roadmap mentioned/milestones are currently getting finalized we are hoping to publish info about these next week.
The ansible/galaxy_ng README.md invites me to view the Roadmap which leads me to a three-year-old page leading to roadmap for 4.4.0 which is tweakable, but searching for various combinations of “markdown”, “preview”, and/or “galaxy” just … reminds me that I have a lot of “good intention” artifacts in my own projects.
Hi @utoddl! I actually took an interest in this one quite some time ago and added a command to galaxy-importer to convert markdown to html. It was released with version 0.4.19 of galaxy-importer on January 18th.
I’m a little vague on how galaxy-importer fits into the ecosystem. Is this the same code that’s used by galaxy.ansible.com when uploading content? If so, does this imply that galaxy (the service) stores doc assets pre-rendered? (That would explain why I didn’t see anything relevant to rendering md→html when rummaging through the galaxy-ng code.)