Wiki.js

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.

Upon page creation, the ability to set a lifetime or expiration for the content that when lapsed will trigger an email or notification to the page creator and site admin. This would automate the process of revising and refreshing documents that would otherwise go stale.

Context Page not found will show up if you: Actually want to create a new page Didn't find correct page In the 2nd case it would make sense to have search option. (Note: Also works as a built in duplication prevention)

Drawio has some powerful interactive features to add (custom) links to subpages within the diagram or adding actions for showing/hiding layers. This is especially handy for creating navigatable BPMN diagrams and show sub-processes when needed. (or for SW/System/Enterprise Architecture Modelling ...) This can be achieved by simple HTML Embedding provided by drawio, but instead of a manual HTML Embedding (with time-consuming round-trip), it would be great to just be able to show the drawio diagram directly as a HTML Embedding instead of a static rendered PNG/SVG image. Just check this tutorial: https://www.drawio.com/doc/faq/embed-html And check the options: https://www.drawio.com/doc/faq/embed-html-options Some more interaction features: https://drawio-app.com/blog/interactive-diagrams-with-custom-links-and-actions/ The feature is very easy to test and works great.

Have a setting in Wiki.js where you could setup posting updates to certain webhooks everytime someone commits an edit or reverts an edit, creates a page, deletes a page, uploads an image or a video or some other file, a comment is made on a page, a new user registers, a user account gets deleted or a user gets blocked etc. This would be very usefull for people who use Discord, Slack or any other application that supports webhooks.

It would be great to be able to define words as "knowledge items". This could be internal/product-specific terminology, names, educational topics, etc. When writing these words into a new page, you would proceed the word(s) with a hash symbol, this would provide a auto-complete list based on your input after the hash symbol, and then auto-highlight the knowledge item when pressing enter on the chosen item in the list. Once highlighted, the user could hover over these knowledge items while viewing a page and a short description would be provided in a popup. This could be a word definition, a product owner comment, a statement, etc. The descriptions would be set by the editors in a Knowledge Item management page, similar to tags. Knowledge Items would be handled wiki-wide and permissions to add/edit them could be included. Additionally, certain Knowledge Items could be given an associated wikijs page or external URL, so that if it is clicked by the user, they are taken to that given page. Knowledge items could have a default highlight colour applied when created, so that when automatically highlighted in a new page, the colours remain consistent (perhaps colour could be used by the user to mean context, topic, etc). Another additional feature with this would be to allow icons to be assigned to Knowledge items. The same icon sets available for the navigation. They would appear to the left/right of the knowledge item text in the page, and show in the popup as well. This is just another visual indicator of the knowledge item existing. You can think of this similar to Twitter's hastag emoji. Including knowledge items as part of the search functionality would also be great. Example attached

It would be nice if there was a feature to add a read receipt to articles. That means that when you log in, for example, you see a notice that you have to read an article. There should also be a box that says something like "I have read the article and confirm that I have understood its content". On the other hand, there should be a way to see who has read it. For data protection reasons, however, it should be possible to limit this view to individual persons.

Automatically creates links to Jira issues and automatically add remote issue links back to the wiki pages where these issues are mentioned.

Currently there is not a splash page that creates a process gate where users must click I Agree to continue. The best option for now is to have your ToS on the landing page after logging in so users see them, but in the US this is method is less sure to create an enforceable agreement to the Terms of Service than an I Agree button or checkbox with button. Would also need logging for the last date they accepted the terms. This might also be useful for cookie acceptance or privacy policy, etc. A nice to have would also be schedule the ToS acceptance button to appear on a schedule.