The following tiddler types are a result of a personal brainstorm`. I present these to ask for suggestions or descriptions. I can later provide a tiddler glossary.
Please note the use of the word “Type” here is a word we use in English to categorise things and is only indirectly related to the “tiddler type field”.
CSS Tiddler
Stylesheet Tiddler Contains CSS and tagged $:/tags/Stylesheet
Data Tiddler types
Data Tiddler Refers to all tiddlers containing data but specifically Dictionary Tiddler and JSON Tiddlers
Index Tiddler
JSON Tiddler
Dictionary Tiddler
Template Tiddler
Content Template
Display Template
Edit Template
Form Tiddler
Functional Template (eg; listitem, macro in a template etc..)
Tiddler template
View Template
tiddler-types
Button Tiddler
Child Tiddler
Complex Tiddler
Composite Tiddler
Compound Tiddler
Config Tiddler
Content Template
CSS Tiddler
Current Tiddler
Data Tiddler Refers to all tiddlers containing data but specificaly Dictionary Tiddler and JSON Tiddlers
Display Template
Dynamic template
Form Tiddler
Functional Template
Import Tiddler
Index Tiddler
Instance Tiddler
JSON Tiddler
Library Tiddler
Macro Tiddler
Master Tiddler
Other Tiddlers
Parent Tiddler
Plain Tiddler
Raw Markup tiddler (more than one)
SideBar (tab) tiddler
Stand-alone Tiddler
State Tiddler
Static template
Story Tiddler
Stylesheet Tiddler Contains CSS and tagged $:/tags/Stylesheet
subtiddlers
A tiddler tagged to appear as a tab may be called a “tab tiddler” could be considered a subtiddler
tab tiddler (qualified by the tabset eg; Sidebar tabs, advanced search tabs…)
Given that the TW architecture can amalgamate fragments in infinite ways I’m doubtful that there could ever be a canonical listing that covered all “combo types” (complex transclusions / macro creations etc). Basically I, personally, find your presentation too baroque.
The world is complex. This was a brainstorm of tiddler types i have heard of or used and many are in the core. I believe we should embrace complexity and understand it before we over simplify. I reject the kis (keep it simple) principal because it never was Simple. Make it simple is the better approach, but to do so requires real insight and you start by collecting information and at least you have a reference.
When the core or tiddlywiki uses a very generic term there will be overlap. Tiddlywiki’s type field does relate to a mime type. With the exception of media most user tiddlers are the default and need not even have the type field set.
@TiddlyTitch This is one of the nicest complements I have ever received
In the real world and English we use the word “type” to systematically categorise tiddlers formally or informally eg “is it a shadow tiddler?” “is it a system tiddler?” is it a “Celebrity Quote tiddler”. The type field is rarely involved in distinguishing between tiddlers.
The point here people already use “type” and a strict definition is not possible. However when needed you can place the word in context and it will be considered Content Type as formally defined in tiddlywiki.
The collation of these titles is to make visible the “types of tiddlers” made reference to in the community, wikis and minds of designers. We discover things like the word “template tiddler” is overloaded in tiddlywiki and can be further divided.
Posting, makes public things in our minds we can “share and compare”.
@TW_Tones I simply think using “type” as thedifferential would end in confusion. Let me explain why … Sure we have ContentTypes (universal mime types) and Tiddlertypemodes (normal, shadow, overwritten shadow).
I think there is an underlying semanticissue if those two get mixed up. They are different levels.
I DO want to endorse your exploration. But slightly qualify it’s basis.
(I write this as a European living in the middle of baroque history.)
We agree, qualification is needed and placing something in context critical if one wants to reference content types or differentiate between core tiddlers, system, shadow, overwritten shadows (tiddlers) and regular tiddlers. The some core tiddlers are templates, some templates are view templates… We could try and map all these relationships however I would not be sure how many people would read it unless seeking a description.
I do feel a glossary with links to the documentation would be useful.
Do we have a set name for the two main types of template tiddlers?
I.E. when a tiddler is tagged with something, the viewtemplate is changed, vs. when a tiddler is cloned to have the same text field, to render a specific way, like a snippet?
Unfortunately no, but as @joshuafontany suggests there are some de facto names.
But a tiddler can be many things, so many things can have many types of template.
I tend to use the following terms to differentiate between common templates
Tiddler Template - for making tiddlers
Content template - for content smaller than a tiddler
Object template - which is for tiddlers I use to represent different objects like a contact template for making contact tiddlers. I set object-type-content on resulting tiddlers.
View Template - for displaying via view template
Edit Template - for displaying via the Edit template
Field template - not in use much yet by me but will
And templates for common tiddlywiki objects are often referred to like "button, theme, layout… template
The issue is that tiddlers, and TiddlyWikis templating features like transclusion are so versatile we attempted to do this once before and it was just too broad.