Download Form Feedback - 2022

 Better documentation regarding reverse proxy SSL configuration (nginx). Eventually found a posting that was a huge help in getting this configured and working, so fantastic to get this sorted
 Most applications default to a secure configuration, and would highly recommend that position with a class product like XWiki

 Improve the separation of access rights. Improve the separation of access rights. When I added access rights separately to the page, the access rights to the page and child stopped working

 To design a page it would be much more easier to work with areas like in confluence.
 The extension questions could be a little bit better. You and your team do a great work and we are very happy to use xwiki, thank you so much.

 Inside the WYSIWYG editor, there is a "Replace" function, but unfortunately NOT in the "Source" code. In my documentation I implemented 32 links to the online help of one of our programs and our IT changed the server. Now I have to replace the server and path for my 32 links. But inside the source code I have to do it MANUALLY. Please implement the "Replace" function also in the editor
 We tested the "Office Importer" macro to import one of our training documents. The whole MS-Word document with 257 pages and 56MB size could NOT be imported. For testing I reduced the content to 116 pages and 21MB. This could be imported but with a bad result ! Also the performance is NOT acceptable. If I write text, it takes 1-3 seconds to see my result and it is not possible to switch to the "Source" code in an acceptable time. So, the "Office Importer" is NOT useful.

 Try to support proxy out of the box, every company uses proxies, try to implement Markdown out of the box so you might not even need internet access.
 If you manage to install xwiki it will be one of the hardest things you will ever do in your life.

Answer from Vincent Massol (XWiki Core Dev):

 It seems your life has been pretty simple so far, good for you!
 More seriously: proxies are supported out of the box and Markdown too (just that not everyone needs nor wants it which is why it's not installed by default).

 Text-formating like colored text or striked thru text, background colors should be available in WYSIWYG-editor. Now you have to switch to sourcecode to modify.

Answer from Vincent Massol (XWiki Core Dev):

 This is done voluntarily to focus on content and promote style consistency in the wiki. However it can be turned on.

 How to set permissions to read-only? Restrict the content of others' articles
 Detailed instructions in Chinese

 If xwiki can use less memory, and can run on machines like a raspberry pi 3B+, it'll have a brighter future, because some people who use it may want to run it on an energy-saving machine like a raspberry pi or a cheap but poor-performance VPS, etc.
 I think you can try to add a "lite flavor", it will not create an empty wiki, but only have basic wiki features, and administration tools. I also think you can try to add a "custom mode" when xwiki is installing, which will not only allow the webmasters to choose the features they want, instead of choose a flavor, but also let them can adjust the basic settings when xwiki is installing.
 P.S. I'm poor in English, if I made some mistakes like wrong grammer, please accept my "sorry" for that!

 Documentation is a bit random and hard to follow at times, or even non existent (or maybe not findable by me). e.g. I was trying to find what the various fields when creating a themes for flamingo where. I gave up.

 Oh, the syntax .... it's taken me a while to work out how to reference headings and anchors but I have got there. I've used Markdown and even nroff in the past, so I'm generally familiar with the non-WYSIWYG interface (and actually prefer it). I have looked all over for proper worked examples, but all I saw was a repeat of the syntax guide already on wiki.org. I'd really welcome a page or series of pages with worked examples so we can see how this is done. I'd even be happy to help build this.
 I'm using xwiki because a lot of our data is linked in multiple dimensions, so getting reports of how information is linked is actually more important than the information itself, in some circumstances. I'm hoping to be able to create dashboards based on the linkages. Let's see how far we get.

 Better support for multi-language. The Blog is not working in multiple languages, and the translation/maintenance of multi-language sites is not very user-friendly.

 Implement a access rights information section (e.g. in page header, cf. Confluence) that informs users whether page/subpages are restricted or not. Imrove the Like functionality: Let users see at first glance who liked a page Implement a gadget for a dynamic list of most popular pages/comments etc. (cf. Confluence) based on clicks, interactions and likes over time
 I greatly appreciate this gorgeous piece of software!

 XWIKI is very good as a collaborative documentation environment, it is more flexible and feature rich than Atlassian Confluence. But for a full replacement for Confluence, a very important functionality is still missing – customizable export by templates to PDF and DOCX / ODT formats. This feature is very important for documentation, because it allows you to automatically generate stylized documents from wiki articles. This is very important, as it allows the technical writing team to concentrate on the documents and not waste time on designing the appearance of documents for the customer. There are great add-ons for Confluence: - Scroll Word Exporter - Scroll PDF Exporter. This extensions allow you to fully customize the conversion of wiki articles from Confluence to DOCX and PDF formats. The Scroll Word Exporter extension allows you to load templates with styles created in MS Word and use them when converting to fully control the style of documents. It works amazing! In addition, there is an additional Scroll Exporter extension that allows you to flexibly customize the export for article fragments. And it's very helpful! If XWIKI has functionality like the Scroll Word/PDF Exporter, it will be a super feature for documentation and will allow many companies to completely transfer documentation from Confluence to the wonderful XWIKI!

 collapsible text boxes somewhat easier interface customization (e.g. font sizes in navigation and menu panels) installer can be confusing, especially when using the distribution wizard

 Quite honestly, I particularly like the Confluence product and am only moving away because I cannot put sensitive documentation in a cloud hosted solution. I would suggest using their product and take inspiration from what they do well to enhance your product. eg: -Be more windows friendly, most businesses use windows servers, and the setup process on windows is arduous. Consider packaging the setup into a full stack all-in-one installer and you would have more people complete a proof of concept they can take to sign off -simple things like the sections option in confluence is very useful to have built into the editor -have a non-dev/non-expert user review documentation for xWiki, for example, setting up templates (https://www.xwiki.org/xwiki/bin/view/Help/Templates/), useful function but when setting it up, the "template to use" field was not obvious that it was just a normal page that can be used as the template, and then you search for xwiki create a template you get the same help page that does not describe what the "template to use" actually is (alternatively you could name that field, "Page to use as template")