Unify markup to Markdown (in this repo) #928
Labels
architecture/legacy or broken
Legacy and/or broken architecture
contributor experience
Contributor/Maintainer experience
Milestone
What was the
end-usercontributor problem that led to this PR?Middleman supports for multiple template engines as shown in https://middlemanapp.com/basics/templating-language/, and so we had used three engines: HAML, Markdown in addition to ERB for files from the upstream's
ronn
man pages.Conversion from Markdown to HAML was done in #230 in 2016 😭 .
What was your diagnosis of the problem?
As HAML allows us to flexibly use Ruby code in their files, these files tend to be complicated. And so line wrapping gets harder to use, which results in problems recently resolved in #926.
As discussed in #829,
ronn
files inrubygems/rubygems/bundler/..../man
are based on Markdown.While HAML provides helpers to easily avoid duplications, there have been many duplications (see https://github.com/rubygems/bundler-site/milestone/2 for detail).
After completion of https://github.com/rubygems/bundler-site/milestone/2, we will have three types of files in this repository: guides, navigations, blog articles.
guides
While HAML files are dominant, it looks like the existing HAML can be converted to markdown.
navigations
docs.html.haml
has many Ruby code snippets but they can be replaced with a new Rake task.whats_new.html.haml
has no Ruby code so that it would be easily converted to markdown.blog articles
All articles are rewritten in Markdown. No sense to convert them to HAML.
What will be your fix for the problem?
All files would be in Markdown than a mixture of HAML and Markdown.
TODO
Why will you choose this fix out of the possible options?
Not sure if HAML is suitable for such a static site.
The text was updated successfully, but these errors were encountered: