Consider using Markdown for the spec rather than HTML

[JayBeavers]

This would give us a lovely view right in the Github window and would allow us to use Github's web based editor for modifying the content.

[marcoscaceres]

Hmm... that would be nice, but we would eventually need to convert this to a "real" HTML spec. Using ReSpec has a lot of advantages, like it generates the WebIDL, does all the cross-references, and handles a ton of other stuff.

We could certainly develop proposals using markup initially then integrate them into the spec if that would help.

[marcoscaceres]

eer... initially in markdown I mean.

[reconbot]

I can see the value in ReSpec as the end product, but if there's collaboration on github initially markdown does seem smart.

[domenic]

+1, has been working out well for domenic/promises-unwrapping.

[larsgk]

+1 (to keep it simple)

On Wed, Oct 30, 2013 at 3:54 AM, Domenic Denicola
notifications@github.comwrote:

+1, has been working out well for domenic/promises-unwrappinghttps://github.com/domenic/promises-unwrapping
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-27361679
.

[marcoscaceres]

Turns out ReSpec also supports markdown. I'll convert the spec. However, not all parts can be converted (obviously!), but we get most of it in md.

If the end result is still not palatable, then we can switch to just markdown. However, it will mean eventually having to do everything again, so, I would really like us to avoid that! (having done specs for 7 years, I know first hand how much of a pain that can be).

[marcoscaceres]

Can you guys take a look at:
https://github.com/whatwg/serial/blob/markdown_convert/index.html

Let me know if that will work. That allows us to keep the WebIDL auto-generated (makes it much more maintainable!), but let's us have all the other prose as markdown.