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 dix...@gmail.com 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3f66bf7b-cdda-4679-97ca-9e0c195101dfn%40googlegroups.com.
