The trouble with the word “static” is that it has several meanings depending on ones frame of reference.
Conventionally, a “static web page” is one that is served directly from storage, with no processing on the server to customise the page. Ever visitor gets the same file back when they request the page. In that sense, TiddlyWiki itself is a static web page; it’s one of TiddlyWiki’s most important properties that it can be uploaded to the web and it just works. But, we also use “static” in a slightly different, more browser-centric sense, meaning a page with no JavaScript, or one that can be used successfully with JavaScript turned off. TiddlyWiki is emphatically not a static page in that sense; the main HTML file won’t load at all if JavaScript is not available. So, in TiddlyWiki, the distinction we emphasise is that between TiddlyWiki itself running in a single HTML file, and “static pages” in the sense of not needing JavaScript. As Thomas notes, static pages can be exported from TiddlyWiki in the browser or under Node.js. Now, the advantages of exporting static pages are that: a) it’s easier for Google (and other search engines) to index the content b) the content will generally load faster because the file size is reduced by jettisoning the TiddlyWiki core c) they will work with any browser on the planet, regardless of JavaScript settings. For me, the sweet spot is being able to edit and curate content in the full TiddlyWiki user interface, whilst giving readers the simplest possible interface to navigate the results. Best wishes Jeremy. > On 2 Mar 2017, at 09:29, BJ <[email protected]> wrote: > > in this case static mean a page 'build from fixed html' - ie uses the browser > to parse html into a dom, as opposed to tiddlywiki that creates (and > recreates) the dom from a (dynamic) list of tiddlers. > > On Thursday, March 2, 2017 at 8:24:41 AM UTC+1, Mat wrote: > To be honest, no really great answer so far ;-) ...but, I guess the main > point with a static TW is faster/easier for the visitor to load. > > Wikipedia states: > > A static web page [...] is a web page that is delivered to the user exactly > as stored, in contrast to dynamic web pages which are generated by a web > application. > > But vanilla TW seems to qualify for both. So I wonder what disqualifies > something in TW from being exported into static? > > * anything that relies on JavaScript > > ... more? > > And, for us mortals, what are the practical consequences; Which widgets are > disabled? Other? > > BTW, this indicates it is a good idea to try to replace JS functionality in > TW core with CSS (!) when possible. Comments on this - @Jermolene ? > > > Tobias wrote: > > Static means node generated sites [snip] > > I'm not sure that's correct since single-file TW also can export static. > > > <:-) > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywiki > <https://groups.google.com/group/tiddlywiki>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/56f2feb5-b975-4cd6-aef0-096ef427f8e7%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/56f2feb5-b975-4cd6-aef0-096ef427f8e7%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/B3ABC59E-A7CB-465C-A3D6-2316792BC3C7%40gmail.com. For more options, visit https://groups.google.com/d/optout.
