To create an anchor to a heading in github flavored markdown.
Add - characters between each word in the heading and wrap the value in parens (#some-markdown-heading) so your link should look like so:
[create an anchor](#anchors-in-markdown)
Created
July 8, 2012 14:12
-
-
Save asabaylus/3071099 to your computer and use it in GitHub Desktop.
Github Markdown Heading Anchors
Easiest Way I found to fix this was after writing down the headings on github, just do inspect element from the browser and find what the anchor links are 😁
thx, could not find the link for my complex text.
Upd. You can use any id, its value does not have to match the text of the element.
# 1.1 [Header](#1.1) ...some text... # 1.1 Header<a id='1.1'></a>Nice, that was actually the only real solution I found in the www for this issue. ❤️ Many thanks!
This works well. Thanks! 👍
Thanks
Note- If anyone facing issues with anchor linking. Please ensure that the text of anchor and the text of place where you are linking are different.
For e.g. There will be problem if you use
> ### [Anchor Link](#anchor-link)
> ## Anchor Link
Here problem because "Anchor Link" is used as text in both lines
But if different text used in [ ] then no issues. For e.g. we added "1." in [ ]
> ### [1. Anchor Link](#anchor-link)
> ## Anchor Link
Is there a way to do the opposite don't generate anchor links. This seems to happen automatically in github wiki everytime you defined a header and that clutters the sidebar navigation.
Every time I change section name I need to go and update all the anchors.
Consider HTML <tr id="XXX">…. Then a link to #XXX is a link to that whole row. Clicking on a <a href="#XXX">to XXX</a> causes the whole row to be on the screen, if possible the top pixel of the row at the top of the screen (not always possible if row near end of page). This is good.
In Markdown, putting | <a name="XXX"></a> … |, and clicking on [to XXX](#XXX) jumps to the middle of the row, at least if there is an image in the row. The top half of the row isn’t visible: above top of viewport. This is not good.
Please, is there a known solution?
Solution found.
• The large image cannot be a link (which is what confounded me).
• Then wrap the <a names="…">…</a> around the image.
Just wanted to leave a note that this approach does have accessibility/semantic issues (ref: https://developers.google.com/style/headings-targets).
Unfortunately, Github does currently not support the extended markdown syntax heading-ids (e.g. ### My Heading {#my-heading-id}), so the most accessible approach would be to use the HTML equivalent <h3 id="my-heading-id">My Heading</h3> instead.
I needed a quick Markdown TOC generator that would be compatible with GitHub, so I made my own: gh-toc.
It’s basically a web page with some JavaScript: You paste in your Markdown and it generates a GitHub-compatible Table of Contents. Your browser does the work and nothing gets sent to the Internet.
Features:
- Full Unicode support, all international characters.
- Better handling of (hopefully) all underscore cases.
- Correct handling of
code with backticks ` inside. - Much better code block support (backticks, tildes, differing number of them).
- YAML front matter support.
- Optional output of the full Markdown file, ToC inserted between
<!-- ToC begin -->and<!-- ToC end -->HTML comments, instead of just the ToC. - Optional named anchor generation for each ToC element (not needed for GitHub use).
- Optional use of
idinsteadnameattribute in generated anchors.
Markdown test file included.
thank you
Is there any way to cross reference to another files header?
For example:
File1 contains
# Title
## Description
Lorem Ipsum
File2 contains
# Data
Click here to see the Description from File 1: [Information](../File1#Description)
Is there any way to cross reference to another files header?
For example:
File 1 contains
# Title ## Description Lorem IpsumFile2 contains
# Data Click here to see the Description from File 1: [Information](../File1#Description)
Looks like it does work like that however keep in mind if you have special Characters as a File name (at least for me) it did not properly show up in VSC. However after just pasting it in manually and clicking it via the preview it should work out just fine. Note the %20 stands for a blank space character here.
For example:
File 1 contains
# Title
## Description
Lorem Ipsum
File2 contains
# Data
Click here to see the Description from File 1: [Information](../File%201#Description)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nice, that was actually the only real solution I found in the www for this issue. ❤️ Many thanks!