Tiddlers having many roles, types and uses

[TW_Tones]

@Springer

Does that spell out the daydream more clearly?

It certainly does, thank you. Very interesting.

It is different to, but not unlike my current thoughts, as yet unpublished, where we are trying to discover the structure, which can be built as content/data arrives in a wiki. Tolerant of missing information, it discovers and builds what it can from the data available, and could identify what is missing and kindly ask for it.

• If I understand correctly your idea is also “discovering something as a result of ‘analysing’ list fields and tiddler existence”, but you seem to go way beyond that.
• I can see the creation of some analytic functions here such as
  • iterate the items in a list field and return a value that determines the ratio of “list items” to “items with actual titles (in the wiki missing or otherwise)” OR the ratio of “list items” to actual existing titles.
  • Simply returning the number of item in a list
  • For a given item how often it is named in the same list field throughout the wiki, named in any list field in the wiki
  • Ratios or values that assist logical determinations resulting in questions like

Would you like to enable virtual nodes for publishers?

@TW_Tones

OK, Quoting myself, but this does sound like one of two features we seem to be looking at managing here a “Content Display System” C.D.S. but beyond this we are also wanting to manage it, so it also becomes a CMS “Content management system”. But I remain open to other descriptors.

And again: Is it fair to say we need these components;

• Content definition (what is what and related to what, a schema)
• Content display ( display according to the content found and the definition)
  • Content Editing (Permitting change to content)
• Content query reporting/listing
• Content analytics that as @Springer suggests can feed back into “Content definition”

[Edit] Post Script

The current development in the preview Tiddlywiki 5.4.0, of the multivalue variables “MVV” will help in this kind of design. eg one can take a list field and store it in a multivalue variable and then make use of it multiple times even in the same filter.

• Ultimately it should allow passing lists into filters and functions easier.
• However I still have concerns about this MVV implementation falling short of what it could be.

[Edit] Again

It seems there is also a need to support “upfront definitions” we know right away as we build something. for example if we know we want person, organisation and invoice tiddlers then lets allow this to be defined upfront making their use easy, but then assist the evolution of the definition as data becomes available.

[intrinsical]

I was not clear enough that I was designing the wiki as a platform any D&D player can pick up and use. I want the D&D wiki to be as simple and as easy to use as possible. So consider this as an ease-of-use feature if non-TW experts can simply insert a Skeleton statblock using {{Skeleton}} rather than having to type something more complicated like {{Skeleton||monster}} or <<monster Skeleton>>. The latter case of using a macro is worse from a usability standpoint as a lay-user who does not understand TW5 would begin to wonder in which situation they should they be using curly braces and when they should angle brackets be used.

This is also why I have worked hard to remove the use of macros in my wiki, replacing them with parameterized transclusions. This way, the end-user has one less thing to think about when using the wiki.

[TW_Tones]

Sure, I get what you are saying, but if you look closely at the excise tool in the editor toolbar, or the link button, there are ways to provision even easier tools, than typing special characters and as a result they can be more sophisticated.