New on eZpedia:about

Latest News

Mon, 01 Jan 2007 11:29:20 GMT

Checkout the latest reported news on anything eZ Publish via eZpedia (Recently, Email, Rss, Feeds, Main, About), eZ Projects (WebSVN, ViewVC), PubSVN, eZ Publish Planet, eZ Publish, Developer, News, Articles, Forums or eZ Systems!

Subjects

Mon, 01 Jan 2007 11:25:05 GMT

Subjects

Read and update documentation on any eZ subject current or otherwise, created by the members of the community or from eZ Systems

Learn! Developer, development and extension documentation educates how to extend existing or add new functionality within eZ publish
Search! For solutions to questions previously solved and best practices
Study! The source code api documentation
Report! Review and report unique issues using eZ Systems' issue management site for all their products (eZ Publish, eZ Components, eZ Newsletter, Online Editor, eZ Find)
Review! Changelogs;
Read! The latest commits to the eZ Publish public subversion repository via rss
Download! The latest eZ publish source code, extensions, source code and official releases

Tips

Mon, 01 Jan 2007 11:23:19 GMT

Tips

Read! Our faq of documented problems, experiences, references and solutions!
Search! Still searching for answers, experiences or references? Consider searching eZpedia, ez.no, your favorite search engine via browser search plugins or GooZee with related keywords.
Write! Still can't find a clear answer? Ask your questions in clear, detailed, unique way via the irc and then in forum.
Clear! Try clearing all the cache!
Support! Support eZ community projects!

Support the community!

Sun, 31 Dec 2006 15:05:02 GMT

Support the community!

Support the eZ publish community by getting involved and speaking out!

Do you have ideas for the community, send feedback, adding a suggestion, reporting an issue, signing in and completing a task, all highly encouraged!

Adding new eZ publish documentation (contributed by the community) extends benefits beyond traditional boarders and limitations; reducing tco for everyone.

The very diverse eZ community supported projects, including PubSVN and eZpedia.

Introduction

Sun, 31 Dec 2006 14:46:04 GMT

Welcome to eZpedia!

eZpedia is a community driven effort who's goal is to create complete sets of freely available 'eZ Publish' documentation created and maintained by the community for the community.

"eZpedia.org is still 'under development'. So ... not everything may work quite how one might suppose or expect ... yet."

Namespaces: eZ, People, About, Templates, Help

If your looking for a general overview of eZpedia review the contents of each namespace.

Additions via RSS

All
About

Namespaces

Sun, 31 Dec 2006 14:37:07 GMT

Namespaces: eZ, People, About, Templates, Help

If your looking for a general overview of eZpedia review the contents of each namespace.

Spotlight

Sat, 30 Dec 2006 23:38:54 GMT

History

Fri, 08 Dec 2006 17:38:10 GMT

How it started

Motivated by the eZ community, Kristof Coomans started to work on an eZ publish wiki short before the summer holidays of 2006. During the summer he set up a first prototype on pubsvn. Afterwards, the project was put in the refrigerator for a while.

At the beginning of November 2006 the project was restarted by Kristof and Graham Brookins. They decided to bring a couple of important community members together in what Kristof called the "board". This group would decide on the future directions of the wiki project.

Heavily inspired by Wikipedia, Kristof proposed to call the project eZpedia. And so eZpedia was born.

Promotion

Tue, 28 Nov 2006 08:44:09 GMT

Articles about eZpedia

2006-12-08	eZ publish community world map (via eZpedia)! blog article by Kristof Coomans	English
2006-11-28	eZpedia ! blog article by Damien Pobel	French

RSS

Sun, 26 Nov 2006 10:32:52 GMT

The following eZpedia RSS feeds are available for consumption:

All
About

Originaly Named

New on eZpedia: new articles in the primary namespace
New on eZpedia:about: new articles in the namespace "about"

These feeds provide notification of new published entries on eZpedia.

These feeds do not provide update notification of updated entries on eZ pedia. Notifications can be configured to send email alerts when entries are updated as an alternate solution.

eZ systems

Sat, 25 Nov 2006 11:01:02 GMT

This article describes the relation between eZpedia and eZ systems. For more information on eZ systems in general, take a look at eZ systems in the main namespace.

eZpedia's main contact inside eZ systems is Jennifer Zickerman, manager of knowledge products.

Mirror

Tue, 14 Nov 2006 12:21:24 GMT

You are encouraged to make available public mirror sites of eZpedia. Follow the eZpedia installation instructions.

List of mirror sites

Please add your mirror here (preferably in an unordered list):

Disclaimer

Tue, 14 Nov 2006 10:28:29 GMT

Summary

All documentation on eZpedia is available under the GNU Free Documentation License and source code is also available under the GNU General Public License.

All content under the eZpedia is licensed under the terms of one of two GNU Licenses.

Please, do not submit copyrighted material!

Documentation

The documentation is available under the GNU Free Documentation License.

All documentation contributions will be released under the terms of this license.

Source Code

The source code examples and components are available under the GNU General Public License.

All source code contributions will be released under the terms of this license.

eZpedia board meeting 1

Mon, 13 Nov 2006 20:10:07 GMT

The first online eZpedia board meeting is scheduled at Tuesday the 29th of November 2006, 6:00 PM GMT.

People invited

Currently Graham Brookins, Kristof Coomans, Paul Borgermans, Paul Forsyth and Xavier Dutoit have been invited.

Agenda

Kristof supposed that all invited people would have seen this wiki article, but unfortunately they didn't. Therefor the meeting did not have an official agenda. This is the agenda that was initially proposed:

wiki framework
1. general content structure: namespace, article, discussion forum, user
2. linking content
3. tracking changes
  1. history
  2. RSS feeds
4. installation
5. mirroring
content
1. definition of needed namespaces and their intended usage
2. editor guidelines
3. reviewer guidelines
4. translator guidelines
5. languages
  1. french translation - we already have one volunteer!
6. license
collaboration with eZ systems
1. promotion on ez.no
2. gradual incorporation of eZpedia docs into doc.ez.no
3. cross-linking
4. list of eZ systems documentation priorities
5. import of eZ publish 3.4 old documentation content
division of responsibilities and tasks

Report

Details

Present: Kristof Coomans, Paul Borgermans, Paul Forsyth and Xavier Dutoit

Absent: Graham Brookins (excused afterwards)

Start: 6:05 PM GMT

End: 7:15 PM GMT

Minutes

Import old documentation

eZpedia likes to import the old community documentation from ez.no. There are several ways to grab the content:

content object package export
wget (proposed by Paul Forsyth)

We decided to ask eZ systems for a content object package first. Kristof will contact Jennifer Zickerman, Manager of Knowledge Products.

Paul Forsyth mentions there are even older documentation sites: .

Collaboration with eZ systems

We talked about a possible collaboration with eZ systems. Kristof has send some ideas to eZ systems.

promotion on ez.no
validation of eZpedia documentation by eZ systems

Jennifer Zickerman, Manager of Knowledge Products, replied.

All the community documentation projects will be listed somewhere at doc.ez.no, with prominence given to eZpedia. eZ systems wants to encourage eZpedia authors to cross-link between the existing eZ docs and the docs on eZpedia.
They also will assist in cross-linking as much as they can. The community newsletters can mention new docs on eZpedia when there's an RSS feed available.
eZ systems does not have the resources to validate docs on eZpedia. However, they like to gradually incorporate material from eZpedia into doc.ez.no.

Xavier mentions that incorporating something from the community hasn't been eZ system's key strength so far.

Handling outdated documentation

Paul Borgermans notes that the old docs need careful review. We should explicitly mark them as being outdated:

"not dead, but smells funny" (Xavier)
"this doc sucks! it needs rejuvenated" (Paul Forsyth)

Paul Forsyth proposes to let a cron job send out spam mail to maintainers when docs are out of date.

eZ publish version info

Paul Forsyth asks if we will follow the eZ systems model of having seperate documentation for each new release. Kristof thinks this is not a good idea. What if a new major release contains features you're looking for? This can be an incentive to upgrade. Paul Borgermans adds that having seperate documentation for each release hides the changes between those releases.

Xavier proposes to add tags/keywords with an enhanced objectrelation attribute with version objects (3.5, .6...). If a page applies from 3.8 only, you tag it 3.8 and 3.9. For the few cases there are differences, you simply write it in the doc (as php does for instance). Having several enhanced object relation attributes allows you to use them as filters in a search form.

Kristof notes that you can keep adding attributes for certain criteria while these attributes are irrelevant for certain documentation pages. He rather likes to use ezxml, and the 3.9 enhanced object relations in ezxml (links and embeds). This way of working is similar to Wikipedia.

Xavier notes that having a specific attribute would put a focus on that specific criteria, as opposed to the ezxml embed and link tags. It's also easier to check 3.7 and 3.8 than to embed/link to the 3.7 and 3.8 page, unless you enhance the content/browse interface for this purpose.

