<<forEachTiddler
where
'tiddler.tags.contains("$1")'
write
'"|<<preview [["+tiddler.title+"]]\>\>|\n"'
begin
'"{{smaller{\n|sortable|k\n| !Preview Tiddlers |h\n"'
end
'"}}}"'
>>
1. Place this code in a tiddler titled fETtiddlers2.
2. Call it like this: <<tiddler fETtiddlers2 with: "systemConfig">>
3. A table of hits wll be generated.
A more complicated version (fETtiddlers):
<<forEachTiddler
where
'tiddler.tags.contains("$1")'
sortBy
'parseInt(store.getTiddlerText(tiddler.title+"##SortNum"))'
write
'"| " + parseInt(store.getTiddlerText(tiddler.title+"##SortNum"))
+ " | <<preview [["+tiddler.title+"]]\>\>| <<tiddler
tiddlerLink with: [["+tiddler.title+"]]\>\>|\n"'
begin
'"{{smaller{\n|sortable|k\n| !Sort | !Preview Tiddler | !Edit Tiddler
|h\n"'
end
'"}}}"'
>>
which references a tiddler titled tiddlerLink which contains:
{{small{<<editTiddler [[$1]] ✎>><<editSection [[$1]] "✎" "edit tiddler
$1 inline">>}}}[[$1]]
This version also produces a table but the table includes a link to
open the specified tiddler and begin editing it and a link to edit the
specified tiddler inline (which requires
http://www.tiddlytools.com/#EditSectionPlugin).
You might have accurately guessed that I have collected, tweaked, and
created many ways to render tiddlers and lists of tiddlers. As a
Technical Communicator by profession I am always looking for ways to
improve the discoverability of content.
Craig