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
An alternate way to configure the redirections would be to use symlinks in the docs/ directory. That way it would not require editing the mkdocs.yaml file for every redirect and might be an easier way to manage the files.
The text was updated successfully, but these errors were encountered:
Personally, I'm not sure about this. I have many redirects configured at the moment (300+) and I prefer to have them explicitly configured on a centralized location. It also makes it easier to see the changes to the redirects in the git history.
I'm using symbolic links to create the docs/ (docs_dir) content as the repository file-layout is not inherently compatible with the docs/ (docs_dir) base in Mkdocs. This works very well with Mkdocs and turning all those into redirects would not work.
So to answer your question raised with this issue: No, do not use symlinks in docs/ to configure redirects as they first of all work for the actual content which is incompatible with redirects.
To generalize: Such a change would break compatibility with Mkdocs. Symbolic links have a different meaning for Mkdocs already, it is not possible to use them as redirects as well.
Please let me know if you think this is an over-generalization.
An alternate way to configure the redirections would be to use symlinks in the
docs/
directory. That way it would not require editing themkdocs.yaml
file for every redirect and might be an easier way to manage the files.The text was updated successfully, but these errors were encountered: