Ticket
rename *content and others+issues
confusing because:
- *default also affects the content,
- *content controls not just content but also type,
- we want separate menu items for editing content and editing *content rules, but the names are too close
- you really have to understand Wagn structure to understand why it makes sense in the first place.
rename *content and others+solution
renaming *content to "*structure"
Other Renaming
- *links -> *links to
- *inclusions -> *includes
- *linkers -> *linked to by
- *includers -> *included by
- *plus cards -> *children
- *plus parts -> *mates
- *editing -> *edited
- *edit help -> *help
New Codenames
- by_name
- by_update
- by_create
- refers_to
- links_to
- includes
- referred_to_by
- linked_to_by
- included_by
- children
- mates
- editors
- discussion
- created
- edited
Renamed Codenames:
- structure -- note: Since this card is key to initialization, the codename renaming needs to be done in a straightforward traditional migration in order to avoid any loading errors.
- help
Delete:
- *related
- *incoming
- *outgoing
- *community
- *plusses
- watcher instructions for related tab
The easiest to understand use of *content is making templates, but control is more accurate and complete. Any other ideas?
I'm inclined to change *default to "*initial content" and keep *content as it is. My complaint with both is that neither implies an impact on type, though the more we frame type as a quality of the content (not the card), the less this is a problem...
--Ethan McCutchen.....2013-02-25 00:04:27 +0000
the following is moved from Wagn 1.11+discussion:
migration needs:
1. codenames for all cards referred to in menu (renaming suggestions in parens)
- by name
- by update
- by create
- *refers to
- *links (*links to)
- *inclusions (*includes)
- *referred to by
- *linkers (*linked to by)
- *includers (*included by)
- *plus cards (*children)
- *plus parts (*mates)
- *editors
- discussion
- *created
- *editing (*edited)
2. *edit help for many of the above?
3. I'm inclined to rename *default to *template and *content to *structure, but I should push that discussion elsewhere...
4. I vote to delete:
- *related
- *incoming
- *outgoing
- *community
- *plusses
- watcher instructions for related tab
--Ethan McCutchen.....2013-03-11 18:52:30 +0000
2. the only one that's editable is +discussion, but maybe by *edit help you mean something other than eg discussion+*right+*edit help ?
The key is to find a way to have help text in the related view (the one navigated to from the menu). I was thinking *edit help is the best place to store that. Perhaps we should rename *edit help to *help? That makes this less confusing, and it actually makes the override relationship with *add help more obvious. And "*edit help" is already used in at least one non-edit context (viewing rules).
--Ethan McCutchen.....2013-04-05
3. let me know when/where you're having that discussion. my 2 cents - i think default is most descriptive for that setting, and how about *form for *content if we're changing language? I find structure pretty opaque.
see rename *content and others (discussed at length in Circle 16)
--Ethan McCutchen.....2013-04-05
--John Abbe.....2013-03-11 22:56:55 +0000
Given that the Related tab has gone away, there are a bunch of cards used to build custom related tabs on that should probably be removed from English, yes?
yes, I think #4 above covers all those, no? (remember that deleting those will delete all their plus cards)
--Ethan McCutchen.....2013-04-05
--John Abbe.....2013-03-14 05:03:46 +0000