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
Therefore the links need to be modified in this way:
in_root.md
[Link to in folder](folder/in_folder)
folder/in_folder.md
[Link to root](../../in_root)
[Link to also in folder](../also_in_folder)
The ability to link without the extension is great but the complexity of the linking is not. So the smart linking should also be aware of whether permalinks are activated or not, and allow to use the following syntax and transform it as needed:
in_root.md
[Link to in folder](folder/in_folder)
folder/in_folder.md
[Link to root](../in_root)
[Link to also in folder](also_in_folder)
When a project contains several subrepos (like the contentascode spike developed for the open integrity project) it would be good to allow linking across parent repo and subrepo in a way that is simple for instance
[Link in the parent repo to a sub folder in the parent repo](/subfolder/file.md)
[Link in the parent repo to a subrepo](/subrepo_a/folder/file.md)
-> We need to manage subfolder/subrepo name collisions (via the pre-commit validation run? Implement link checker and other server side validation on Travis #11)[Link from a subrepo to the parent repo](/subfolder/file.md)
[Link from a subrepo to another subrepo](/subrepo_b/file.md)
With the baseurl problem (when sites are served from
scheme://host/folder/
) this needs some kind of pre-processing.The text was updated successfully, but these errors were encountered: