I am getting to the stage of making my TW publicly accessible. So, I am thinking about what to show and hide through the main UI. Can I get some ideas from people who have done this before, what facilities did you hide/configure and how?
bobj
I am getting to the stage of making my TW publicly accessible. So, I am thinking about what to show and hide through the main UI. Can I get some ideas from people who have done this before, what facilities did you hide/configure and how?
bobj
It all depends on who your audience is and will they care or use what is left.
Unless you want to hide all the edit features then look for read only themes and settings.
Standard hiding is no guarantee of security if that is what you are looking for.
I have a number of wikis that are for general consumption but with only a few editors. The editors view the wiki over Node and have full access. The public sites are on GitHub Pages or GitLab Pages, derived from the edits we made in the Node version and committed to git. Almost all of these are behind corporate walls, but a framework I started for creating them is at https://crosseye.github.io/TW5-Tiddox/.
In either view, you can toggle read-only mode on or off with a keystroke (I usually use CTRL-SHIFT-/
.)
In read-only mode the following buttons are hidden:
clone
delete
edit
new-here
new-journal-here
import
manager
new-image
new-journal
new-tiddler
control-panel
save-wiki
info
as well as the tools
and more
sidebar tabs. Also drag-and-drop is disabled. This is mostly done through a few tiddlers cherry picked from Mohammad’s utility plugin, plus one custom action setReadOnlyOnReload.
Of possible use:
The hide macro can probably be modified to work in reverse, i.e to show specific elements in certain tiddlers of your choice.
Thank you everyone for your ideas and thoughts.
bobj
Just another idea.
You could tag tiddlers “locked” and use the stylesheets attached to hide the buttons.
locking-tiddlers.json (1.4 KB)
to expand on this i’d recommend assuming anything on the site is public information. i would recommend treating anything hidden via template changes etc. as “getting rid of unnecessary ui elements / irrelevant information” and not “users should not know this information / this is private”.
Absolutely. In my case, there’s nothing hidden that would be worrisome if they saw it, and they cannot save changes back to the server. It is mostly a matter of showing them the content without bothering them with (to-them) useless options for modifying that content.