Skip to end of metadata
Go to start of metadata

<ac:macro ac:name="tip"><ac:parameter ac:name="title">How to join the documentation and translation teams:</ac:parameter><ac:rich-text-body>
<li>Yes! We need your help <ac:emoticon ac:name="smile" /> .. <a href="">Translations' Status</a></li>
<li><ac:link><ri:page ri:content-title="Contributing to Zend Framework" /></ac:link> - See #1 to #4.</li>
<li><ac:link><ri:page ri:content-title="Documentation Standard" /><ac:link-body>Follow our documentation style guide.</ac:link-body></ac:link></li>
<li>Introduce yourself and interests by posting to the fw-docs mailing list.</li>

<ac:macro ac:name="note"><ac:parameter ac:name="title">"Master" manual</ac:parameter><ac:rich-text-body><p>The English version of the manual is the "master" document from which other languages are translated. All translation members are encouraged to help improve and add (e.g. examples, FAQ) to the English manual. Improving the quality of the content helps reduce support requests sent to the list, and results in more successful and enjoyable deployments by developers new to the ZF.</p>

<p>Adding substantial deviations directly to the translations would in effect create multiple master documents, and staying in sync becomes a nightmare quickly. Instead, where translators discover improvements can be made (there is plenty of room!), these should be either made directly to the English manual, or added as new <a href="">JIRA</a> issues for the English manual. Teams simply continue to track changes to the English "master" version for translation.</p></ac:rich-text-body></ac:macro>

<ac:macro ac:name="toc" />
<h1>Teams introduction</h1>
<h2>Documentation Team</h2>

<p>The ZF documentation team helps with tasks and projects affecting all versions of the manual. Many tasks require only basic English skills, so we <strong>strongly</strong> encourage participation by everyone. All documentation team members are also encouraged to help with the English manual. Many edits, improvements, example contributions, and merging of user-contributed comments do <strong>not</strong> require strong English skills. Content and accuracy are much more important than "perfect" English, and English experts can adjust wording as needed later.</p>

<p>The documentation team has the authority to edit the English manual. Documentation project team members include:</p>
<li>All Translation project members</li>
<li>All <a href="">English manual project members</a></li>
<li>All Zend ZF team members</li>
<li><ac:link><ri:user ri:username="andries" /><ac:link-body>Andries Seutens</ac:link-body></ac:link>:
<li>automatic translation of docbook to Wiki</li>
<li>automatic translation of Wiki to docbook</li>

<h2>Translation Teams</h2>

<p>Each translation team gets his own wiki page. On these pages the team can list its members and resume where the team is needing help, e.g. We encourage people to communicate in whatever language they prefer. The language translation team wiki pages support UTF-8, including Japanese and Chinese. Translation teams include:</p>

<ac:macro ac:name="children"><ac:parameter ac:name="page">Documentation Team</ac:parameter></ac:macro>

<p>If you see this "<ac:link><ri:user ri:username="nocla" /></ac:link>", then please ask that person to <a href="">send a CLA</a> before contributing.</p>

<h1>Help wanted</h1>
<h2>"Wikification" of the Manual</h2>

<p>We have documented numerous cases and examples where the current process imposes too many hurdles, complications, and effort for those wishing to use it and contribute. Since the vendor of our current wiki successfully uses their own product for their manual, including generating the PDF and HTML, we would like to consider the implications of switching from authoring content in docbook to using our wiki.</p>

<p>We are proposing opening up the English documentation process to participation by all documentation team members, and allowing wiki page commenting by anyone, but with reasonable moderation by the documentation team members, following in the footsteps of wikipedia. In order to help achieve consistency, we are also proposing borrowing <a href="">'s</a> documentation style guide, subject to exceptions you might recommend (hint).</p>

<p>The process for adding content and editing the ZF manual pages might benefit from the use of a wiki that allows user-contributed comments. How many times have you wanted to make a suggestion or change to the English manual, but not done so?</p>


<li>Make a PDF and HTML copy of the manual available for download.</li>
<li>Make smaller edits easier, and possible by at least everyone on the documentation / translation teams, possibly including all CLA signers.</li>
<li>Reduce the learning curve and effort required to make edits to the manual and translations.</li>
<li>Allow anyone to comment on each section, but with comment moderation, so that the manual can evolve more quickly and with more flexibility than the current process.</li>
<li><ac:link><ri:page ri:content-title="Documentation Standard" /><ac:link-body>Follow a documentation style guide</ac:link-body></ac:link> and proofread before it is released.</li>
<li>Need to support offline editing of content, ideally with a plain-text import/export capability. Alternatively:
<p>1. Click the "Edit" tab for the page<br />
2. Select all and copy the wiki markup<br />
3. Paste it into my text editor<br />
4. Save a copy as "page title.txt.orig"<br />
5. Save a copy as "page title.txt"<br />
6. Continue editing "page title.txt" <ac:link><ri:page ri:content-title="offline" /></ac:link> until complete<br />
7. Review the diff of "page title.txt.orig" and "page title.txt", revising the latter as necessary<br />
8. Paste the revised wiki text into the wiki markup tab of the page editor, and save the page
<br class="atl-forced-newline" />
In this way, one can work on the wiki pages offline when needed.<br />
Edits from different authors can be merged using the wiki.</p></blockquote></li>
<li>Quick access: type <a href=""></a> similar to, where you can easily access a specific function by appending it to the url</li>
<li>Unreleased incubator documents should be avaiable in wiki, but not added when extracting to HTML and PDF (Maybe tagging or a seperated wiki space).</li>
<li>Some contributors are writing like "this function can handle xxxx" other as "you can handle xxxx with this function"... note the first person stlye... a defined write style is <strong>must</strong> and makes the document flow smoothly as a whole.</li>
<li>Automatically generate HTML and PDF for each language, either directly from the wiki, or from docbook, after auto-generating docbook from the wiki.</li>

<li>Study <a href=""></a> information on features, including the user manual</li>
<li>Research plugins and current efforts to export the wiki to docbook. <a href=""></a></li>
<li>Research possibility of tagging pages, such that a PDF could be created from tagged pages.</li>
<li>Consider adding "edit last comment" to our issue tracker (Jira), and search for a way to do so with our wiki (Confluence).
<li><a href=""></a></li>
<li><a href=""></a></li>
<li>Decide on moderation process / policy for comments.</li>
<li>Provide feedback to an example docbook to wiki converted page: <a href=""></a></li>
<li>Provide feedback to an example new wiki homepage: <a href=""></a></li>

<h3>Process Mechanics</h3>

<p>The purpose of the wikification includes removing the need for any of us to write docbook. </p>

<p>1) Docbook to wiki import (one time only)<br />
2) Translators and english manual authors use the wiki to author content, but they should restrict and limit themselves to the basic wiki markup already found in the wikified manual pages.<br />
3) All CLA signers use the wiki to comment<br />
4) Translators and english manual authors review comments, sometimes deleting comments and merging comments with the wiki page content<br />
5) Wiki to docbook export (every time we make a release of the ZF)<br />
6) We use normal docbook to HTML/PDF process to publish updates to <a class="external-link" href=""></a><br />
7) If we can export the wiki to HTML/PDF and they look as nice as #6 above, then we can use the HTML/PDF created by the wiki to HTML/PDF process. The wiki to HTML process could be either something custom, using Zend_Pdf, or using Confluence export. However, we still don't want to lose the ability to convert back to docbook, just in case we need the docbook formatted version of the manual for some other reason. To keep this ability and make wiki to docbook conversion easier, wiki authors must not use "fancy" wiki markup (use only basic tags that are already used in wikified manual).</p>

<p>Please enter our brainstorm time, where we can openly consider all ideas to help synthesize a final proposal, before decisions are made.</p>

<p>For the mechanics of this new process, we could setup <strong>two</strong> new wikis. One would contain the last official release for public viewing and commenting. The other would be a draft, work-in-progress with comments rolled into the body of the page before pages are "released". When we prepare for a release, changed pages could be copied to the official release wiki. Then, translators could use the wiki "difference" feature to see what has changed in the English manual on the release wiki, without seeing all the interim edits made in the draft wiki.</p>

<p>There might be a wiki plugin that allows tagging and viewing differences between tags ( <a href=""></a> ). If so, such a feature/plugin might eliminate the need for having two wikis. I am not eager to consider using a different wiki, as it would significantly complicate user account administration and logins. The current wiki already supports UTF8 text.</p>

<p>Our current wiki system supports export to PDF and HTML, although the exports are "plain", and might require some creative manipulation, such as using Zend_Pdf to beautify it. I agree entirely with recent posts about the value of providing HTML and PDF downloads for the manual. Several questions remain, including the docbook import/export process for our wiki (Confluence).</p>

<p>Also, incubator components using the wiki for documentation would make documentation available immediately, without requiring the curious to go through the process of "building the manual". Many of us would like to help with documentation for the new incubator components. Group editing of a wiki page has advantages over trying to coordinate editing of the documentation via SVN.</p>

<h2>Wiki Maintainers</h2>

<p>The <a href="">ZF Sidebar</a> helps greatly, the organization and look and feel of our wiki pages could be improved. <a href="">Drupal's</a> website demonstrates an orchestrated, planned arrangement and organization of content. Their content is somewhat similar to that found in the ZF wikis, so perhaps we can borrow some organizational ideas.</p>

<p>We are looking for volunteers to proactively define this team's mission, responsibilities, and tasks.</p>


<li>Managing: <a href=""></a></li>
<li>Maintaining site maps for each wiki space</li>
<li>Provides recommendations for changes to ZFDEV, etc. wiki spaces</li>

<h3>Milestones & Tasks</h3>

<li>Improving organization of wiki</li>
<li>To make sure users can easily find what they are looking for in our wiki</li>
<li>Bring logic structure in every page, and set some standards</li>
<li>Site Maps</li>

<p>Currently the I18N team is looking for your help. They are looking for people to document the already commited code, write examples and use cases. Interested? Please <a href="">Subscribe to fw-i18n</a> and <a href="">send a message</a>.</p>

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.