eZ Publish documentation - what's next?

Wednesday 20 April 2011 1:49:21 am

By : Geir Arne Waaler

The eZ Publish documentation has always been a shared effort with many different contributors putting word on word, code snippet on code snippet. Slowly it has evolved into what it is today, an information highway. The standards and quality of this highway can and should be discussed, and it can surely only be evaluated by its users.

eZ Systems would like to open up for more discussion and feedback from eZ documentation users. Indeed eZ Systems would like to see a community effort towards the documentation in a different and much larger scale than today. We are still discussing the form of this new type of collaboration and at this point I only wish to get your opinions on this. But we are discussing rewards, competitions, prices, paying for services ..... I will keep you updated on the progress.

Jaroslaw Heba at eZ Support took this "springy" picture!

 

Feedback please!

What form could such a collaboration take? What is the most important thing we could do to the documentation? What are the weak spots? Do we miss some information? Is the language too technical? Not technical enough?

Please be specific with your feedback!

We will push on with the planning of this new collaboration, and will come back soon with more information/channels for collaboration.

Best regards
Geir Arne Waaler
eZ Documentation

 

Commenting and FAQ

Note 1: We regret the closing of commenting on our documentation pages. We are working on ways to avoid the spamming and hope to open up this very valuable feedback channel as soon as possible.
Note 2: The community have requested a FAQ for the documentation pages. Indeed I have started work on this and I am open to comments/suggestions on that topic as well!"

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 17 2025 23:54:41
Script start
Timing: Jan 17 2025 23:54:41
Module start 'layout'
Timing: Jan 17 2025 23:54:41
Module start 'content'
Timing: Jan 17 2025 23:54:41
Module end 'content'
Timing: Jan 17 2025 23:54:41
Script end

Main resources:

Total runtime0.0893 sec
Peak memory usage6,144.0000 KB
Database Queries48

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0051 589.0313152.6250
Module start 'layout' 0.00510.0023 741.656339.4531
Module start 'content' 0.00740.0806 781.1094492.9531
Module end 'content' 0.08810.0012 1,274.062515.7031
Script end 0.0893  1,289.7656 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00283.1648160.0002
Check MTime0.00121.3712160.0001
Mysql Total
Database connection0.00101.065910.0010
Mysqli_queries0.038843.4370480.0008
Looping result0.00030.3486460.0000
Template Total0.060467.620.0302
Template load0.00212.361320.0011
Template processing0.058265.201520.0291
Template load and register function0.00010.116410.0001
states
state_id_array0.00252.806820.0013
state_identifier_array0.00141.517830.0005
Override
Cache load0.00192.0882300.0001
Sytem overhead
Fetch class attribute name0.00293.237940.0007
Fetch class attribute can translate value0.00000.036010.0000
class_abstraction
Instantiating content class attribute0.00000.012540.0000
XML
Image XML parsing0.00202.261510.0020
General
dbfile0.00323.6298140.0002
String conversion0.00000.008040.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.tplblog_entry/full.tplextension/community_design/design/suncana/override/templates/blog_entry/full.tplEdit templateOverride template
2content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
7content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
1content/datatype/view/ezxmltags/embed.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/embed.tplEdit templateOverride template
1content/view/embed.tplembed/image.tplextension/sevenx/design/simple/override/templates/embed/image.tplEdit templateOverride template
1content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
3content/datatype/view/ezxmltags/emphasize.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/emphasize.tplEdit templateOverride template
2content/datatype/view/ezxmltags/separator.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltags/separator.tplEdit templateOverride template
2content/datatype/view/ezxmltags/strong.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/strong.tplEdit templateOverride template
2content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1content/datatype/view/ezkeyword.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezkeyword.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 24
 Number of unique templates used: 12

Time used to render debug report: 0.0001 secs