(Note that when they were implemented, "patterns" got renamed to "sets".)
The "pattern cards" idea aims to address a number of evolving wagn challenges that stem from different ways in which we want to manipulate (format, regulate via permissions, cue editing with instructions, layouts, etc) cards that adhere to certain patterns of name and type.
Needs
- We are increasingly finding our permissioning system meeting significant limits. For example:
- you can set global permissions determining who can change
Solution
We propose to abstract the idea of a "pattern" out from these separate problems -- conceptually, in card structure, and ...Use cases
The two most common use case for patterns are:- we have a card and need to know a pattern-based setting.
- how do we want to pull off step #1 in Pattern Cards+implementation? So far we've stopped short of picking an implementation route.
Type forms
BP: ...
I ...
Also see:
