Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch rustdoc to Common Markdown #16978

Closed
brson opened this issue Sep 3, 2014 · 5 comments
Closed

Switch rustdoc to Common Markdown #16978

brson opened this issue Sep 3, 2014 · 5 comments
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@brson
Copy link
Contributor

brson commented Sep 3, 2014

Assuming this takes off it's probably best to be on the right side of history: http://standardmarkdown.com/. Probably easiest to just make hoedown conformant.

@Gankra
Copy link
Contributor

Gankra commented Sep 4, 2014

While I agree in principle, from their FAQ:

The current version of the Standard Markdown spec is complete (two years in the making!), but provisional pending public feedback, testing, and evaluation.

So I'm not sure if this is immediately appropriate. Should I log an issue against hoedown regardless?

@Gankra
Copy link
Contributor

Gankra commented Sep 4, 2014

Being tracked by Hoedown at: hoedown/hoedown#119

@Gankra
Copy link
Contributor

Gankra commented Sep 13, 2014

Moved to http://commonmark.org/

@RasmusWL
Copy link

RasmusWL commented Oct 9, 2014

Title should be change to CommonMark as well.

FYI: Hoedown is almost done with their implementation.

@steveklabnik steveklabnik changed the title Switch rustdoc to Standard Markdown Switch rustdoc to Common Markdown Oct 16, 2014
@steveklabnik
Copy link
Member

I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized.

This issue has been moved to the RFCs repo: rust-lang/rfcs#620

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants