-
Notifications
You must be signed in to change notification settings - Fork 83
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
provide a .md template alongside the .rst one #94
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please! See also #85.
Here are minor tweaks I’d recommend, and a suggestion to also drop the forced line wrapping at 80 characters so the content is more readable.
conjunction with the content guidelines in [DEP | ||
1](https://github.com/django/deps/final/0001-dep-process.rst), this | ||
should make it easy for you to conform your own DEPs to the format | ||
outlined below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In #85 there’s also a mention of removing the wrapping to 80 characters, what do you think of updating this template accordingly?
template.md
Outdated
TEMPLATE!** | ||
|
||
To get the source this (or any) DEP, look at the top of the Github page | ||
and click \"raw\". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here and further through the rest of the doc, I think it’d be nice to remove the unnecessary escaping.
Co-authored-by: Thibaud Colas <[email protected]>
@thibaudcolas I'm personally in favour of everything mentioned in #85 and the original list but since none of those seemed to have reached a consensus, my goal for this PR was to be as minimal as possible in order to be able to merge it as quick as possible. If we can get a strong support behind all those changes, I'd be more than happy to have it here. Then I would also suggest removing the manual TOC in the .md file since, GitHub has this out of the box as a dropdown. |
Co-authored-by: Thibaud Colas <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me! Looking good
Which part? the part about not doing more in this particular PR or the part about doing more? |
the part about keeping things simple until there’s more support :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
About the Markdown
vs MarkDown
, I updated it to be consistent (I think the lowercase d is the correct casing).
Also suggested some syntax fixes for the rST links.
Co-authored-by: Gert Van Gool <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, no reason not to allow folks to use Markdown.
@carltongibson this should be good to go now |
Co-authored-by: Lily Foote <[email protected]>
Co-authored-by: Lily Foote <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @nanuxbe — I merged a couple of suggestions from @LilyFoote and resolved the escaping comment from @thibaudcolas.
I just had one other comment...
As suggested in this forum thread and this mastodon thread and probably many other places (I know the topic has been brought up several times on the forum, only have this one link).
The
.md
file was mostly generated using pandoc (only alterating the head of the file).Changes have also been made to the
.rst
template as well as DEP-1 in order to point to the markdown template, while the markdown template also points to the restructured text one