as a follow-up, I am now back to a single-file TW. I am also no longer invoking the TOC via macro, just simple HTML using toc-selective-expandable. For some reason using the macro was indenting everything, adding ordered list numbers, and causing most entries to wrap and generally creating chaos in the layout display.
On Saturday, December 19, 2020 at 8:35:35 AM UTC-6 Glenn Dixon wrote: > ok, I should update this. While the 'toc-tabbed-internal-nav' is nice for > displaying, it's not so great for actually *using* on my local desktop. As > in, you can't actually open any individual tiddlers from that view. Which > kinda defeats the purpose, no? > > So, back to a more traditional TOC structure. Unfortunately the expandable > items are still NOT expandable in the exported HTML files :( So - I'm back > to square one on my original question... > > On Saturday, December 19, 2020 at 6:08:17 AM UTC-6 Glenn Dixon wrote: > >> I assure you, I am *not* missing the point. :) Most of my static sites >> are html, but they also tend to have at least a splash of javascript. The >> whole 'jamstack' thing. Generally just for menu toggling, similar to what >> the macros do inside TW. >> >> I am using a static site because I want to simply display my TW publicly, >> w/out being editable. So are you saying that's not possible w/ the >> single-file TW? Would this be easier w/ the node.js version? >> >> On Friday, December 18, 2020 at 10:13:34 PM UTC-6 TW Tones wrote: >> >>> I think you are perhaps missing the point of a static site. >>> >>> Sure you could redesign the way the static site export works but the TOC >>> internal nav uses macros and widgets that are not active in a static site >>> by definition. >>> >>> Why are you using a static site? >>> >>> My personal interest is a static site where all static pages links are >>> to the tiddlers full wiki, with a splash screen to warn of loading. >>> >>> - The static site would then have static tiddler files for search >>> engines etc... but as soon as you need interactive features it loads the >>> full wiki. >>> - You could generate a static html tiddler from your TOC internal >>> nav then export that. Keeping in mind it becomes static ie does not >>> respond >>> to interactive code. >>> - It may be possible to generate a site index and robots file to >>> support single file wikis without a need to export a static site. >>> >>> Regards >>> Tones >>> On Saturday, 19 December 2020 at 12:25:55 UTC+11 [email protected] wrote: >>> >>>> >>>> My local TW uses toc-tabbed-internal-nav and each section expands when >>>> clicked. But if I export the site, nothing expands when clicked, so all >>>> the >>>> sub-tiddlers are inaccessible. >>>> >>>> Do I need to do something special with the export code? >>>> >>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/94cd3072-a770-4f05-8f3a-6eb720bee3afn%40googlegroups.com.
