This is a request for ideas for cleaning up the existing administration interface for template creation.

Initially, just a small handful of fields were covered, and this has slowly grown, making this page very cluttered.

I'm going to look at implementing some CCK integration, and I'll move the sections into fieldsets but open for any UI suggestions.

Comments

mdupont’s picture

mdupont
Primary language French
Location Switzerland
commented

Some suggestions:
- Add "Token Help" under each field accepting tokens
- Item "Default menu link title": display only one field instead of 3 checkboxes. If the field is left empty, then the default behavior is used ("Copy user specified title") ; if "<none>" is entered, no menu entry will be created ; if it is something else, then it is a custom menu link title.
- Categorize the available options : display the more important first ("Default menu link title", "Default parent item behaviour", "Taxonomy settings", reference content item and user), and hide the other option behind a collapsed "Advanced options" field.

alan d.’s picture

alan d. commented

Thanks mdupont

@ Categorize the available options

Totally agree. Using fieldsets + vertical tabs appears to be the best solution, but still usable without vertical tabs.

@ Add "Token Help" under each field accepting tokens

Due to the large # of fields, the last tab will contain the help. It least site site we use this on has over 50 fields, so 1 set token help per field will be to much of a performance hit. I'll normalise the help text on each field, adding the suffix t('Tokens supported.') if the token module is available.

@ Menu settings

I thinking having more options is best. It would be to complicated to explain the usage, negating the benefits of the reduced number fields.

# General changes

Normalising the general options on all fields, unsetting the ones that are not applicable.

t('Empty')
t('%module default')
t('Custom value')
t('Clone related nodes value')
t('Clone related nodes user value')
t('Clone reference nodes value')
t('Clone reference users value')

# Front end

I haven't started refactoring this yet, but reduced options that have more flexibility is planned, somehow.

Removing the three user permissions to just one. Block access will be controlled by core.

Changing t('Create related content') to just t('Create content')

alan d.’s picture

alan d. commented
Status: Active » Closed (fixed)