-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Update docs #1081
Update docs #1081
Conversation
Josh, this is the third PR you've opened concerning updates to the README. Can you slow down a bit? I cannot follow you around in all these new issues. Remember if you change your mind on some commits you make in the PR branch you can always rewrite them by |
That's fair. Not sure the other specific PRs you're referring to - I only have two opened at the moment: #1076 (0.3.17 release updating PR templates) and this one. I believe the others might have been merged or closed...I did run into an issue where GitHub was listing my PRs as being from an "unknown repository," which I've never seen before now; therefore, some of the closings were due to that. Don't think I'll be opening any more new things for a bit. :) Definitely understand the feeling though - this is what it felt like when @chjj and I were doing the organization thing - things were done before I could hit reply. ;) |
@@ -0,0 +1,136 @@ | |||
## Extending Marked |
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.
@Feder1co5oave, @UziTech, and @styfle: Could use some help on the content here, I think. Purpose is to document and demonstrate overriding/extending the renderer, lexer, and parser...seems we are light on documentation there.
USAGE_EXTENSIBILITY.md
Outdated
<li><a href="#parser">The parser</a></li> | ||
</ul> | ||
|
||
<h2 id="rederer">The renderer</h2> |
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.
The renderer...
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.
Why are you using HTML here? Instead of <h2>
you can use ## Renderer
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.
Fair question. For the id
attribute. Is there another way to get inline anchors to work properly using GitHub Markdown??
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.
Consolidating comments from #1061: I've always run into issues there [GitHub automatically generating IDs]; so, normally end up doing it by hand. Also, could make it more difficult to use in a non-GFM setting; at least here we know the TOC will always work[...like pulling in the Markdown file into a separate context outside of the GFM markdown rendering.]
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.
I typically let github generate it like so: https://github.com/styfle/copee#demo
But a TOC is a good point, you don't want to accidentally break it if you change the heading later.
- image(*string* href, *string* title, *string* text) | ||
- text(*string* text) | ||
|
||
<h2 id="lexer">The lexer</h2> |
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.
The lexer...
The lexer is... | ||
|
||
|
||
<h2 id="parser">The parser</h2> |
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.
The parser...
|
||
The parser is... | ||
|
||
*** |
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.
The current documentation for the lexer and parser
|
AUTHORS.md
Outdated
- Tony Brix @UziTech | ||
- Federico Soave @Feder1co5oave | ||
- Tony Brix @UziTech - really good at the test harness and environment setup | ||
- Federico Soave @Feder1co5oave - really good at the regex things | ||
- Steven @styfle |
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.
Steven @styfle - good for nothing
😜
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.
I honestly thought about putting: Good for lying in the weeds and randomly showing with a nugget of excess truth on operations before disappearing again. 😝
Description
This PR helps break up the README into more consumable chunks.
Submitter
Reviewer