describe essential components of wagn
Idea
+status
+priority
+tag
+issues
I think it's useful to thing about what fundamentally a wagn is as a frame for making decisions about major features or refactorings.
+example
- CRUD. id, name, content
- modules
- links in content. (content parser)
- inclusions
- UI implications, javascript/ajaxy stuff.
- versioning
- plus cards
- relative inclusion
- smart renaming - types and type creation (note: consider how multiple types & inheritance affect pattern cards)
- pattern cards
- users and permissions
- WQL & Search cards
+discussed in support tickets
+relevant user stories