--- urn: "urn:penemure:7a1bb42d-eb09-4ce1-8356-0d4cd57cb7c5" backend: "pub" ancestors: - 📁 Penemure created: 2025-01-27 09:29:29+00:00 updated: 2025-01-27 09:29:29+00:00 tags: status: "done" --- # 📝 Templates we want to define templates for an "app". (and decouple the app from code and make it more generic). we should - stop having apps, they're just thin thin wrappers over note anyway. delete them. - allow "apps" via templates, these describe roughly a table/notion database. - (templates are an app tho, own namespace everything) - users can edit these templates, they define things like which Keys are present on a thing, what icon that key used, how to render that value ## example we want a Task template, it is going to use Template tags (maybe they're a block type, maybe they're a KV) for: - Status, enum (a status subtype specifically, so we can easily pull the status from someone else's table), maybe some specific colours associated with the values. HTML shaped enum? Max=1 - due date, future date shaped, display calendar picker, (or project relative dates) - priority, enum - is blocking, a reference type. (do we want to enforce any guarantees on that ref?) should that reference copy the resolution state, given that we may not be able to resolve something?