Boards

Wiki.js

Powered by Canny

Wiki.js

DO NOT ASK QUESTIONS / DO NOT SUBMIT BUG REPORTS HERE! Use GitHub Discussions instead!

Save current state of the buffer when editing a page, so in case the page is closed or the browser crashes, the work is not lost. This would work better with a warning when the page has been changed since the time the draft was saved.

planned

Detailed search

To further highlight pages where keywords are found or with sub search results for hits of the keyword searched.

added in v3

Moving/renaming multiple pages

It would be very useful to be able to move multiple Pages at the same time into a different hierarchy. If I want to move 5 pages from /root/folder/page1-5 to /root/parent/child/page1-5 , currently the only way seems to be to open and move/rename each page individually. This becomes a bigger inconvenience the more pages are added in the hierarchy. Maybe being able to select multiple pages for a rename/move in a single overview?

Change "Site Tree" navigation to redirect to folder landing pages

One of the more serious problems with Wiki.js is the navigation which to many is unintuitive. (If you search the net, you will actually find multiple evidence that people have avoided Wiki.js for just this reason.) I found that there was a PR in progress/draft that tries to remedy this. So I decided to make this feature request so that people can vote and show their support for this change. (You can go there a make a Thumbs-up, too...) ( https://github.com/Requarks/wiki/pull/2933 )

Add accordion feature in the content https://getbootstrap.com/docs/5.0/components/accordion/

Allow to select ToC depth level

Current ToC depth level is hardcoded to 2. Should be possible to change globally and – best – override per article.

in progress

Better markdown tables formatting

Writing tables in markdown is very difficult and annoying. It would be nice if you could add this ( https://github.com/susisu/mte-kernel ) or similar package to handle them. This looks easy to implement, and could improve markdown a lot. A little effort will bring many benefits.

planned

Specific diff version in URL

change link in history view to reflect currently selected diff source and target versions. (e.g. add both target and source commit ids in the link)

Image links open in new tab or modal

I'd like to have images on my pages that have been resized, to be clickable to view the full image in either a modal or new tab. Closest workaround is to wrap the resized image in a link pointing to the image path, however that opens in the same tab when clicked.

Allow user to configure UI language independent of page content language

At a multi-language company, many users with different personal language preferences may be working with many different pages in different languages (e.g. updating code examples). wiki.js should display the UI elements (navigation/controls) to a user based on http Accept-Language if the requested language is installed (otherwise site default language). A user with a login/account should be able to override their Accept-Language language preference in their user profile settings to one of the installed languages. Not all users know how to get their browser to change Accept-Language header...and they shouldn't need to. For instance a user who has personal language preference (browser Accept-Language ) of es on a wiki that has only installed de and en with a default de can go into their user preferences and select en as their preferred UI display language. A user with language en or en-US should be able to edit a de-DE page on the wiki without the UI controls changing to German...ie edit German language page with English UI controls (or vice versa). The implication here is that user language for UI internationalization purposes needs to be treated/handled separately from the page content language paradigm. I understand we want to be able to set <html lang="XX"> when rendering the pages...however lang can be set differently on the content editor/viewer container than it is on the root html or body tag. So I don't think this should be a problem. https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang I felt like I already posted about this somewhere but couldn't find it on canny or github...so I don't know. But it comes up often with our users.

Load More

→

Powered by Canny