Wiki.js

Wiki.js provides us with very powerful multilingual functionality, enabling creators to quickly build pages in multiple languages. However, document translation and synchronization are major issues, especially when there are many languages involved (for example, I have an 8-language wiki. When I create a page, I need to synchronize translations for the remaining 7 pages. Moreover, if I later modify this page, I also need to manually synchronize the changes to the remaining 7 pages). The emergence of AI will make translation and synchronization work much easier. Users only need to enter an API KEY to let AI help translate a page into various languages, and when the page changes, it can also be quickly synchronized to pages in other languages. I think this can be applied to the localization of pages and navigation. Based on my previous work experience, I can provide a rough workflow for your reference: Users enter the API KEY, API Base URL, and other necessary information on the AI management page in the backend, so that Wiki.js can correctly access the large language model. Users can use AI to select single or multiple items on the page and navigation management interfaces in the backend, and then use the AI translation function. AI will translate all content of the original page into the specified language, but will not change certain fixed paths (URLs, images, etc.). It is recommended to use the default language as the "mother tongue" to determine the synchronization status of each page and navigation. This is very simple: you only need to compare whether this page exists in other languages and check their last edit times to know whether the page has been synchronized. AI translation sometimes has problems, so manual modifications are needed. (According to point 3, manually modifying interfaces or navigation in non-default languages will not break the synchronization status.) Not all pages and navigation need to be synchronized, so a blocking option can be added. On the AI management page in the backend, a glossary of professional terms can be maintained for the translation of special content such as company names and proper nouns. I hope these suggestions can be helpful to the Wiki.js team and contribute to making Wiki.js even better. Thank you for your time and for your continued work on this excellent project.

For email authentication, verification token should not be one time used..there should be validity but should not be single.. current issue is that token is used by safelinks in Outlook and it got expired and customer facing invalid token issue..this must be resolved

search should gives result based on current user language. if its english then only show english pages,if it is dutch then only show dutch pages

When duplicating a page, please also copy the contents of the Scripts and Styles fields in the page properties.

I would like to stay informed about new releases of wiki.js and therefore want to embed https://beta.js.wiki/blog in my RSS reader.

When typing underscores (such as for file names), the WYSIWYG editor automatically replaces them and italicizes the text within. This is very annoying behavior. It's a particularly poor UX when you've already combated the editor successfully so your text has underscores in it, but if you then later on type another underscore. It will look back and match with a previous underscore that's far away. This disrupts large amounts of text in an unexpectedly non-local way. Here's an example of how annoying it can be. Imagine I have entered the equivalent of this HTML: <code>a_b_c_d</code> and some text. And sentences. Then a When you type an underscore, you don't get an underscore, you get this: <code>a_b_c<i>d</i></code><i> and some text. And sentences. Then a</i> If you type another underscore, this happens: <code>a_b<i>cd</i></code><i> and some text. And sentences. Then a</i> There seems to be no way to work around this until all of the underscores is gone. Very annoying. Solutions: preferred: remove this functionality entirely. If you want italics, you can use the toolbar or the keyboard shortcut or, at least disable this functionality within text that's formatted as "code" or, if you don't disable it then at least prevent the lookback from spanning across multiple words, multiple sentences, or multiple format spans.

It would be helpful if Wiki.js had an optional “Diagnostics” section in the admin area where we can quickly run basic checks on our instance (hosting, DNS, SSL, etc.) by opening external tools in a new tab. For example, a simple link to a free hosting checker like https://beingoptimist.in/tools/hosting-tools/web-hosting-checker/ could help admins verify where their wiki is hosted and troubleshoot issues more easily.

Now every time you want to upload an image, it's very troublesome, and it takes many steps. I recommend: All uploaded files are automatically categorized by year and month; Support Ctrl+v to paste directly into the editor with one click.

To use the Keycloak authentication strategy we need to customize the scopes. Therefor it would be great if this option, which is also supported by the underlying javascript module (keycloak-passport) would be available in as a configuration field.

Your docker images has no org.opencontainers.image labels. I need label org.opencontainers.image.version for kubernetes image auto-update features. Please add missing labels. Example build from HA: https://github.com/home-assistant/core/blob/dev/.github/workflows/builder.yml#L261 ## Examples of correct org.opencontainers.image.version labels: docker pull mariadb:10 docker inspect --format='{{ index .Config.Labels "org.opencontainers.image.version" }}' mariadb:10 10.11.15 --- docker pull mariadb:latest docker inspect --format='{{ index .Config.Labels "org.opencontainers.image.version" }}' mariadb:latest 12.1.2 --- docker pull phpmyadmin/phpmyadmin:latest docker inspect --format='{{ index .Config.Labels "org.opencontainers.image.version" }}' phpmyadmin/phpmyadmin:latest 5.2.3