Wiki.js

Wiki.js lacks a true plugin architecture that allows developers to create, package, distribute, and install extensions without modifying the core application. This limitation creates several problems: Developer Friction: Contributors must understand the entire Wiki.js codebase and build process to add functionality Maintenance Burden: Custom modules require manual integration with each Wiki.js update Distribution Challenges: No standardized way to share modules with the community Enterprise Adoption: Organizations cannot easily develop proprietary extensions Innovation Limitation: The community cannot rapidly experiment with new features Limitations of Current System: Modules are tightly coupled to the core codebase and must be present at build time No mechanism for dynamic installation or removal of modules Limited to predefined module types (authentication, storage, rendering, search, editors, analytics, logging, comments) No version management or dependency resolution No marketplace or discovery mechanism Updates require rebuilding and redeploying the entire application Third-party developers must fork the repository to add custom modules

It would be useful, for non technical users, to have a draw.io integration in the Visual Editor (like BookStack has).

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

If someone needs to update the list of attachments, the user will click “cancel” and log in again. It's bad to show him a full-line function that I can't even think of using. p.s. You have made a cool product in terms of functionality, but I would like to wish you a designer who will make wiki.js for people.

I want to insert a picture that is already in the database. You're making me look for her url, but even when I find it, I can't find it in the assets list - there's no search.

When editing pages, if you click “insert picture”, you open 100500 windows and the only visible buttons are the buttons for editing the page, not for inserting a picture. It is necessary to: remove this menu when inserting images. The user wants to close the image insertion and clicks to close editing the page, losing all content. raise the “cancel” and “paste” buttons to the top, because they are NOT VISIBLE. ps. If a user needs to get used to an interface, this is a bad interface.

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.

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.

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.