Some work on static sites

[RichardWilliamSmith]

Dear all,

I made a static site with Tiddlywiki and a tutorial explaining how I did it: https://www.didaxy.com/exporting-static-sites-from-tiddlywiki

There is no great innovation to what I've done but it packages knowledge from lots of different places into a set of instructions that I've now tested. The tutorial also explains how you can host your static site and how you can manage images, which may be of more general interest than the rest of the tutorial.

I've made my work available as a plugin and a github repo and I hope that, if you're interested in this sort of thing, you will be kind enough to give me your feedback about anything that you think I can improve.

This is still experimental so, although it carries no particular risk, please back your work up as always before using it, if you choose to.

Regards,
Richard

[@TiddlyTweeter]

Ciao RichardWS

I made a static site with Tiddlywiki and a tutorial explaining how I did it: https://www.didaxy.com/exporting-static-sites-from-tiddlywiki

A few comments ...

1 - Far too modest.
Don't underwhelm your audience.
As far as I can see this is documentation of a fairly developed CMS web-site PUBLISHING SYSTEM.

2 - Saying its "static" generation sorta separates the mother from baby. But I don't think its accurate. Your method, even if you yourself don't go that way,  could ALSO generate dynamic sites (i.e. that include JavaScript).

3 - I think that more upfront, probably in the Title, you should make clear this is a NODE.JS mediated CMS. [Its important in the sense that on GG there is a lot of discussion about "static" TW. Frankly, most of it is confusing truly STATIC sites with REDUCED ACCESS interface a lot of the time. You want to avoid getting mixed into that confusion like the plague.]

4 -  The DETAIL in your tutorial is great to read.

5 - A wondering? Is this compatible with what Riz did? If so, then a link to his examples could be helpful adjunctive to display the potential in a strongly visual way.

Very best wishes
Josiah

[RichardWilliamSmith]

Hi Josiah and thank you,

Could you please point me towards the work of Riz? I don't think I've seen it and it would be very useful to see what other people have done. The other work I found that was useful to me, in addition to Jeremy's docs, was by Welford: https://github.com/welford/twstaticblog

Indeed static sites are poorly named - the only thing that's static about them is the deliverable assets at any instant in time. In fact Tiddlywiki itself is usually delivered as a "static" asset but is, of course, very dynamic once on the client.

The main win for me in setting up the system as I have is that I now have effectively "one click" publishing from TW on my desktop to the Netlify global CDN, so my site has the same up-time and availability as some major sites (https://www.netlify.com/case-studies/). All I have to do is tag tiddlers "Live" and run a Git commit and the site gets rebuilt "in the cloud" in about 30 seconds. One more reason to love Tiddlywiki.

Regards,

Richard

[@TiddlyTweeter]

Ciao RichardWS

Riz's demo of his site builder is here ...

    https://ibnishak.github.io/t-blog/

He provides several completed examples.

Documentation: https://ibnishak.github.io/t-blog/Documentation/Hello%2520There.html

Repository: https://github.com/ibnishak/t-blog

Best wishes
Josiah

[@TiddlyTweeter]

Ciao RichardWilliamSmith

Just a footnote.

The main win for ... is ... "one click" publishing from TW ...

 

... tag tiddlers "Live" and run a Git commit and the site gets rebuilt "in the cloud" in about 30 seconds.

Right. And comments like these would be appropriate as bullet points in any up front "marketing" :-)

Best wishes
Josiah