Share your feedback...
A more editor-friendly approach to asset management
Many times, images uploaded by editors will only be used in one page. So can a more convenient way of managing assets be added? For example, if the editor is editing /aaa/bbb/ccc, he can upload the image img.jpg directly in the page, and the image will be automatically stored in a path like /i/aaa/bbb/ccc/img.jpg. Within this page, the editor can use the image directly by url "img.jpg", and the html renderer will automatically complete the image url to "/i/aaa/bbb/ccc/img.jpg". When the editor deletes all img.jpg from the page and clicks Render, the renderer checks if the files under /i/aaa/bbb/ccc/ are used in the page. If not used, the file is deleted. Administrators can see the size of the assets owned by each page. This helps simplify the rules of image uploading and can remove images that are no longer used in a timely manner. Developers can set users to only allow access to assets on that page to enhance asset security.
Review Pages frequently
Have the ability to mark pages as needing a review every x days/months to ensure information is kept up to date
Export Pages to PDF
Looking for a nice way to share (formatted) wiki pages with external links intact
Find and list pages containing broken links
It would be great to have an administration tool in "utilities > content" which would allow to list all pages containing broken links. The tool should be able at least to list broken links pointing to internal pages of the wiki instance. An advanced feature could be to list broken links that point to external pages. It would ease greatly the maintainance of the wiki and keeping it up to date. Thank you in advance
Tag users in native comments
Add a feature to tag/mention other users of this wiki in native comments (e.g. ' Hi, @AndrewK') with autocomplete suggestions. The tagged user should receive either an email notification or a notification in the user area in the wiki itself.
Notifications / Email on select events
A modular notification system. Users, User groups, Admins can be notified about events. For example: Content events (new page, updated page, deleted page) Admin events (new registration, failed login attempts, failed git sync,....).
Enable comments by page or some node
I would find it useful to only enable comments on some pages. For now you either allow or disable comments for the full wiki. Enabling/disabling comments from a site tree with checkboxes, hierarchically-aware would be best IMO. If you enable a node, all leafs are enabled. Or some matrixing.
'Scripting' section for documentation and update graphql docs
Request from those who are new to graphql and also those who want to script user creation etc. Update graphql docs section with a real example, including giving authentication header within graphiql (screenshots), pointing to query samples in graph/admin/users section etc. With some real scripts which will work from command line, including how to get authentication token and use it in script.