Wiki.js

I would like to use wiki.js as a knowledgebase for incoming employees an present them directly our video natively in the wiki, no links or downloads, just start the video right away from the article. this would be great, if you could make it possible to natively integrate videos such as .mp4!

We use a knowledge base system where users see changes to documents, and one needs to press the "I have noted the changes" button for acknowledging those changes. Admins then can check if users have read the new information.

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.

Currently the default language is saved within the Git repository root instead of an appropriate locale dir. Unfortunately, that creates a bug where Git repository link to edit by volunteers is pointing to a non-existent file, which would be in the locale dir, but resides in the root dir instead. Simple solution would be to save all locales to their respective directory, regardless of whether it is a default locale or not. This solution also makes sense from the semantic point of view, as each language has a distinctive directory. If we were to change the default language from Czech to English in the future for example, then what would happen to the files? The Czech locale would be transfered to "cs" directory, and English locale would suddenly swoop in to the root? That doesn't make sense. Because of this inconsistency, our wiki, which default locale is Czech (cs), GitHub link for external edits points to an invalid resource, and as such people might be confused. This suggestion was posted as per request in GitHub discussion for a related bug report: https://github.com/requarks/wiki/discussions/7121

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.

after working with confluence for several years now editing in wikijs is just kinda painful. three editors and none of them allow me to "just write". what's missing? keyboard shortcuts, especially for ... * inserting tables * inserting headings (CMD-<number> in confluence, so good) * formatting text (CMD-b/i/...) * inserting anchors * editing / saving a page ("e" or "CMD-s" in confluence, easy) there are a couple of tickets already open, so i guess i'm not the only one :)

Allow a page on the wiki to display which other pages on that wiki are linked to that page.

Looking for a nice way to share (formatted) wiki pages with external links intact

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

Sometimes you might have a page that could go under multiple titles. Mediawiki handles this with a thing called "redirects". This kind of feature is espc needed in any large wiki since with multiple editors you can't count on people following the same naming standards.