Although I would have preferred to use Koa template, it had to be Napili because it is the only one that allows you to show Custom Objects and multi language is only supported on Napili. And the Salesforce communities showcase site - Eway is on Napili - and it has a PKB, so I thought it would all work fine.
So I did a test run first. However the two things I did not test have made me come unstuck, and now I have to say DO NOT TRY TO DO A PKB on a Standard Communities Template. Just don't. It doesn't work. And don't try to do a multilingual public site on Standard Communities Template. Just don't. It doesn't work.
Now, in researching writing this article up today, I did find this ONE tiny snippet in the Winter '16 release notes
- Article smart links (links from one article to another) aren’t supported.
Start with Setting up Knowledge on Communities to do the setup and see all the gotchas.
(Sorry, the community in this example is not working right now. I will have to get it up and running again in my spare time. Lolz, what even is spare time).
- Have no linked knowledge articles at all - this is how https://go.eway.io have gotten around this issue
- If I maintain the two PKB apps for Brand A and Brand B, it means I would have to replicate ALL The content in my knowledge articles to create completely new knowledge articles for Brand C then ensure there are no Smart Links used.
- If I go to three (or more - we are planning more) branded customer communities using the community templates, which is the goal and why we first created this first community as a testing ground rather than using the awful PKB3 app again, we would have to replicate EVERY ARTICLE THREE TIMES and ensure there are no smart links used. And of course you can't just clone articles, you have to copy and paste into a new article.
- Create 301 redirects on EVERY article manually so that they redirect back to the community. (That's what I did).
Why would a company trying to produce enterprise level software and really push communities as the future of the way things are done, have such a glaring bug that means you have to duplicate content multiple times. That is just such the antithesis of what Salesforce is about.
This idea and and this idea both seem to suggest that Salesforce Support say it is a feature and by design!!!!! It can NOT be a feature, this can NOT have been thought about and the answer be that it is the way it is meant to work!!! it is a BUG - pure and simple - a BUG.