One of Tbx’s many facilities is the manner its features tie into each other, and therefore how rapidly the new users grasp of concepts could web outward.
Example - you have:
- 50 Notes on topic A
- 25 Notes on topic B
- 25 Notes on topic C
Some questions to explore:
- what do I eventually want to do with or extract from these Notes? Do I already know this or will I play with them until a structure emerges {incremental formalization}?
- Would I like Notes of each topic to be visually distinct for ease of identification {Prototypes}? Will these topics be distinct, or could Notes belong to one or more topics {Set-type Attributes}?
- Will I be appending additional Notes under each topic, and if so would I feel like doing this graphically {Map View, Adornments} or in an Outline/list {Outline View} (a list being simply a flat Outline)?
- Will I link Notes within or across topics {Linking}?
- While working with these Notes, would I like them to develop behaviours based on their content or Attributes {action code, primarily housed in Functions, Stamps, and Agents}?
- Will these topics ultimately form into sections? Will those sections be fixed, or fluid? Will they gain hierarchies, and will those hierarchies be exclusive?
- Do the contents of my project have external utility - do I intend to Export some/all of my results and if so in what format {look into Exporting, Pandoc export, Posters} - do I want to generate html or markdown or rtf documents?
Just scratching the surface here. Think about attending our weekly Meetups (there’s one starting in 45 minutes I believe). Welcome to Tinderbox.