h1. Documentation Team Meeting Minutes 2013-04-18
h2. Attendees
Martin Bless, Michael Schams, Christopher Stelmaszyk, François Suter
h2. Official manuals
* François still working on Core APIs
** updates for TYPO3 6.0
** reworked some older sections
* TSref, up to date for 6.1, a few details to work out
* check TSconfig
* list of officially unmaintained manuals
** Inside TYPO3
** Skinning Reference
** TYPO3 Services
** Frontend Localization Guide
** => Use the "comments" column to mention status (unmaintained, work in progress, etc.)
* Static "glue pages"
** Originals are in /home/mbless/HTDOCS/git.typo3.org/Documentation/DocsTypo3Org.git/
=> Edit these files!
= \url{http://docs.typo3.org/~mbless/git.typo3.org/Documentation/DocsTypo3Org.git/}
Rebuild possible with request\_rebuild.php in the according DocsTypo3Org.git.make/ folder.
* the overview (\url{http://docs.typo3.org/typo3cms/)} could display the versions of TYPO3 for which they are compatible. This is difficult for now.
h2. T3DD13
* attendance
** François
** Martin
* workshops
** Introduction to ReST by Martin, running all day with quick introduction every full hour
** Viewing ReST-based documentation in the TYPO3 BE, by François (in particular (system) extension manuals)
** submit at \url{http://t3dd13.typo3.org/call-for-papers/submit-your-papers/}
h2. ReST migration for sysext manuals
* target 6.2
** ReST sysext manuals will then be included in the TYPO3 Core.
h2. Renaming of Documentation related projects
Check the notes here \url{https://notes.typo3.org/p/renaming-technical-todo}, section "forge"
Are they OK?
Should we really keep the extension keys in the project names? We do not use these keys anymore.
=> Maybe better change to Git Repository Names?
extension key Git repo name (part "**CMS**" each time to be added) new project identifier
=> For all of our git repos add "CMS" => Identifier matching to the path of the Git repo
E.g.:
doc\_core\_tsref Documentation/TYPO3CMS/Reference/Typoscript documentation-typo3cms-reference-typoscript
* redirects from the old URLs to the new ones would be great :-)
h2. docs.typo3.org
* extension manuals
** improved the current extensions page (\url{http://docs.typo3.org/typo3cms/extensions/)}
* François to ask Fabien, if he can be available for that job on the Flow application; otherwise maybe someone else can do it.
* docs.typo3.org resources:
** Resources used on docs.typo3.org (JS, CSS, etc.) stored on Github: \url{https://github.com/marble/typo3-docs-typo3-org-resources}
** Documentation rendered to: \url{http://docs.typo3.org/typo3cms/drafts/github/marble/TheResourcesOfDocsTypo3Org/}
h2. Priorities
Reminder of priorities defined early 2013
# extensions page improvements (done)
# version switcher
# Solr indexing
# TER integration
# Flow application
# migration to ReST for 6.2 sysext manuals
h2. Competitor workflow enabling documentation contributions
Proposal currently on hold. The main issue is about breaking the current workflow requiring Core changes and Documentation changes to be coupled.
h2. Miscellaneous
* Christopher updated the MediaWiki software of the TYPO3Wiki
* The next mediawiki (major) update will break our extensions. More work will be needed for this update.
h2. Next meeting
* Thursday, May 16, 2013, 21:00 CEST