2008-07-24 DanielSteffen Friday via skype about documentationtypo3org¶

import manuals into TYPO3 as pages:

• ext bitsoffice, needs improvement for images, needs docbook-support

1500 manuals with 10 pages

• 15000 TYPO3-pages, 50...150 logged-in-users who edit their documents or translate [maholtz: they would not write or translate it at the same time i think:) perhaps 10 logged-in-users would be "many"]
  • needs own server for this
  • alternative: "diese Seite melden" with comment what the problem is and the new text that should be there ++ must be shown as comment - so it's not a problem when the author doesn't react for months [maholtz: +1 most important feature i think]
  • [maholtz:] on every page an mailto-link to the author of that page/tree, and a possibility to become an author/co-author of an page like in dmoz.org
    • overview-list for every manual-author: liste of all needed changes and checkbox to mark as "DONE"
• process: timeout of an extension or extension-manual. e.g. warn when it's 1 year old without a change, remove when it's 1.5 years old without a change [maholtz:+1]
• process: extension to mark manual-sections as draft/review/publish/published
• performance-optimization: staticfilecache from michiel roos: static pages can be saved as HTML but they cannot contain a plugin for the moment [maholtz: i did that via ajax, so i can use statifilecache with user interaction]

DATA-STORAGE: as TYPO-Seiten, not as docbook-files

• why: all TYPO3-features are usable [maholtz:+1]
• export regularly or when the manual-author clicks on a button: export to docBook and archive in SVN
• export as PDF: nc_pdfgen