How do you manage different "views" for contexts and projects?

[phillipadsmith]

I came across the recommendation to duplicate the default Bases (and rename them) before customizing, so that future TaskNotes updates don’t overwrite your changes. That makes sense to me in principle.

What I’m less clear on is how people apply this in practice when working with contexts or projects.

Specifically:

• Do you generally duplicate entire Bases (e.g., tasks-default, kanban-default) for different contexts or projects?
• Or do you prefer to keep a small number of Bases and rely primarily on views within those Bases?

For example:

• With the tasks-default Base, it seems reasonable to duplicate it for contexts, since each context might benefit from its own set of views like Not done, Overdue, etc.
• But with the kanban-default Base, where views aren’t really the organizing mechanism, duplicating the entire Base feels less obviously useful. In that case, it seems like views (or filters) per context or project might be enough.

I’m curious how others are handling this tradeoff:

• Duplicate Bases vs. shared Bases with multiple views
• And whether your approach differs between task-style Bases and kanban-style Bases

Would love to hear what’s worked (or not worked) for you.

[phillipadsmith]

I found my own way of managing this tension, which is mostly using views, not duplicate bases.