New TYPO3 Extension Repository
In the last sprint in Würzburg, the new TYPO3 Extension Repository (TER) website was initialized. On this sprint we optimized the local development, which is based on a Docker container
(requires a typo3.org login), and included the TER extensions for SOAP and frontend and a Solr server with the corresponding TYPO3 extension. Also, we integrated a design and started with the Solr indexer. We are using currently TYPO3 7.6 due to upgrading the extension on a facile way. We need to put more work into the extensions before upgrading to TYPO3 v8, so we shifted that to "after the go-live".
During the sprint, the TER team formed itself in person of Tomas Norre Mikkelsen, Thorsten Griebenow and Jonathan Iroulin. There will be weekly meetings within the team to keep the work on it.The next steps will be to get it running and fully tested on the subdomain, so we can go live within the first quarter of 2017. After that, we will refactor the extensions for TER and create a plan for getting the TER future-proof.
Everybody is welcome to join the team and contribute to get this most visited part of t3o. If you are interested, say hello to us on Slack
in the #ter-team
New typo3.org page
As we get the TER environment running in a stable way, we copied that information for setting up the new typo3.org page. After some evaluations, we decided to use the latest sprint release of TYPO3 v8. The design team in person of Oliver Oertel, Michel Loew and Fabian Stein joined us to improve and create the markup for the new site together with the integrators in person of Harry Glatz and Thorsten Griebenow.
Besides the work on the output of typo3.org, there was a productive and agile discussion on the menu and content structure. Marco Seiler, Ina Burkardt, Jörg Ems and Stefan Busemann sat together and formed the new page structure. It will be reduced in the first menu level to focus on the main areas which we want to provide.
Concerning the design, template and layout of the new typo3.org website, we decided to build a sitepackage with all required layout and content elements. This sitepackage (in form of an extension) will enable us to use it on most (maybe all) websites of the TYPO3 universe. We will use another "custom" sitepackage on each instance to overwrite the needed components like Typoscript, assets etc. This will reduce the amount of time for maintenance of the basics and will provide the same look and feel on all pages.
All this will be done hand in hand with the design team which will basically do all the HTML/CSS work. We hope that all elements - both for the frame and normal content - will be done until the next sprint and within the first quarter of 2017.
Anyone who is willing to join forces on this topic is invited to do so. Just get in contact with Thomas Löffler, Fabian Stein or Harry Glatz through Slack. We will provide you everything you need to contribute!
Page and content concept
The typo3.org relaunch will not only provide a new layout, but also take care of the content structure. We examined the page tree and aim to restructure it while reducing the navigation points on the first level.
One goal is to define an easy to retrieve place for the content of every page in the page tree. The second goal is to add useful crosslinks between typo3.org and typo3.com. On our way, we identified outdated pages and marked them to be removed.
Due to the lack of man power and an editorial team, we do our content restructuring work mainly on page level. Reworking the content on every single page should follow later and help is needed and welcome.
We created a complete timeline for our relaunch project. When we started the project last year, we planned to have only a new start page in fresh responsive design and have then a relaunch step by step. After we collected feedback in our community, we decided to have a full relaunch by end of June 2017. To reach this goal, we will have 3 additional sprints in the first half of this year. Also we will create tasks, which will be done between sprints. These tasks can be done by everyone who is willing to contribute.
To wrap it up: Main focus for the second quarter of 2016 is new typo3.org page, with a responsive design and cleaned up obsolete content and functions. In the second half of 2017, new functionalities will be implemented.