building interface for content editors people

Author Message

Jacek S

Thursday 20 July 2006 9:01:32 am

I curentlly develop a site which will have several level of users. Some (me :) ) will be full administrator, some will be only content editors - with only inserting and editing pages/object rights.
Standard admin interface is far to complex for future content editors. I have to build simply interface for:
- getting info about curentlly explored node/object
- editing/deleting/publshing selected nodes/objects
- making translation of nodes/objects
- creating subnodes in selected nodes

So, where to start? Is there any guidelines for such task? Maybe an example or tutorial?
Any sugestions will be welcome.

Egil Fujikawa Nes

Thursday 20 July 2006 11:31:04 am

Hi Thorgrim

I would recommend you to take a look at Nexus Admin from Nexus Consulting in Norway, this is a great administration interface that cover the basic needs of content editors.

http://ez.no/community/contribs/applications/nexus_admin

Best regards
Egil Fujikawa Nes

BuildCMS - Av. Paulista 777, 15° Andar - CEP: 01311-100 - São Paulo
URL: http://www.buildcms.com

Jacek S

Sunday 23 July 2006 2:09:10 pm

Thanks for answer.
This Nexus Admin looks great, but I think it still too complex.
I also have decided to build my editors interface from scratch.

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 19:03:12
Script start
Timing: Jan 18 2025 19:03:12
Module start 'layout'
Timing: Jan 18 2025 19:03:12
Module start 'content'
Timing: Jan 18 2025 19:03:13
Module end 'content'
Timing: Jan 18 2025 19:03:13
Script end

Main resources:

Total runtime1.1226 sec
Peak memory usage4,096.0000 KB
Database Queries57

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0057 589.4766152.6406
Module start 'layout' 0.00580.0060 742.117239.4766
Module start 'content' 0.01171.1094 781.5938532.0078
Module end 'content' 1.12110.0015 1,313.60168.1250
Script end 1.1226  1,321.7266 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00610.5415160.0004
Check MTime0.00360.3237160.0002
Mysql Total
Database connection0.00070.064110.0007
Mysqli_queries1.066294.9783570.0187
Looping result0.00070.0620550.0000
Template Total1.076395.920.5381
Template load0.00270.242920.0014
Template processing1.073695.629120.5368
Template load and register function0.00020.021310.0002
states
state_id_array0.00150.134010.0015
state_identifier_array0.00150.134620.0008
Override
Cache load0.00240.2135220.0001
Sytem overhead
Fetch class attribute can translate value0.00130.114720.0006
Fetch class attribute name0.00150.131640.0004
XML
Image XML parsing0.00060.050920.0003
class_abstraction
Instantiating content class attribute0.00000.000840.0000
General
dbfile0.00170.1504160.0001
String conversion0.00000.001040.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
3content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
4content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
5content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
1content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 15
 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs