Concept and ideas for new ter_fe extension

Project details

Views

  • List
    • New and updated
    • Popular
    • Full list
    • Categories
  • Detail
    • Info
    • Ratings
    • Feedback form
    • File preview
  • Search
  • Documentation overview and download
  • HTML documentation
  • Help (e.g. Render problems report)
  • Extension review
  • Hudson request
  • Link to forge

Obsolete extensions scheme

Extension Link Status Remark
ter http://forge.typo3.org/projects/show/extension-ter *?* Needs some revamping
ter_doc http://typo3.org/extensions/repository/view/ter_doc/current/ Under refactoring code has been overhauled - uses now cli_dispatch.phpsh
ter_doc_docbook http://typo3.org/extensions/repository/view/ter_doc_docbook/current/ Obsolete
ter_doc_html http://forge.typo3.org/projects/show/extension-ter_doc_html Obsolete unclear - should split up between ter_fe2 and ter_xsl
ter_doc_sxw http://forge.typo3.org/projects/show/extension-ter_doc_sxw Obsolete
ter_fe http://forge.typo3.org/projects/show/extension-terfe Obsolete new development goes under ter_fe2. Some features need to be split up into other extension

New extensions scheme

Extension Link Status Purpose
ter http://forge.typo3.org/projects/show/extension-ter Work started Web service that manages extension Upload. BTW, shouldn't it be renamed to ter_upload? ter_upload_manager?
ter_doc http://typo3.org/extensions/repository/view/ter_doc/current/ Work started generates and manipulates the documentation
ter_xsl https://svn.typo3.org/TYPO3v4/Extensions/terfe/branches/doc_family/ter_xsl Work started provides XSL service across TER
ter_fe http://forge.typo3.org/projects/show/extension-terfe Work started renders the documentation onto the FE
ter_key_management - To decide manage the key on the FE - old code is under EXT:ter_fe/pi2

Allocation of tasks

ter

  • Extension upload
  • Extension download from EM (Extension Manager)
  • Extension download from website (e.g. typo3.org)
  • Retrieve extension list from EM
  • Pack and unpack t3x-files

ter_fe

  • Render extension list on website
  • Show new and updated extensions
  • Search and browse extensions
  • Handle extension keys in restricted area
  • Handle extensions in restricted area
  • Provide version history for each extension

ter_doc + ter_doc_docbook + ter_doc_htm

  • Provide documentations in several formats:
    • HTML
    • DocBook
    • and of course OpenOffice document

Conversation with Steffen Kamper (TUGS)

  • Mirror servers will be fetched once a day
  • Download count will be read from Apache log files
  • The presence of ratings and comments must be increased
  • The conversion from manuals to HTML pages must be improved

Requirements for the new extension

  • Ensure as much compatibility as possible to current infrastructure and EM (Extension Manager)
  • Clean implementation with Extbase and Fluid
  • Fast and reliable
  • The design must be appealingly and compatible to typo3.org (maybe coordinate a typo3.org redesign)
  • Improved conversation from manuals to HTML pages
  • Increase the presence of comments and ratings, because they are important decision criteria
  • Implement additional sorting functions, e.g. by ratings or last update
  • Usage of SimpleXML instead of DOM
  • Integrate forge.typo3.org and Hudson
  • RSS Feed
  • Filtered search
  • Views with pre-filter (e.g. most active and most voted)
  • Maybe provide a „Hot or not“-voting for old extensions
  • Maybe show dependencies to other extensions in a graphical tree-view with links to other extensions
  • More suggestions on forge.typo3.org

More Features (Brainstorm)

  • Tags by extension owner and by users. Added tags from users can be deattached by extension author
  • Graphs representing download and activity
  • RSS Feeds, may be forge news automated with extension upload
  • The category system used by TER and EM is static, add free categories in extension management that are used by the index
  • Tutorials for extensions
  • Company, Sponsor and Paypal options
  • Social network integration (facebook, Twitter etc)

Additional extension informations (Brainstorm)

  • Count of PHP lines in all files
  • Similarly extensions by category / tags / downloads
  • Notification if an extension was updated (logged in users only)
  • Mark Extbase / Fluid extensions with default tags

Nice to have (maybe for future versions)

  • Tag filtering by clicking into tag cloud. (Click on "gallery" -> all extensions with tag "gallery" and in tag cloud all tags from these extensions, a.s.o.)
  • Analyze / optimize click path to final target of a user search for an extension
  • Similarly extensions by viewed extensions / downloaded extensions (logged in users only)

Requirements for the infrastructure

  • Save downloads in database and synchronize them with mirror servers, maybe use only one database server and multiple content provider servers
  • SOAP server and client
  • PHP 5.3

Testing Environment

Steffen will prepare a TER for testing, it will be available at:
http://ter.steffenkamper.info

Fabien has prepared a TER for testing, it will be available at:
http://dev.ter.typo3.org - testing purposes
http://ter.typo3.org - communication purposes