#anchor heading links to content lower on page

[craigboman]

Describe the feature:

Looking at this #10461 and the merged #12560, this does not match the user story for markdown heading anchor links. I would recommend the following request. It is an expected feature in markdown to be able to jump from a table of contents at the top of a page to the heading for content lower on the same page. Please add this functionality.

Describe a specific use case for the feature:
When creating a markdown page in Kibana, I am documenting potential use cases for my customers, or creating documentation to help users navigate our hosted implementation of Kibana (ELK). When creating a documentation dashboard in the markdown widget I have a table of contents at the top of the page with #anchor jump links to the content lower on the same page. This is a super popular feature already present in Github markdown, but is not possible in Kibana markdown. Here is an example I have made on Github using this feature, but there are millions of other examples. https://github.com/craigboman/markdown-test/blob/master/README.md On this page the [markdown-test-test](#Writing-your-own-Kibana-documentation-using-markdown) links to the corresponding heading lowering on the page.

[elasticmachine]

Pinging @elastic/kibana-app

[timroes]

I am not so sure how well jumping to ids (and that would be the easy part, giving each dashboard panel an auto generated or from its title derived id) works with putting all the state in fragment of the URL and using it for single page app navigation. Could be worth investigating though.

[craigboman]

Right, I can do something like the following from a page [How do I get to my dashboards?](/app/kibana#/dashboard/3f525040-b795-11e9-9287-c9e26264e588#anchor-heading) which will link to /app/kibana#/dashboard/3f525040-b795-11e9-9287-c9e26264e588 but the app doesn't recognize /app/kibana#/dashboard/3f525040-b795-11e9-9287-c9e26264e588#archor-heading.

[craigboman]

...and by recognize I mean the page will load just fine, but viewing the page at the top, rather than jumping to #anchor-heading, as you probably know.

[ThomThomson]

In order to build functionality like this, we'll need to create something that programatically scrolls to the correct panel. This is because the hash is already used in routing.

Will close this for now, as our preferred solution for organizing panels will be the navigation embeddable. Once that is complete, we can consider adding an additional feature that can scroll to a panel id.