improve interface for editing settings

Ticket

+commit
 

Settings tab screenshot

 

Help text

Help text people will see when editing.

All help rules that apply to

cards of a given type

given field cards

given field cards on a given type
User Story+story+*type plus right+*help
See the (StUb{"cast":{"id":9213},"view_opts":{"title":"gu...

a single card

 

Permissions

Who can create new cards

All create rules that apply to

all cards

all "+" cards

cards of a given type
Blog entry+*type+*create

all "*" cards

all "+*" cards

given field cards

Who can view cards in the Set.

All read rules that apply to

all cards

all "+" cards

cards of a given type

given field cards

a single card

Who can update cards

All update rules that apply to

all cards

all "+" cards

cards of a given type

all "*" cards

all "+*" cards

given field cards

given field cards on a given type

a single card

Who can delete cards

All delete rules that apply to

all cards

all "+" cards

cards of a given type

all "*" cards

all "+*" cards

given field cards

a single card

 

structure

Controls cards' content / structure. more

All structure rules that apply to

cards of a given type
User Story+*type+*structure
RichText :

Story

{{+story}}

Tag with the [[tickets]], [[ideas]], [[blueprints]] and/or [[decks]] it's relevant to:
{{+tag|item:link}}

 

{{+discussion|open}}

 

 

given field cards
relevant user stories+*right+*structure
Search : { "type":"User Story", "plus": ["tag", {"refer_to": "_left"} ] }

given field cards on a given type

a single card

All default rules that apply to

all cards

cards of a given type
Blog entry+*type+*default
RichText :

DRAFT — To publish, remove this section and change this card's [[permissions]] to be viewable by Anyone.

 

Summary for mailing list:

 

 


 

 

Head1

 

 

 

Head2

 

 

 

Head3

 

 

Article+*type+*default
PlainText : title:{{+article|display:inline}} author:{{+article|display:inline}} date:{{+article|display:inline}} comments:{{+article|display:inline}}

given field cards

given field cards on a given type

 

Pointers

edit interface for list cards

All input type rules that apply to

given field cards

given field cards on a given type

a single card

Value options for List and Pointer and cards. Can itself be a List or a Search. more

All content options rules that apply to

given field cards

given field cards on a given type

a single card

Label view for radio button and checkbox items. more

All content option view rules that apply to

all cards

given field cards

 

Events

Configure events to be executed when card is created

All on create rules that apply to

cards of a given type

Configure events to be executed when card is updated

All on update rules that apply to

Configure events to be executed when card is deleted

All on delete rules that apply to

 

Assets

Skin (collection of stylesheets) for card's page. more

All style rules that apply to

all cards

a single card

JavaScript (or CoffeeScript) for card's page.

All script rules that apply to

all cards

 

Other settings

Autogenerate name for new cards by incrementing this value. more

All autoname rules that apply to

cards of a given type

Anti-spam setting. Requires non-signed-in users to complete a captcha before adding or editing cards (where permitted).

All captcha rules that apply to

all cards

cards of a given type

HTML structure of card's page more

All layout rules that apply to

all cards

cards of a given type

a single card

All table of contents rules that apply to

all cards

cards of a given type

given field cards

given field cards on a given type

a single card

Destination after card is created. more

All thanks rules that apply to

cards of a given type

 

I see three somewhat distinct pieces here:

  • order - chunk the settings that go together (see Settings by category), and put the most accessible ones first — e.g. table of contents, permissions when they're setting-ized. Ideally, hide ones the user can't add/edit.
  • added cue text - without having to open a setting, and ideally for each chunk rather than each setting
  • improved interface within each setting (e.g. *layout above) - one easy simplification is to stop linking the sets

Type cards currently offer to add settings applied to themselves+*type. These should have pretty much the same interface, with chunking etc. Maybe in a separate, default subtab? The same could be done for right cards (anything for which |foo|+*right+*count > 1). Depending on how we improve form creation experience it may make sense to remove formatting-related settings from this interface.

 

 

hmm.  drastically improved interface but not using above specs.  should discuss.


can we move above to a separate "idea"? Would like to focus testing on this ticket on whether current functionality works, not on any design tweaks. (Shifting to get-it-out mode)

  --Ethan McCutchen.....Wed Jan 25 15:33:47 -0800 2012


Closing.  Further improvements here: further improve rules interface

  --Ethan McCutchen.....Fri Feb 03 10:34:42 -0800 2012