Good day,
I feel like regarding that, it would be necessary to really come to an agreement in regards to certain aspects. After all, most requirements we agreed on previously in that or other threads have already been achived in one way or another.
Let’s go through them one by one:
How does the new solution make sure translated pages do not get out of sync? I.e. when the English original is modified, how is this change reflected or at least noted on the translated version?
Well, similarly to Mediawiki, not at all really. Since Mediawiki has always kept the translated pages and the original fairly seperate, that has been what I set out to achieve as well. With Github as the base, and some tinkering with Jekyll, it seems to work, for now.
Can we make it pretty? Usable, modern presentation?
In the “New Website Thread”, I have already demonstrated and discussed a few designs. Whether these are presentable enough however, would have to be decided, as well as the question, which of the many mock-ups/attempts now should be used (i.e. categories on the side, long page, etc).
Can we have a mostly imported migration process from the old to the new wiki?
What about internal links?
What about wiki templates?
What about special markup such as {{Code2|…}} etc?
Since this is mainly being discussed for the short documentation, this question isn’t really important for this discussion.
Can we add meta tags (for seo, social media)? (Example below.)
There are different ways to achieve this with Jekyll, however I didn’t really test any at the current point in time.
Regarding things like “Expand buttons”, to enhance documentation, I already wrote about that in the post above.
Have a nice day,
Ego