The document discusses the development and status of typo3.org, which has undergone multiple iterations since its launch in 2000. It highlights the community-driven efforts in redesigning the website, achieving significant milestones such as public previews and feature completions. Current challenges include technical upgrades, improving documentation, and engaging community contributions for ongoing maintenance and development.

1. typo3.org
The Information Hub

2. Welcome
· Joern
· Project leader and project manager at AOE media
· Ben
· Co-leader and community manager TYPO3
· Tolleiv
· Technical leader and senior developer at AOE media

3. A lot of people worked a long time
Before the Launch

4. The old typo3.org
· Launched in 2000
· Split 2002 into
· typo3.org
· typo3.com
· news.typo3.org
· Smaller improvements…

6. Pains
· No clear code-base
· Missing QA process
· Old maintainers not available
· Many hidden ''gems'' in the system
· Background tasks too load intensive

7. Ignition
· First start in 2007
· typo3.reorg
· Stopped in 2008
· Company attempt
· Stopped in 2009
· Restart from scratch in 2010
>T3O

8. T3O
The new Website

9. A community approach
· Company sponsored phases 2010/11
· Design phase
· Markup phase
· TYPO3 setup and FCEs
· T3O Week in Essen
· April 2011

10. T3O Week in Essen 04/12
· modelled after the T3UXW09
· 26 people
· 8 days
· 4 teams organised via Kanban
· 217 features BL
· 80% done

13. The Public Preview
· 833 tickets in Forge (655 done)
· 42 people from the community
· 2 code sprints
· September 2011 - 16 guys
· April 2012 - 10 guys

15. Launch at
2 nd of April 2012

17. Per Month
· 1.3m page views
· 200k returning visitors
· 154 countries
· 750GB traffic

18. Entry pages

20. Traffic distribution

21. Professional Service Listing
· Network of qualified Agencies
· Qualification Levels
· Active contributer
· Certified developers
· Proof of development knowledge
· Sponsorship

23. The Current Status
· 260 tickets in Forge
· 315 ideas via Uservoice
· QA process
· Some maintainers not available

24. The challenges
Technical Inside

25. Basics
· TYPO3 CMS 4.5
· 76 installed extensions
· >80% extensions from TER
· ajaxlogin, be_groups, cachecleaner, cacheinfo, cc_langguess, cc_softlink, cc_textcat,
comments, crawler, css_filelinks, cz_simple_cal, dam, dam_catedit, dam_filelinks, dam_index,
dam_ttcontent, dam_ttnews, dam_tv_connector, dependency,true docondemand, donation,
ed_damcatsort, ed_extbase, ed_gallery, ed_transliteration, ed_tv, extbase_dam, fed, geshilib,
js_css_optimizer, kb_tv_cont_slide, linkhandler, links, lowlevel_scheduler_task,
naw_single_signon, ods_facebook, pagebrowse, pagebrowse_tt_news, pastecode,
pdf_generator2, pmkshadowbox, powermail, purge, randfeuserlist, randombanners, realurl,
skip, solr, solr_redmine, static_info_tables, t3o_ajaxlogin, t3o_cla, t3o_userimage, t3org_base,
t3org_comments, t3org_configuration, t3org_feedparser, t3org_flickrfeed, t3org_template,
tabs4templavoila, templavoila, ter, ter_doc, ter_doc_docbook, ter_doc_html,
ter_doc_solrindexer, ter_doc_sxw, ter_fe2, ter_fe, ter_xsl, tika, tt_address, tt_news,
ttnews_irre, twittersearch, typo3_agencies, vimeo_connector
· ~6.000 lines of custom TypoScript

26. The infrastucture

27. Deployment Pipeline
Source: http://www.aoemedia.com/us/full-service/quality-assurance/continuous-deployment.html

28. Varnish
· Cache everything
· including Ajax responses
· send proper cache-control headers
· use smart purges
· EXT:cacheinfo / EXT:purge

29. Background Jobs
· Use the TYPO3 scheduler
· Introduce queue processing
· Frequency relates to the server load
· ~20 background jobs running

30. Search
· Systems included in the indexing process:
· TYPO3
· TER
· Redmine (a.k.a Forge)
· Documentation
· Forum (disabled)
· forge.typo3.org/projects/show/extension-solr

31. TER
· Existing TER migrated BUT:
· Rewritten TER frontent
· Asynchron manual rendering
· 10GB files +
· 10GB extension manuals

33. Upcoming Challenges
· Bugfixing
· Migrate towards a Git deployment workflow
· Migrate documentation to dedicated server
· Upgrade to TYPO3 CMS 6.0
· Migrate TER towards composer support
· More automated testing
· Enable Workspaces

34. Contribution
Get the community involved

35. Maintenance Concept (FOR)
· Most of the work will still be done by
volunteers
· If a volunteer needs to step back - the
agency will take over
· Agencies will backup the voluntary work
· Each FOR has an contact person
published at the FOR page at typo3.org
· http://typo3.org/projects/typo3-org/themaintenanceconcept/

36. The FORs
· Login and Registration
· Extension Repository TER
· Professional Services Listing
· News, Events, Articles, Security Bulletins
· Documentation
· Server, Deployment
· Search
· Video Integration
· Markup
· Donation

37. Goals
· Sub-pages (e.g. topic and team pages)
· Migrate other pages such as
· association.typo3.org
· shop.typo3.org
· buzz.typo3.org
· forum.typo3.org

38. Participation
· What to do when someone wants to help
out?
· What skillset is needed?
· What are possible takeaways for
newcomers?
· When could you support the team?

39. Try this at home!
· Install Vagrant (http://vagrantup.com/):
# gem install vagrant
· Import or Vagrant setup:
# git clone http://bit.ly/t3o-box
# cd Typo3Org
# vagrant up
· Download 800MB
· Start improving
· Send patches to the bugtracker!

40. Please
Get involved!