Custom heading anchors could match the rest of the world
See original GitHub issueFeature request
What problem does this feature solve?
Markdown does not have a standard format for defining a custom heading anchor format. I see from this doc that docsify allows this with:
### Hello, world! :id=hello-world
First time I’ve seen this format. Would it make sense to add this far more common format “as well”?
## Hello, world! {#hello-world}
This allows things like working with pandoc for pdfs, and easier migration for anyone who wants to use docsify.
What does the proposed API look like?
NA
How should this be implemented in your opinion?
No
Are you willing to work on this yourself?
No
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Make headings into link targets - Google Developers
If you revise a heading in a content management system where anchors are automatically created, you can create a custom anchor to avoid...
Read more >tfs - Anchor can't find headings - Stack Overflow
When I look at the URL, it shows &anchor=1.3-Hello-World but that anchor is not scrolled to. In this example, I have to scroll...
Read more >Anchor links - Expert Success Center
Heading anchor link - Headings in MindTouch automatically function as anchors links. To create a heading anchor link, use the editor Heading ......
Read more >Links in HTML documents - W3C
Uniqueness: Anchor names must be unique within a document. Anchor names that differ only in case may not appear in the same document....
Read more >How to Create Anchor Links in WordPress (3 Easy Methods)
Using anchor links on headers lets you share direct links to different sections within an article. This is awesome for social media and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I understand that you may want have a more common syntax to render things like the sort of defacto-standard . IMO, for a real LTS project, things r not that idealized. Docsify is not a brand new project, hence we should take care of those breaking changes avoid breaking exist things for users.
Personally, I think we wont replace/refactor all the docsify syntax for now, maybe it would have plugins or adaptors in the future.
Thanks. Closing - made my point 😃