I saw this article already. But I can’t seem to get the anchor link to work in a url. For example, if I wanted to give my colleague a url to a specific anchor, the url loads up fine, but it doesn’t anchor.
Here is a more explicit example: If I put an anchor called “aboutDogs” in my guru card, when I click on the url (for example
https://app.getguru.com/card/12345/animal#aboutDogs) - the url loads up fine - but the browser doesn’t skip to the
About Dogs section.
How can I provide a url to an anchored section?
@Meng ! Thank you for asking this question.
As I understand it, you wish to be able to link your team to a specific Card section. You have set up the markdown feature to include that section in the table of contents (example here) but when you try to pull the URL you’re not able to load the Card specifically at that section. Is that correct?
If so, I have a few recommendations for you. While your request isn’t something we’re able to do in Markdown, I’d recommend:
Here’s an example of alternative #2:
Alternative (Breaking Card information out to multiple sections and Cards)
Hopefully this helps! Let me know if you have further questions.
Okay - thank you for your response
+1 on this - the problem I’d like to solve is linking users to a specific section in a Guru card from outside of Guru.
For example, we are creating documentation on how our team can use specific dashboards/software. We might have a card that walks through how to use a specific dashboard, what all the charts/visuals tell you, what alerts to set up on that dashboard, etc…
When folks get to the “what alerts should I set up” button on the dashboard, I want to link them directly to the section on the relevant card. Creating a separate card for each section related to each dashboard would be too much bloat.
I want to create robust interlinking to and from Guru, and being able to link to specific sections of Guru cards from other places would increase usage of Guru.
Thanks for sharing your use case
@Christina Blake! I suggest upvoting this feedback post (and maybe copying the link to your comment above as a comment on that post for additional visibility), as this feels pretty closely related.