I wiped the discussion here because it was mostly about implementation of an earlier version of the solution. It's all in "Changes", of course.
I had a look into how we're currently using star cards. Here's how it breaks down:
Patternable Settings
____________________
*google analytics key
*autoname
*edit
*favicon
*layout
*new
*related
*table of contents
*tform
*rform
*watchers
*title
*thanks
~~~(Pointer)
*input
*options
*option label
Whole Site Settings
---------------
*home
*css
*tinyMCE
Right Forms
-------------------
~~~(Search)
*cards edited
*editors
*includers
*inclusions
*links
*linkers
*members
*roles
*plus cards
*plus parts
*type cards
*watching
*tagged
~~~(Related SubTabs)
*account
*community
*plusses
*outgoing
*incoming
*type
Email
--------------
~~~(Deprecable?)
*notify
*invite
*request
*signup
~~~(Will have right forms)
*from
*to
*subject
*message
Not in Code
----------------
*logo
*sidebar
--Ethan McCutchen.....Tue Nov 03 17:28:03 -0800 2009
Some card names begin with a star (*). These "star cards" are
Wagn configuration works by connecting Sets (groups) of cards to Settings (configuration options).
These star cards help form sets:
And these represent settings:
Note that you can go to a set or setting card to see all rules associated with it.
These are used for flexible email and account-related emails.
The following configure signup communications, including email notifications and thank-you pages:
Each card has a "related" tab entirely configured through cards:
These cards are simple single card config options:
These cards configure valuable searches:
--John Abbe.....Tue Feb 15 21:57:36 -0800 2011
This is in place via sets and settings!
--Ethan McCutchen.....2013-02-25 16:45:52 +0000
(closing)
--Ethan McCutchen.....2013-02-25 16:45:56 +0000