multiple object types

[kevgo]

• mixing people, products, companies, publications, etc in a single flat hierarchy is strange
• the different note types use different section types
  • example: people use "contact" and "career" while technologies use "functionality", "benefits", and "challenges"
• the easiest and most straightforward way to do this is to put each note type into its own subfolder that contains its own tikibase.json
• the nested tikibase.json files inherit from the root tikibase.json file and override certain keys

example for nested tikibase.json:

{
  "extends": "../tikibase.json",
  "sections": ["contact", "career"]
}