[TYPO3-hci] BE-pages reloaded

[Jens Hoffmann]

Hy,

1. No "radio" where only 2 states are posible!!! (TRUE or FALSE = Checkbox!)
2. PLZ no coloring on only one point in the BE!
    If we start useing (bad/good) color indicators, than we need to do this all over the BE!
3. It's about HIDDING the page in the FE .. so why do we need change the wording?
    DISABLED = Wrong, the page is not disabled and still avalible
    OFFLINE = Worng, too.
    UNPUBLISHED = Worng, no revewing process involed in this way.
4. Who will have to beaware of this Error suff, the editor or an admin?
5. From to Fields show tell what they do and when.
    This means something like this ... Page is visible between: [ from ] and [ till ].
    There is really enougth space to be more detailed and domain driven.
6. Is it a good Idea, to have this "Include Subpages" ONLY on the "hideing", form part?
    I guess we need a general way for this ...
7. "Access Tab" Concept not clear to me. Please provide a Wireframe/Screen Moggup.

I guess a Tree (Mindmap) to view the sorting would help.
Could you please provide this, Malte? A better structure
would help TYPO3 a lot but it needs to be discussed, please.

Feel free to contact me via Skype.

--
Jens Hoffmann
[TYPO3 HCI Team Leader]

eMail: jens at typo3.org
Skype: WrYBiT


Malte Jansen schrieb:
> Hi!
> 
> Ok, here the summary of all suggestions.
> Please, make suggestions directly to this post, because otherwise some 
> points get lost during the discussion.
> 
> 
> Generally it should be grouped like we suggested.
> 
> 
>> Our Main Point: hidden/access
>>
>> General Tab
>> - Publish Setting (palette, always visible)
>> -- hidden (Type: radio!)
>>    Labels: publish | unpublish
>>    (unpublish fits?)
>>    (perhaps some color for highlighting
>>    the current status)
> Checkbox prefered.
> Other options for labeling:
> - Disabled
> - Offline
> 
> (Remember the labeling should only be used for pages and tt_content. All 
> extension can choose the labeling and can change it to their own 
> purpose. For the TCA it is still the same...)
> 
> My Idea for future:
> The FE-access check should be splitted into two parts.
> - hidden/publication-palette check
>   denied: error 404 (not found)
> - user-access check
>   denied: error 403 (forbidden)
> 
>> -- starttime: now
>>    Label: ??? (not to long)
>>    (perhaps some bluring, when it's empty like 'now'),
>> -- endtime: endless
>>    Label:  ??? (not to long)
>>    (perhaps some bluring, when it's empty like 'open-end'
>>    or endless)
> 
> Labels were not discussed. No suggestions.
> 
>> -- extendToSubpages:
>>    Label: Include subpages
>>    (affects only hidden,starttime,endtime)
>>
> Splitting seems to be a good idea.
> 
>> Access Tab
>> - fe_group (type: check)
>>   Label: Frontend Access
>> -- accessToSubpages:
>>    Type: check
>>    Label: Include subpages
>>    (affects only FE-Access)
>>    Update Manager: Getting values from 'extendToSubpages'.
>>
>> - Backend Access (palette, always visible)
>> -- editlock
>>    Type: check
>>    Label: Restrict editing by non-Admins | Admin only
>>
> No suggestions.
> 
>> Now Publishing would have a double meaning.
>> The status in the workspace should be change (anyway)
>>
>> "Editing -> Review -> Release"
>>
>> (Old-Version: Editing -> Review -> Publish)
>>
>> Here ends our main issue...
>>
> There where no doubts
> 
>> -----
>>
>> Here are some ideas, which would be an improvement ;)
>>
>>
>> Moving "Last updated:" to "Tab Metadata".
>>
> No doubt.
> 
>> Group "Navigation"
>> - navigationtitle
>> - hidemenu
>> - alias
>> - target
>> (palette arrangement or fields?)
> No suggestions.
> 
> 
>> Group "Cache"
>> - fields: no_cache,Cache expires,Login Mode
> Login Mode was unclear for all.
> Login Mode should be a checkbox, because it has only to options
> 
> There must be a better label.
> 
> Should there be a checkbox "include Subpages".
>>
>> Group "Localization"
>> - fields: "Hide default translation of page",
>>       "Hide page if no translation for current language exists"
>>
> No doubt.
> 
>> All three groups should be place in General. The sorting is open.
>>
>> The "Options" tab should be more like a configuration tab.
>> The "General" tab should be more like a editing/editor tab.
> 
> No suggestion were made.
> 
> 
> 
> Cheers,
> 
> Malte