I've seen the security module under the rendering settings which appears to allow you to disable "strip javascript" however I don't think this works yet. Is this actually a feature that will be implemented?

Add possibility to use Google Analytics. This feature would you setting your Google UA Code and Wiki.js print on end page the code provided by Google to Analytics works.

e.g., fr.wikipedia.org/path/to/article instead of wikipedia.org/fr/path/to/article. I presume that within the github repo it'd still be stored as under the directory "/fr/path/to/article", but this is simply a request to make it possible to have subdomain languages.

Not sure if this isn't already included, couldn't find it in the docs. Being able to collapse long blocks of text would be usefull. I'm using wikijs 1, I'll be happy to wait untill the 2 release for this feature.

As far as I see, wikijs can only be hosted at domain root (http://wiki.example.com/). Would be cool if it could also be hosted at a subpath, like http://example.com/wiki/

Ability to recreate the complete content history from git when importing content. Ref: https://github.com/Requarks/wiki/issues/852

Depending on the window size, the blue navigation area on the left disappears into a round blue button with 3 horizontal white stripes. It would be nice to have the option to always (independent of window size) have the navigation area collapsed. This would maximize screen real estate in some cases

I don’t mean how to write Markdown. I can do that in my sleep. I mean that getting-started documentation that demonstrates how to actually USE Wiki.js. I’ve installed it. Now how do I use it to improve my life? Every other wiki (even the smallest) seems to have a guide for this. Perhaps it has been misplaced? An example of the expected content: How to reference internal pages; How to embed a PDF; Syntax for this kind of rendering, that kind of rendering, and so on; How to build a simple TOC for internal pages; How to reference filesystem files.... Having a demo built with Wiki.js (the docs page) is a good idea, but how would one see how it was made (the markdown Source)? I have put considerable effort into trying to locate answers to these questions but have come up empty. The system (v1) looks promising but this kind of a guide is vital.

Similar to personal spaces in Confluence, essentially a sub-wiki that a user has complete access to. That way any personal projects/pages can be a subpage of that user's personal space or profile, keeping it slightly distant from the main wiki. The user has full control over who can read/write in his/her personal space.