It makes no sense to have system requirements and command-line arguments documented under "Usage", but the installation and first-run instructions under "Tutorials", especially when the pages themselves say that "Tutorials" is intended for module developers.
No redirects yet, old wiki links will need updating, etc., hence WIP. Maybe Liquid templating can go in the _redirects file or something, along with YAML front-matter in the pages that were renamed? I'll have a play with that next. Auto-generated redirects from the old pages to the new ones work, though.
But, all the {% link %} tags work without errors, so the site is at least internally consistent. (Patches like this are precisely why I decided using those was a good idea, because it helped me catch a few links that I forgot to update while drafting this change.)
It makes no sense to have system requirements and command-line arguments documented under "Usage", but the installation and first-run instructions under "Tutorials", especially when the pages themselves say that "Tutorials" is intended for module developers.
No redirects yet, old wiki links will need updating, etc., hence WIP.Maybe Liquid templating can go in theAuto-generated redirects from the old pages to the new ones work, though._redirects
file or something, along with YAML front-matter in the pages that were renamed? I'll have a play with that next.But, all the
{% link %}
tags work without errors, so the site is at least internally consistent. (Patches like this are precisely why I decided using those was a good idea, because it helped me catch a few links that I forgot to update while drafting this change.)