Currently, all pages are published by default. You can flip the switch to deliberately un-publish a page. This is backwards to how it should be. A page should not be published by default, but rather published deliberately by command of the user (either by flipping the switch, or using an appropriate button labelled something like "Publish"). I have the following use-case: I work in a team with multiple developers. We use wiki.js to create documentation for our product. Since we work on it in parallel, we also have to each create different parts of a given page of documentation. Our customer only has read access to the wiki and thus can only see published pages. It would make a lot of sense for us to publish a page when its ready, not having to remember marking it as un-ready when creating it.

Currently when moving or renaming a page, all existing links point to the old page. The correct behaviour would be to update all links to the new page, either optional or explicit.

Support for child navigation items to allow dropdowns in the main navigation pane. If you have a large wiki, it can be hard to organize your pages without some type of collapsible navigation.

To be able to open images that are inserted on the page in a popup/modal window or in a FancyBox/Lightbox. Also, to have varius types of galleries, sliders and slideshows for the images.

A modular notification system. Users, User groups, Admins can be notified about events. For example: Content events (new page, updated page, deleted page) Admin events (new registration, failed login attempts, failed git sync,....).

When a user created or edited a page, it wont publish right away, rather have a admin or higher lever user to approve the modification, then publish.

Images should be pasteable via clipboard ctrl+V as a shortcut, similar to how Github's MD editor works. This would be a gigantic time saver.

Wiki.js should create a sitemap.xml on a standard path (e.g. wiki.example.com/sitemap.xml ) and dynamically update it as pages are added and deleted.

Currently, the visual editor is missing various features that are available in the markdown editor. Examples: changing the quote design, adding footnotes, and the option to add a horizontal bar. For a modern wiki system, it would be really nice to see all these features to be working in the visual editor, so that users don’t have to learn markdown.

Let's assume we have two people editing the same document. If Person A adds / changes a few lines in section 1 and Person B adds / changes a few lines in section 3 - that isn't a merge conflict that requires manual resolving. Both changes can simply be combined into one. If on the other hand Person A edits lines in section 1 and Person B edits the same lines in section 1 - that is a conflict that needs manual resolving. Someone needs to decide which parts of either edit should go into the final change. It would be great if the first type of conflict could be merged automatically, because the diff-view is really difficult to read and use. That would also be what people are used to from GitHub / GitLab or other version control platforms.