Hi,
I was asked by a forum member so I thought I might as well share my experiences with everyone. Bear in mind as I post this, we are not live and the exposure to simple edit users has been minimal, their feedback may change things.
- We have decided to not use the keyword to change screens (javascript/drop down) and create our own CSS tabbed interface which seemed more flexible.
- I was hoping to keep all simple edit related things inside the layouts as single point of control, unfortunately some keywords (asset url) are available only in the design.
- We are using 4 layouts currently applied only to Page Standard. Each layout is made of two content area: the navigation one, common to all 4 layouts apart from a class, and the screen-specific keywords.
Design area
In our design area we have the following code just above the 'body' design area:
Page title:
(/_nocache" target="_new">Preview in a new window)
which results in the following:
[quote]Page Title: My page Title
http: //mydomain.com/my_page (preview)[/quote]
Navigation Content (common to all layout)
That's probably the funkiest (designed long ago now, so maybe out of fashion).
The DIV containing this content has ID set to "cmsscreenmenu".
And of course, the 'class="selected"' is placed in a different <a> according to which tab needs to be highlighted.
I've attached the CSS which makes the above list inline and tab-like (I hope it works for you, there may be more style involved which i forgot to attach).
Detail screen
Current status: %details-F_status_current%
Change status: %details-F_status_change%
%commit_button%Content screen
%__custom-contents%
%commit_button%Metadata screen
%metadata-F_metadata_values%
%metadata-F_metadata_instructions%
%commit_button% Workflow screen
%workflow-F_workflow_metadata_warning%
%workflow-F_workflow_status_change%
%workflow-F_workflow_log_message%
%workflow-F_workflow_status_commit%
%workflow-F_workflow_report%[b]Important facts:[/b]
- We would really like to hide (using CSS) the cascade checkbox for status and for workflow because in simple edit it causes chaos (content going into approved to go live when page hasn't started the workflow, etc...). Unfortunately it is not easy because the source produced by Matrix isn't using any id we can simply hide. Hiding the checkbox is doable, however the text following the checkbox cannot be removed easily.
Attached is the resulting look of our simple edit.
I would love to see what else people have done.
(sorry for the long post)
Cheers. simpleedit.css (1.06 KB) simple_edit.jpg (25.8 KB)