Autolinking

Xavier is wondering if we can support some way of autolinking. Kristof replies that he has some ideas. Maybe it can be easily done by a workflow.

Roadmap

Sun, 12 Nov 2006 05:32:22 GMT

This is a Stub article. Help the eZ Publish community by expanding it!

Translations

Sun, 12 Nov 2006 05:23:46 GMT

eZpedia

eZpedia provides for entries in the following languages.

Language	Description	Articles
English	Default Language; The Free eZ publish Encyclopedia	525
Français	L’encyclopédie libre eZ publish	17
Español	La enciclopedia libre eZ publish	26
Nederlands	De vrije eZ publish encyclopedie	1
Polish	Ten Wolny eZ publish Encyklopedia	0
German	The Free eZ publish Encyclopedia	0

Translation

Sun, 12 Nov 2006 02:57:40 GMT

eZpedia Translation Roadmap

Goal

Automated translation of content to alternate languages.

Requirements

Automated Content Object Translation
Supported Translations
Translation Team

Dependencies

Translation Verification Schedule Negotiations and Planning
Translation team verification of resulting translations of namespace nodes.
Translation team's translation verification status board (node link).
Update Mirror Data Exports
Translation Service - External with large language support (Google?)

Deliverables

Create Translation(s) (eZ publish admin, cronjob and php-cli script)
Remove Tranlation(s) (eZ publish admin, cronjob and php-cli script)
Update Translation(s) (eZ publish admin, cronjob and php-cli script)
Updated Mirror Data Export(s) (eZ publish admin, cronjob and php-cli script)
Google Translation API Implementation for eZ publish as an extension
eZ publish Automated Content Object Translation Extension (ezcontentobjtranslation)

Supported Translations

Target list of documentation translations which eZpedia might support based on demand and participation from the community.

Status: Draft

en_US
French
Spanish
Italian
Chinese
Japanese
German
Polish

Translation Team

Members of the international community reviewing the automated translations meet the desired criteria.

No volunteer(s) at this time

Schedule

No plans at this time. Marginal, lukewarm interest or support in building and maintaining this solution

License

Sat, 11 Nov 2006 16:13:27 GMT

All content under the eZpedia is licensed under the terms of one of two GNU Licenses.

Please, do not submit copyrighted material!

Documentation

The documentation is available under the GNU Free Documentation License.

All documentation contributions will be released under the terms of this license.

Source Code

The source code examples and components are available under the GNU General Public License.

All source code contributions will be released under the terms of this license.

News

Sat, 11 Nov 2006 13:55:44 GMT

Changelog

All about eZpedia's changes, improvements and additions.

2007-08-21 - Upgrade - eZpedia upgrades to eZ publish 3.9.5

2007-09-04 - Upgrade - eZpedia upgrades to eZ publish 3.9.3

2007-01-01 - Press - 'Happy New Year' from the eZ community!

2006-12-19 - Upgrade - eZpedia upgrades to eZ publish 3.9.0.

The following new features in the 3.9 branch will be quite useful for the wiki:
History view, Class/classattribute name translation
XML block: improved custom attributes, Improvements to related objects added from XML block text field, other new features

2006/12/08 - Press - Announced eZpedia on ez.no forum!

2006/11/10 - Content - Added news node!

2006/11/13 - eZpedia updated to the latest eZ online editor 4.1.5

2006/11/09 - Performance - Improved oe performance and toolbar button issue, bug fix.

2006/11/06 - Upgrade - eZ publish to version 3.8.6 + eZ publish online editor to version 4.1.4 + Lucene search plugin

Support

Sat, 11 Nov 2006 04:18:25 GMT

Supporting The eZ publish Community

While everyone can learn from reading the documentation, still ... others may see a need to refine the content, composure or structure of the existing documentation.

Create Documentation

If your interested in adding to the text documentation ... try adding a new document or extending an existing document. If you want to get involved as an editor, then please read our editor guidelines and sign up!

Document an existing contribution
Document an eZ publish topic of your own personal interest
Document your eZ publish experiences and favored solutions
Document an existing solution from an alternate source, say ez.no/community/forum
Answer a unique question from an alternate source, say ez.no/community/forum
Document how to implement (solve) a requirement (problem) into a solution
Document eZpedia, make a suggestion or report an issue.
Add your own private contributions to pubsvn, ez.no, ezpedia
Add existing ez.no contributions into pubsvn's subversion repository
Document eZ architecture and design concepts

If you are interested in improving this wiki outside of content modifications, build an eZpedia mirror (link), impliment a requested feature, confirm a bug, fix a bug, submit a patch.

Create Alternative Documentation

Try new ways of documenting your work. Look at what the movers and shakers do. Take the next logical step. Become a subject matter expert on documentation.

Text (eZ publish) Documentation
Text (Related) eZ dependencies documentation
Text (Related) eZ dependencies configuration documentation
Articles, HowTo(s), Example Source Code
Video Tutorials
Video Presentations
Audio Tutorials
Audio Comments

Promotion

Tell a friend about eZpedia (link to email friend this page)!
Write an article on your own website. It will be listed on the promotion page.

BecomeAnArchivist

Tue, 07 Nov 2006 01:50:52 GMT

Archivist

How to become ..

Friendly Introduction

Help:Editors! eZpedia needs editors!

A community members who encounter a problem which turns out to have been solved long ago, not known to the general public, or simply recently uncharted or revisited subject mater. After a time an answer may be found by one, many, most or all independently or collaboratively. The distance between the time exhausted by multiple participants over say 3 months and the time required to document a subject before setting the matter aside is astonishing.

The collaborative sway of the entire eZ publish community, the folks who wake up and find themselves thinking about something eZ related, these are the folks who are all investing (for whatever the benefit) in the 'eZ' platform, these are the same folks who upon encountering a solution have not known how best to share those experiences, situations, solutions.

Suggestions

I tend to create most of my documentation using a very simple method.

Document what you do while you work and the amount of available documentation will increase (as will your knowledge of the systems or tools you use).

Be a history archivist. As you work or watch others in the various methods in the eZ ecosystem; Document all the related key pieces of the information regarding the conversation / problem and solution required to reproduce and resolve the problem (to local text file for example)
Be thorough (if you can), document the participants of the conversation and the date/time (to local text file for example).
Be polite. Ask for permission to submit an entry to the community documentation, Licensed using the GFDL.
Be an author. Review existing nodes for example content formatting, Write up the conversation publish, maintain and promote your node!
Be an editor. Review existing nodes for common spelling, formatting, linking, toc, etc errors. Document errors and or make proof-reading corrections.
Be a maintainer. Maintain, revise, promote your node!
Become a maintainer. Maintain, revise an existing node which has not been maintained (unless it is version specific)

The quality, medium, and quantity of available eZ publish community documentation depends on the contributions made by the very community who needs it.

I think it's a given we really want to encourage people to stop what they are doing right now mid sentence and go create their first node!

If you come back and discuss; well, that's a plus as well ...

eZpedia - Meeting Minutes - 2006/11/04

Sun, 05 Nov 2006 03:20:06 GMT

Meeting Minutes

Details

Date: 2006/11/04 @ 08:48:50 - 09:43:11 (20:07:47)

Description: eZ publish community ( eZpedia / pubsvn.ez.no ) documentation wiki solution - meeting notes

Participants: Kristof and Graham

Summary

- Wiki is open to public user registration and editing!
- Development plans are forming for the next 60 days and beyond
- Community Members will represent the group driving development and direction of the Wiki
- All of the wiki solution will be quickly made available via pubsvn subversion repositories (design, code and database content)
- Community Discussions regarding the wiki solution will be available on ez.no/community/forums

Minutes

Intro

- Kristof is quite busy with other projects at the moment.
- Kristof seeks to make arrangements regarding the community wiki
- Kristof remarks there's still some work to do on the wiki solution itself as a whole.
- Kristof notes there are some improvements in eZ 3.9 which will be of great benefit for the wiki, like the automated object relations from the ezxml attributes for embed and link tags.

Opening wiki for user registration

- Paul and Kristof are giving everyone the opportunity to share your documentation and to collaborate using the wiki
- Graham says 'that's great news
- Graham comments, those in the 'how do i contribute documentation' thread in the forums will be pleased to hear of the opening of the wiki's registration.
- Graham comments, I see this becoming popular with folks looking to build community documentation as a way to avoid asking others for support or repeated support of reoccurring reproducible requests of similar subjects.
- Graham comments, I just see a real value in banking on the average small time eZ publish users contributing to better documentation for themselves and for others.
- Graham comments, The commoditization of these contributions over the long life of all things eZ, re: value and opportunity.
- Graham comments, Better documentation, ... linking to solutions rather than duplicate them.
- Graham comments, It also puts an end to eZ holds the community back in documentation comments made by newbies

Engaging the community for contributions

- Kristof will make publicly available the wiki design
- Kristof will create a thread on ez.no forums to discuss these efforts and publicly open user registration of the pubsvn wiki to the public.
- Kristof will post an invitation (to users) on the forum topic.
- Kristof will remain responsible for the set up on the pubsvn server.
- Kristof will upgrade the wiki to 3.9 when it's stable
- Kristof asks 'Do you have some sight on how to continue?'
- Kristof is too busy with other stuff but would really like to see this evolve too
- Kristof says, … I can't decide everything myself and I don't want to do that, would like a democratic wiki development :-)
- Graham agrees
- Graham comments, if one is too busy, another should rise to continue the work ...

Sharing the solution, keeping the commons

- Graham comments, If we don't share it all, I fear it will continue to stagnate ...
- Kristof says, every part of the wiki solution has to be available freely.
- Graham thinks the whole solution should be placed in a subversion repository via pubsvn. Including the design, base code additions / modification to eZ publish, settings and database dump. Share all the wiki solution, make all available for download, development, documentation mirrors and return changes.
- Kristof says, you can help with the configuration if you want … I can put that in svn too … no problem at all
- Kristof says, we can make a wiki article to document the set up … so everyone can set it up to test … and suggest improvements
- Graham grins and says, If you do I'll use it
- Graham says, In this way those who might step up and contribute if all the pieces are available for experimentation which we can encourage to return their improvements back to the 'board'.
- Graham says, As for the database, I too think this should be shared.
- Kristof already has as solution for this to export a db for external usage including documentation on the steps involved.
- Kristof suggests the creation of a script to easily provide mirror sites data exports.
- Graham says, With these key pieces to the project available I think it turns the tide in everyone's favor.

Community Board

- Kristof suggests a board of community members to manage the solution's development and direction.
- Kristof says, (the name of the wiki / docs) … that's something we should decide with the board
- Graham says, I'm all for democracy until it results in non-action, then I tend to take action :\
- Kristof will make available all parts of it (design) trough a svn repository on which the community members on 'the board' will have write access. The design is what I'm really going to make work … I expect it to be available in it's current form next Monday.
- Graham says, those who wish to contribute to the development of the wiki solution behind the scene should put there name in the wiki and contact Kristof via email.
- Graham comments, regardless of the backend development, content creation will continue as determined by user interest

Closing

- Kristof says, registrations are open now (pubsvn.ez.no/wiki)!
- Graham says, Thank you for opening up registrations
- Kristof wants to involve Sandro Groganz, Xavier Dutoit, Paul Forsyth on the conversation and will mail them.
- Graham will add new content nodes to the wiki during his testing.

Afterthought

- Graham wished he'd asked if selected imports of 3.4 content at a later time could be considered and estimated :(

This wiki

Thu, 18 May 2006 12:51:45 GMT

Contributions

Follow the "Create account" link in the upper left corner of this page, fill in the registration form, wait for the activation e-mail and you are ready to contribute!

Technology

This wiki is based on eZ publish, enhanced with the extensions and modifications listed in the following table.

Name/Extension/patch	Author	Current version	Notes
eZ publish	eZ systems	3.9.3
eZ Online Editor	eZ systems	4.2.3
eZpedia	Kristof Coomans	n/a
SCK•CEN Create copy workflow event	SCK•CEN, written by Kristof Coomans	1.0
redirect	Kristof Coomans	1.0
changelog attribute	Kristof Coomans	n/a
eZ Syntax Highlighter	Łukasz Serwatka	1.1	Optional
so far untitled search plugin using the Solr open source enterprise search server		n/a	Optional, currently not publicly available
eZ Author Contact	Łukasz Serwatka	1.0.0
mixed static content / logged in features	Geraint Edwards / Kristof Coomans	n/a	Optional
temporary bug fixes for static caching (bug #9126)	Kristof Coomans	n/a	Optional
temporary bug fix for wrong ui_context of language choice form (bug #9124)	Kristof Coomans	n/a	Optional
String Replace Operator	Lex 007	1
Google Maps Location datatype	Joe Kepley	0.4
temporary patch to add sorting to version_list fetch function (enhancement #9585)	Kristof Coomans	n/a	Optional
RSS fetch functions (enhancement #9933)	Kristof Coomans	n/a
Akismet	Kristof Coomans	n/a	Optional but requires workflow modification