The way I understand it, Tiddlyhost act like github page but use a put saver based on the WebDAV protocol, so we have one wiki that save change if the user is logged in with the right credentials. A wiki can be private or public, but there is no backend like with wordpress.
@simon has added a way to tell if the user is logged in by setting the login status in $:/status/IsLoggedIn, so it’s possible to switch the template used by the save button to trigger a download of the full wiki if the wiki was made with an external template, or hide some ui elements with a startup action: Read only TW — experiment for a read only wiki hosted on tiddlyhost
With saq’s plugin to embed external content from other wikis, I think it should be possible to have a bi-wiki setup, one with all the tools needed to create content, and the other that would recieve the content (minus the capability of editing). Then, maybe your uglify plugin could be used to trigger a save of the wiki in a compressed state ? @simon are you using uglify behind the scene ? If not, maybe you could make it optionnal to allow saving more space for your server ? I’m doing all I can to keep my tiddlyhost wikis as light as possible, but I’m dangerously reaching the 30MB mark…