I have been working on exporting a subset of my tiddlywiki as a static
blog. You can see my work in progress
here https://dl.dropboxusercontent.com/u/41230376/blogtest/index.html All
the posts aside from the top one are nonsense.
Some of the features are : To make up for the lack of a search I
dynamically (at generation time) create tag pages so any article tagged
with the same keyword as the current one can be easily found by clicking on
the tag itself. I also generate the index by transcluding the 5 most
recently created articles tagged with "blog"
I really like the static export feature, but I have run into several issues
which i write out on the top most article of my site. Copying them here
they are:
1. I can't get the highlight plugin to accept custom styles when exported.
It looks as though the tags get stripped out. The CSS data is exported
however. Katex seems to work though
2. Batch building has issues
I output everything individually as i have found that grouping
rendertiddler commands causes issues. e.g.
"index": [
"--rendertiddler", "$:/core/templates/static.template.css",
"static.css", "text/plain",
"--rendertiddler",
"$:/themes/welford/phasersonkill-static/templates/static.index.html",
"index.html", "text/plain"
],
Results in index.html being empty, where as
"index": [
"--rendertiddler",
"$:/themes/welford/phasersonkill-static/templates/static.index.html",
"index.html", "text/plain"
"--rendertiddler", "$:/core/templates/static.template.css",
"static.css", "text/plain",
],
results in static.css missing my phasersonkill-static css data.
exporting them individually as shown in Exporting The Blog (see the
original post) works as I expect
3. RenderTiddlers deletes all existing files from a directory
This is an issue for me because of the following and previous issues. I
output a kind of dynamic set of tiddlers which keep track of tags to make
up for the lack of a search in a static site. I do this in two batches
(again see the original article for my tiddlywiki.info setup) and have to
manually copy the output from ./tag to the parent folder. I'd Actually
rather keep this file structure as it is but there is the next issue to
consider.
4. One Size Doesn't Fit All for tv-wikilink-template
I'd like to be able keep certian pages in separate folders. The current
basic static site exporter kind of expects a relatively flat folder
structure:
./index.html
./static/~ //all other tiddlers
I'd prefer
./index.html
./tags/~ //tagging related tiddlers
./blog/~ //all other posts
or even
./index.html
./tags/~ //tagging related tiddlers
./blog/<field:created>/~ //tiddlers exported under created date
I don't see how i can use tv-wikilink-template in an elegant way to link to
different folders.
If anyone has solutions to these problems or has used the static website
generator to any extent and has some advice, please let me know.
The first issue is really just cosmetic, but i would like to fix it. The
final 2 issues are big ones that i would like to address. A more robust
solution setting the output location of RenderTiddlers would be ideal. but
that needs to be developed with a better version of tv-wikilink-template
(unless i am missing something)
The issue i was having with tv-wikilink-template was that with a folder
structure like this :
./index.html
./~ //all other posts
./tags/~ //tagging related tiddlers
On "tags" article (linked in the banner) I'd want links to posts to point
to the root directory while the tags themselves would point to the root
directory.
Thanks for any help, James
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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 http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.
