You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue addresses how we could implement relative linking in the tutorials.
As of now, we'll need to add the full url for navigation from chapter to chapter. As Gatsby and Markdown out of the box won't allow relative linking between chapters and headings.
Adding such relative linking will default to the top of the page. This was tested with a development build with gatsby develop and a production build with a emulated server, using gatsby build && gatsby serve.
Once we have a little more time i'll circle back to this and implement what was started with #299.
At that time and per @domyen feedback some additional work was required for it to go through, not only visually, but technically as well. As some of the heading links need to be "sanitized" for special characters, for instance in my native language with the usage of (ç, ã, ).
We could go with adding the gatsby-remark-autolink-headers plugin and create a nice way for the headings to be used and have a good and efficient way of displaying the content and allowing linking.
Feel free to provide feedback.
The text was updated successfully, but these errors were encountered:
This issue addresses how we could implement relative linking in the tutorials.
As of now, we'll need to add the full url for navigation from chapter to chapter. As Gatsby and Markdown out of the box won't allow relative linking between chapters and headings.
Adding such relative linking will default to the top of the page. This was tested with a development build with
gatsby develop
and a production build with a emulated server, usinggatsby build && gatsby serve
.Once we have a little more time i'll circle back to this and implement what was started with #299.
At that time and per @domyen feedback some additional work was required for it to go through, not only visually, but technically as well. As some of the heading links need to be "sanitized" for special characters, for instance in my native language with the usage of (ç, ã, ).
We could go with adding the
gatsby-remark-autolink-headers
plugin and create a nice way for the headings to be used and have a good and efficient way of displaying the content and allowing linking.Feel free to provide feedback.
The text was updated successfully, but these errors were encountered: