I would create a custom button to export a public version of the wiki and publish it, stripped from private tiddlers. You could use this:
\whitespace trim
\rules except wikilink
<$wikify name="site-title" text={{$:/config/SaveWikiButton/Filename}}>
<$let publishFilter="""-[tag[private]]""">
<$button tooltip="Download a public standalone wiki" aria-label="download full public wiki" class="tc-btn-big-green">
<$action-sendmessage $message="tm-download-file" $param="$:/core/save/all" publishFilter=<<publishFilter>> filename=<<site-title>>/>
{{$:/core/images/download-button}}
<span class="tc-tiny-gap-left">
Download full public wiki
</span>
</$button>
</$let>
</$wikify>
Mark the private tiddlers with a “private” tag.
You could also use the command line, Soren use a tool he built in python:
A vanilla instance, yes. There is a plugin that uses the sjcs.js tiddler to encrypt individual tiddlers.
It requires you to keep the same title and remember the password, so in practice, two keys.
But I do agree with you none the less that really, the safest option is to simple export it from the wiki, if you worry about someone reading the contents of said tiddler.
My wiki https://wiki.onetwo.ren/ only contains 1481 public notes, but has 13942 notes in total when using it on my PC. Where public and private notes can link to each other.
Simply add a tag “Private” or “Public” can switch the visibility.
In TidGi app, I provide out-of-box way to do this. See its doc. It is a nodejs wiki, you can use same technique in nodejs wiki if you are a tech expert.
If it’s just a matter of what’s clearly displayed to web visitors, you might consider one of the ReadOnly solutions. These hide all editing interfaces, and easily change what people see, when the wiki is viewed online (rather than in TiddlyHost logged-in mode, or via file protocol).
I love it for a constantly dynamically-edited wiki, because I have no separate “publication” step, but I always see the stuff I need for editing and drafting and organizing, and my viewers never see it (unless they’re peeking at source, etc.)
It’s true that all of my wiki can be seen by a determined hacker, except any tiddlers that are encrypted… (which you might consider if you need that). But the readOnly solution is plenty good enough for ordinary web visitors to be shown only what I want them to see, and not to be distracted by things (not only tiddlers, but GUI elements specific to editing) that are not there for them.
Hi,
I’ve tried the second method. It does hide the editing interface but I want to control wich tiddler I want to show. Is it possible to achieve that with that method or do you use the Encrypt Tiddle plugin for that?
Thanks!
@Kartoushh how do the tiddlers come to be seen?, I mean is it already open?, is it opened from the contents?, was it found using the search?
Unless a user can find the title they can’t open it, so I am sure we can do other things to make your unpublished tiddler not be listed and thus not opened. However when you are using the wiki you don’t want this to get in the way.
The easiest way is to make them system tiddlers and rename and remove the $:/ when ready to publish. If you call them $:/draft/tiddlername then even if a user finds it they will guess its not ready to take seriously.
We could make a button, only you can see, that allows a click to add/remove the $:/
I am confident you could use the bags to control one set of tiddlers vs another. What tools allow tiddlers to be moved between bags is the next question.
They can be seen through search and thought internal links of other tiddlers.
Also I’d like my visitors to be able to see the sidebar.
The easiest way is to make them system tiddlers and rename and remove the $ when ready to publish. If you call them $:/draft/tiddlername then even if a user finds it they will guess its not ready to take seriously
Hey that seems easy enough! So far I like it, thanks a lot!
when ready to publish. If you call them $:/draft/tiddlername then even if a user finds it they will guess its not ready to take seriously