Thanks, Tony. Very helpful. Regards Jon
On Wednesday, 9 October 2019 00:26:50 UTC+1, TonyM wrote: > > Jon, > > That is a little question with a big answer. > > Here is a quick response. > > - If I create tiddlers that are code, rather than content I try and > keep them as system tiddlers, using $:/ as the prefix, even $:/PSaT/ which > is my Business initials. So when I want to extract data I just need to > export regular tiddler and [!is[system]] > - With my code tiddlers I make bundles with the bundle plugin and > export them as json files, often using [prefix[$:/PSaT/solutionsname]] > - But I also have data tiddlers such as $:/data/datadictionarytiddler > and I make a bundle for them as well. > - As I develop my wiki I use these prefixes to organise tiddlers, and > when that is not practical I use a bundle to include any tiddler I want. > - The key is to never loose information as you design or enter data, > capture the relationships between tiddlers even if this is simply by > setting some naming standards. > > However the most practical approach is ensure you manage various tiddler > types so you can easily create a bundle of them. For example since the type > field is already in use, I use the an object-type field. When I create > tiddlers of different types, often from a custom new tiddler button, I > always set this object-type field. for example (Written in field operator > /value format you can use in filters) > > - object-type[person] > - object-type[note] > - object-type[project] > - object-type[task] > > However you can already use the built in type field to identify images, > text etc... > > Correct use of tags also helps so I can also list all tiddlers with the > prefix[$:/PSaT/]] and that have the tag $:/tags/Stylesheet or $:/tags/Macro > > Regards > Tony > > > On Wednesday, October 9, 2019 at 4:17:02 AM UTC+11, Jon wrote: >> >> Hi Tony, >> >> I'm wanting to do the same as the original questioner. >> >> Could you give me a few pointers on your naming standards? >> >> Regards >> Jon >> >> On Wednesday, 29 May 2019 00:22:42 UTC+1, TonyM wrote: >>> >>> Ittay, >>> >>> This could be difficult because you are doing it in retrospect, had you >>> planned to identify the difference between the system and the content from >>> the beginning it would be simpler. I would have no problem with my wikis >>> because I take steps to keep content separate from solutions using naming >>> standards, bundles of tiddlers etc... >>> >>> >>> >>> >>> - Someone with a lot of experience in tiddlywiki could do a quick >>> job of *some of this* by identifying macro and template tags, >>> overwritten shadow tiddlers so if you are prepared to share your wiki, >>> they >>> could help get you started (Contact me privately if you want me to have >>> a >>> look, I will respect your privacy, I am a registered business, and well >>> known here) No charge to community members unless it needs too many >>> hours. >>> - However If you start with a new empty file (then install the >>> bundler plugin with the import bundle activated) , drag the plugins over >>> save and reload and make a copy of this and start to locate some of your >>> customisations and replicate them on the new site it may not take as >>> long >>> as you think. >>> - The Bunddler plugin will keep a record of the tiddlers you import. >>> - If you make copies of your wiki as you try something new if it >>> breaks just go back to the previous version. >>> - You could use the filter [!is[system]] to list all non system >>> tiddlers and start to make inroads as to what you need to remove. >>> - In the end you have have your own tiddlywiki edition "template" >>> without content you could use for making new Wikis. >>> >>> >>> This will be a learning process for you as you revisit old >>> customisations but it will give you the opportunity to review them, >>> understand them better and tweek them. The fact is new features and plugins >>> often make customising easier than before so you may find it quicker than >>> you think. I would try and understand what you do rather than just move >>> everything, as tempting as it may be. >>> >>> Just writing a list of the features you want to keep or see in your new >>> wiki would be a great start because you can ask for help here. >>> >>> Regards >>> Tony >>> >>> On Wednesday, May 29, 2019 at 12:13:06 AM UTC+10, Ittay Dror wrote: >>>> >>>> So I have a TiddlyWiki file with tons of tiddlers, plugins and >>>> customizations. I want to start a new one and retain the plugins and >>>> customizations, but not the tiddlers. How can I do that? >>>> >>> -- 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/ae0d7414-d481-4623-8a20-7cddd3502a5a%40googlegroups.com.
