> I've long thought that TW should distinguish, both in the UI and > functionally, between "system" tags and "content" tags, i.e. those used to > drive app functionality vs those used to indicate topics within the end-user > content.
The way I have my site set up really only distinguishes between casual visitor mode and editor mode. If that is something that might be useful to you, I'd recommend looking at BidiX's site: http://tiddlywiki.bidix.info/ It seems very polished with excellent use-case segregation (not only between read-only and editor mode, but also between editor mode and sys-admin mode). I didn't use it because I had already built (read: installed plugins) a lot of segregation structure around my current template. I might use it in the future though. On Jun 24, 1:24 am, HansBKK <[email protected]> wrote: > Excellent idea! > > I've long thought that TW should distinguish, both in the UI and > functionally, between "system" tags and "content" tags, i.e. those used to > drive app functionality vs those used to indicate topics within the end-user > content. > > Looks like your plugin could be a first step in that direction - do you > think it's robust enough to package and post to a public location? -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
