Redefining Flag Clicks

At present clicking on a page flag reloads the site, either displaying only the welcome-visitors page if the reader clicked on the welcome-visitors flag, or both the welcome-visitors page and the wiki-page whose flag was clicked on, should the reader click on a different page-flag in a lineup.

This user interaction is confusing, and lacks flexibility. it is confusing because users have no idea what this functionality will do before clicking on it, and the changes to the lineup that result are dramatic and surprising the the user.

# Tool dialogue

The proposed change is to instead open up an authoring tools page to the right of the wiki-page whose flag has been clicked.

Should there be wiki-page in the Authoring Tools Folder with the same slug as the page-flag clicked on, then that page will be displayed (outlined with a Halo of Integration). If no such page exists, then the Welcome Authors page would be presented again with a halo).

# Tool-page example features

An authoring tools page can be customised with any transporter. By convention these authoring tools would not change the way wiki functions in terms of refactoring, or the way a site looks or is configured.

Examples of the sorts of tools that may be useful here are:

- Existing flag behaviour (refresh site) - Delete Page - Rename Page - Remove from Lineup - Display Journal - Manipulate Journal - Search for similar pages in federation - Find related pages in Wikipedia for import - Export as markdown

Now that we have space for navigation to a large number of tools, we can also link to or display the means to author Transport-proxy JSON. This (and other site-wide configurations, could be placed on the Welcome Authors page or linked from there to a configuration tools page.

# Not yet specified

i am unclear at this stage whether configurations tools, and authoring tools need to be distinct classes of tool. My suggestion is that we start with authoring tools, and can move later to see if we need other wiki dimensions to specify separate classes of functionality. This can easily be done by creating another tools folder, and utilising a distinct halo colour for that dimension.