Works too. Kind of. Same deal, to be honest, since the problem appears to be what Rick Wonder Cogley stated. The race is sometimes won, sometimes lost, thus, the aliases work or don’t, depending on the build’s mood.
The problem is that I do have content on those pages, since I am creating a Support FAQ (support.md) and I draw all the content for that FAQ from different .md files (games.md, publishing.md, etc) which, if I am allowed to say, keep things really, really neat for me and the user.
Yes, I realize that having a single .md file is the standard way to write a faq, and if I went that way, I wouldn’t even need any aliases… but things get a bit crowded in a single .md file when writing a very long doc.
The alternative would be to have different pages, with sections for that faq.
So you could have
But, while that’s also standard, it also gets tricky to browse when looking for an answer for a specific problem.
I made it work with just one file:
That’s it. All the other sections get called from that file.
Anyway, I’m satisfied with the solution, since I got the best of the two worlds. A long faq (any man wants to have a long faq, a manly faq) and the content, living in a single page. My users get to quickly iterate through the faq without jumping back and forth through dozen of different pages, and I get to write the faq in a orderly manner (one topic per .md file, which latter gets called into Support.md)
Thank you Hugo!