Too many configuration options cannot be accessed within wagn.
Here are the cards we currently have:
Some card names begin with a star (*). These "star cards" are
- referred to in Wagn's code, and/or
- key to Wagn's default structure
Note that *title and title are two different cards -- the star leaves the name for other uses. Also see an alphabetical list of all star cards.
Rules
Wagn configuration works by connecting Sets (groups) of cards to Settings (configuration options).
These star cards help form sets:
- absolute sets: *all, *all plus, *star, *rstar
- relative set classes: *self, *right, *type, *type plus right
And these represent settings:
- help text: *add help, *edit help
- permissions: *create, *read, *update, *delete, *comment
- formatting: *structure, *default
- pointers: *input type, *content options, *content option view
- other: *accountable, *autoname, *captcha, *table of contents, *layout, *send, *thanks
Note that you can go to a set or setting card to see all rules associated with it.
Mail / Signup
These are used for flexible email and account-related emails.
The following configure signup communications, including email notifications and thank-you pages:
Related Cards
Each card has a "related" tab entirely configured through cards:
- subtab list: *related See how to customize Related subtabs.
- subtabs: *incoming, *outgoing, *plusses, *community, *account
- reference searches: *links, *linkers, *inclusions, *includers, *refers to, *referred to by, *tagged
- plus searches: *plus cards, *plus parts
- user searches: *editing, *editors, *creator, *created, *watching, *watchers
- role searches: *roles, *members
Other
These cards are simple single card config options:
- basic: *title, *home, *logo
- look and feel: *css, *favicon, *sidebar
- advanced: *tinyMCE, *google analytics key
These cards are included in the Classic Layout and have autogenerated content.
- *head — required, goes in HTML head
- *navbox — the navbox
- *account_links — links to current user's card, sign in/out, and signup
- *version — current Wagn release
- *alert — where notifications show up, defaults to bottom-right corner
- *foot — required, goes just before /body on page's HTML
These cards offer metadata about any card when plussed to them (eg Home+*when created)
- *when created - creation date
- *when last edited - edit date
- *count — the number of cards in a collection (Pointer or Search).
These cards configure valuable searches:
- *account — existing accounts and Sign up
- *recent — used for Recent Changes — all cards by update, inserts Date headers
- *search — similar to a form, used for navbox results
Here are the inaccessible config options:
local.css, site name, various emails (for warnings, invitations, etc)
Let's use this space to include changes that we need to make after we have this functionality.
*table of contents - I know i'm the one usually arguing to put everything in cards :-), but is there any conceivable value in having a card for this? May not be worth the time now, but could eventually just do this in code, and in any case offer a much nicer interface for it (which ideally would only appear if the card in fact had four or more headers).
--John Abbe.....Sun Jan 04 03:43:16 -0800 2009
Solution reads: Any built-in cards that must be a certain type, but need not have any initial content, should be built-in anyway, and set to the correct type.
If we're going to do that, we should have meaningful default values, not blank content, because otherwise it will mess up funcionality. Eg, Wagn does behaves differently when there is vs. isn't a *home or *logo card. This is actually a pretty cool opportunity to make these features more discoverable...
--Ethan McCutchen.....Sun Jan 04 09:24:42 -0800 2009
re "*table of contents". Does "in code" mean in the database? I guess one value of having a card is that it gets exposed to WQL, which could have value for site upkeep (moreso once we have advanced search and bulk updates...).
I suspect that you're right, it won't be worth the time pre 1.0, but worth thinking about!
--Ethan McCutchen.....Sun Jan 04 09:27:52 -0800 2009
That's what i'm thinking - is there any admin situation in which you want to find cards that do or don't have their ToC suppressed? (By "in code" i meant, not having a card.) I guess more important to me than card-or-not is just having a better interface for this, so i added that to our mini-design list.
--John Abbe.....Sun Jan 04 22:34:57 -0800 2009
not sure exactly where to put the *error cards, since our setup had us directly configuring the plugin in wagn.rb...
--Ethan McCutchen.....Wed Feb 11 18:11:28 -0800 2009
Think this belongs in discussion more than solution:
At present, the "actual" search cards are referred to in the related card code, but I think ideally that will all eventually be built out of editable cards, so there may just be *related if any star card at all. But I think it makes sense to keep them for now. Do we want to change the link and update names for more simplicity / consistency? They sure are gangly. Could be hairier than warranted... Recommend status quo for now.
--Ethan McCutchen.....Thu Feb 12 14:13:31 -0800 2009
Let's move all of the "initial setup for new Wagn" components into a new ticket and test all the others, consistent with the card title. The initial setup ones won't make it into this release.
--Ethan McCutchen.....Mon Feb 16 10:29:24 -0800 2009
Ready to test those settings, but we also need to make several migrations before we're through.
-e
--Ethan McCutchen.....Mon Feb 16 10:30:10 -0800 2009
Moved some stuff as requested to implement initial setup for new Wagn
--John Abbe.....Tue Feb 17 14:09:26 -0800 2009
At ((removed reference to sandwagn)) i set *title to Sandwagn and deleted *home, and now ((removed reference to sandwagn))goes to Wagn.
Anyway, i can't see why we have both *home and *title - the solution says the latter replaces wagn.rb site_name, and Installation says that's the "name of the Wagn's front page".
I thought *title might set the browser window title, but it doesn't do that.
--John Abbe.....Tue Feb 17 17:26:08 -0800 2009
I set ((removed reference to sandwagn)) to be a Phrase and a Pointer, but in neither case do i get redirected to the page indicated (instead i go to the home page).
--John Abbe.....Tue Feb 17 21:43:26 -0800 2009
((removed reference to sandwagn)) exists, but the Message box in the invite is blank (and the email received only has what i typed in there plus the account details).
((removed reference to sandwagn)) exists, but the email i get still comes from the User who invited.
--John Abbe.....Tue Feb 17 21:46:11 -0800 2009
Got clarity from Ethan offline about *home vs. *title, documenting at implement initial setup for new Wagn
*message and *from fixed; *thanks in progress...
--John Abbe.....Wed Feb 18 21:16:40 -0800 2009
Everything looks good now. Closing.
--John Abbe.....Thu Feb 19 22:03:21 -0800 2009
Documentation in process on http://new.wagn.org/wagn/Config
Other documentation to update:
--John Abbe.....Sun Mar 01 07:41:37 -0800 2009