Looks good to me, although as discussed yesterday on IRC, I'm still not sure about creating the fake en_US translation.
For the broken links, it seems what is happening is that during the build pelican is trying to find e.g. faq.html, which is not built (we build faq.en-us.html instead) so it gets confused and outputs the link as './'. If the index.md file is modified as below, then the generated links work (but for English only).
Looks good to me, although as discussed yesterday on IRC, I'm still not sure about creating the fake en_US translation.
For the broken links, it seems what is happening is that during the build pelican is trying to find e.g. faq.html, which is not built (we build faq.en-us.html instead) so it gets confused and outputs the link as './'. If the index.md file is modified as below, then the generated links work (but for English only).
[Take me to the FAQ!]({ filename} faq.en- us.md)