Actions

Meetings, Links, Logins

Who:
DanielBruessler http://forge.typo3.org/account/show/72
SteffenKamper http://forge.typo3.org/account/show/89
MartinHoltz http://forge.typo3.org/account/show/68

meetings (newest on top):

Testserver URI backend (With this we can make TESTS with rating, comments, manual-import and so on. You can play with this a bit!):
http://web23.gknetzwerk.de/typo3/

Who has admin-account to this test-server: Steffen, Daniel, Martin

Roadmap

We found out that it's best to edit the manuals via TYPO3, because there are MANY advantages. We have to export each manual as docBook, because that's the standard the TER needs. We have to import .sxw or docBook, because nobody wants to copy-paste a whole manual. A manual written in the wiki can be copy-pasted to an OpenOffice-"HTML-document" and then saved as .sxw

The first time (until January 2009) we can edit the manuals via TYPO3-Backend, for public usage we need to do it via FE-editing.

Tip: the EXT bitsoffice now can import ODT-documents

To do list

most important: TSRef and TYPO3 Core API -- as copy of the core-manual, so that comments and snippets are possible

the next steps

follow-ups

what we don't need for the moment

questions

  • ...

.

Updated by Daniel Brüßler about 13 years ago · 22 revisions