## Principles - Can create templates for queries you can re-use anywhere but then modify when needed, just like buttons and fields in [[Obsidian Meta Bind Plugin]] - How should it be stored in someone's vault? - Scripts/Datacore/ - Utils - sortByX - Views - Based on the content you're trying to query? You can't do a template since there might be multiple imo? - Projects - Days - Obstacles - All - Instead of creating dynamic variables, frontmatter should just contain them? like how i'm doing with the goal queries atm? - Just adds a lot of complexity though - how can you make template queries convenient to change? do you literally just create a forced view with no edit permissions? - But the question remains on if you should have each component the reusable part, or if you should just make a whole new one - Or what if you could do even more abstraction? - Columns have your custom ones - useQuery you also have custom ones - sorting you have custom - Render you have custom - You can also organize by the note as well? Like you have a mirror note for each dashboard you have or template? hmm - Make the creation of these tables easy to do, even for non-technical users - What preset sorting queries should I have? - Sort by date - Sort by text in an array - Sort by alphabetical order - Sort by numerical order - What filter queries should I have? - Can create a form or quickadd schema? - Very basic - Don't think it's worth creating a whole page with metadata fields just to modify one though since it might be different across - Think of migration away from inline metadata, and think of another solution. If I do actual inline I can change my fields so it becomes that - Can use regular dataview for inline fields since it's less common? - This should only affect inline indexing so I think it's safe for now ## Explanations - How Datacore works