Wiki.js

I would like to have an option to created colored text while using the visual editor.

When editing a page in the visual editor, there is no setting to change the text color. Will it be added?

It would be nice to have some basic options with respect to how Headings are styled. For example, for H1, H2 and H3, you can control whether they're indented, have a border, their size, and font color. I'm sure style in general is something that could be a site-wide thing, but the headings might be a good place to start.

Changing the color of the text on the page would be a very useful feature!

It would be beneficial to provide a area in which to create some content variables. This would be useful if there are items to be included in several pages of the wiki, but subject to frequent updating. This way a single change would be reflected in the whole structure.

Currently when moving or renaming a page, all existing links point to the old page. The correct behaviour would be to update all links to the new page, either optional or explicit.

I have a requirement to allow pages to be loaded with information stored in a database. Would it be possible for a wiki page to display this information in a table and text area?

Sample table: | | Grouping || Grouping 2 || Not Grouped | | First Header | Second Header | Third Header | Forth Header | Fifth Header | Sixth Header | | ------------- | :-----------: | -------------: | :----------: | :----------: | --------------- | | Tall Cell | Long Cell || Long Long Cell ||| | ^^ | Bold | 1. first item | Italic | 3. third item | + first point |\ | ^^ | | 1. second item | | 1. forth item | + second point | | New section | More | Data | ... - -- --- ||| | And more | With an escaped \| || "Try 'quotes' in quotes " ||| gets displayed correctly on the editor, but the result when viewing the page is wrong, compare screenshots

This would allow wiki.js to be used for checklists with an easy method for checking of items.

Although a wiki is a collection of pages, often they are organised in a tree structure. If you want to move a page that is at the top of a subtree and all pages below it, that is very cumbersome. Adding a "move tree" function would greatly simplify moving, or renaming, subtrees and keep consistency.