@Edgaras it is a valid point, especially when I look back at things I setup a year or two ago!
I too tend to: a) place things under a name, for example $:/sq/stories or $:/sq/static and then a filter can be be handy [prefix[$:/sq/static/]] b) when it makes more sense for the tiddler to be in $:/config or if its a shadow tiddler I need to tweak etc, I usually have a listing page per "project" that lists all the tiddlers required for it, usually generated by the above filter with a few tiddlers added on by name. With a filter for all the tiddlers you need for a certain "project" it is easy to see a list or create a button to drag and drop them into another wiki. For example: <$button dragFilter=<<myfilter>> > Static export tiddlers </$button> Regards, Saq On Saturday, May 9, 2020 at 3:28:36 PM UTC+2, Edgaras wrote: > > Saq Imtiaz good explanation. It works well with your new update too! > > What my OCD brain asks: how do you keep track of all those extra small > config files that we scatter all over the place? I try at least to list > all additional ones I add under my project name. So in the future I can > tell someone how to achieve the same result from brand new empty.html > TiddlyWiki. Anyways, this is offtopic😊 > > Yeah, you are right about the latest modified and problems with > transclusions. I think I would have two buttons: > > 1. One simple one when I just want to publish few recently added or > edited notes. > 2. Second one full export, that I would use only once in a while, or > when problem occurs to make sure all notes function as they should. > > -- 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/a013eb59-44ca-4288-b3e0-6f36f897bd6e%40googlegroups.com.
