close fullscreen

Idea

+status

+priority
low
help edit space_dashboard

+tag

 

+issues

help edit space_dashboard

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

help edit space_dashboard
  1. CRUD.  id, name, content
  2. modules
  3. links in content.  (content parser)
  4. inclusions
    • UI implications, javascript/ajaxy stuff.
  5. versioning   
  6. plus cards 
       - relative inclusion
       - smart renaming
  7. types and type creation  (note: consider how multiple types & inheritance affect pattern cards)
  8. pattern cards
  9. users and permissions
  10. WQL & Search cards

 

describe essential components of wagn+discussed in support tickets

help edit space_dashboard

+relevant user stories

help edit space_dashboard