It would be nice to have a possibility to switch to the printable view via url parameters, e.g. www.mywikijs.com/en/home?view=printable will generate the page in Print Format, whereas www.mywikijs.com/en/home will keep displaying the page as it currently is.

The Site Title, Footer Copyright and SEO settings are all those that we would normally expect a theme manager to be responsible for not a site administrator, which in the Wiki.js context is a much more technical role.

It might be hard to integrate, but it would be a killer feature that no other wiki offers. Perhaps you could use ShareDB: https://github.com/share/sharedb https://en.wikipedia.org/wiki/Operational_transformation

It would be great, to add an embedded way for PDFs.

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.

For the same LDAP authentication strategy allow people from different LDAP groups (nested in one allowed to login into WikiJS) to be automatically assigned to different WikiJS groups.

There is insufficient logging of errors in Authentication Strategies such as Azure AD and Open ID Connect. I have Azure AD and Open ID Connect authentication strategies with callbacks that produce error 500 but there is no code to actually log those errors anywhere, leaving no ability to troubleshoot. A Dev Flag which logs all errors from Authentication Modules, similar to the LDAP one, would be useful.

current table designs is not appealing, would be col if table structure is similar to that of confluence wiki

A user can opt in to be notified when the contents of a page are updated.

There could be tool for checking existance of links used in all .md documents, especially internal links, from time to time we need to change folder structure, move a piece of info somewhere else etc... or external links stop working. link refactoring is planned, but additional testing tool could be useful from time to time...