Official typo3.org news https://www.typo3.org/ en-gb TYPO3 News Sat, 17 Nov 2018 08:30:12 +0100 Sat, 17 Nov 2018 08:30:12 +0100 TYPO3 EXT:news news-1852 Wed, 14 Nov 2018 20:47:00 +0100 my.typo3.org becomes “my TYPO3” https://typo3.org/article/mytypo3org-becomes-my-typo3/ You probably already know my.typo3.org as the site to register your typo3.org user account. But an exciting change is coming–my.typo3.org will become an important space for our community. Read on to find out what we are planning. Contribution is the lifeblood for a community. The more and better quality contributions we have, the more our products and community can develop. So we are looking for new ways to increase the contribution base and provide benefits for contributors.

Here are some of the new planned features for my.typo3.org:

Personal Profile Page

Each user on my.typo3.org will have the option to complete their own personal profile page. The user can choose what information they’d like to show different types of profile page visitor. There are three different options:

  • Public: the property is shown to anyone who visits your profile (no login required)
  • Community: the property is shown to everyone who is a part of the TYPO3 community and is logged into my.typo3.org
  • Teams: the property is only shown to the teams you are a part of

As an example, you could decide to share your phone number only to teammates, but a small “about me” text to everyone. To give you control, the profile page is disabled by default.

Karma Level

We wanted to visualize “contribution” and decided a great way to do this would be to introduce a “Karma level”. Anyone who contributes to an official team or committee can earn themselves “Karma points”. You can also decide to display your contributions and points on your personal user profile, so the public can see what a dedicated contributor you are! 

If you are an employee of a company that is a member of the TYPO3 Association, you can also link your user profile with your company profile.

Company Member Profiles

At the moment our member listing is pretty basic and more hidden than we’d like. We plan to rework the member listing and company profiles for all company members with the status silver level or higher. These profiles will have the bonus option to add a small company description, product and service offerings as well as their contribution level. We also plan to show the extensions that companies or individual members are currently maintaining.

Companies can connect their profile with user profiles of typo3.org users. These connections will populate page properties such as “number of certified developers”, “employees with typo3.org user profiles” or the accumulated karma level.

The member listing will add the “Karma level” as an integrated ordering item next to the membership level. This means the most dedicated members will appear higher in the listing and have their profile featured on additional pages on typo3.org.

Further Steps

We still have even more ideas and also concrete plans for later development:

  • Team organization: we want to support our teams with services to make their tasks easier. It should become easier to send out mailings to team members, organize meetings and visualize team status.
  • Community services: we will introduce a self-service area for the entire community. Here you will be able to set up your invoice address, plus view or download all invoices you have received (e.g. for official events, certifications etc.)

Contribute

We plan to introduce these functions in the first quarter of 2019. If you like to contribute, join your Slack channel #t3o-team

Your Feedback

What do think about our plans? Go ahead and leave a comment, we are excited to hear your opinions.
 

]]>
Community
news-1851 Fri, 09 Nov 2018 09:33:41 +0100 Budget Ideas for 2019 https://typo3.org/project/association/funding-finances/budget-2019/ The Budget Committee of the TYPO3 Association is preparing the next year’s budget. We are presenting you, the budget idea collection Association news-1850 Tue, 06 Nov 2018 18:02:41 +0100 Report from TYPO3-Sprint Berlin 25.-28.10. https://typo3.org/article/report-from-typo3-sprint-berlin-25-2810/ In a Berlin backyard, near the former Wall, in the last corner of the former West, something as intangible as the TYPO3-Core suddenly became alive: In the form of about 15 people gathering for a sprint. Their common goal: to make a good project even better - take the TYPO3 core one small step further. I'm one of three “newbies“ taking part in such a four-day endeavour for the first time. Of course all of us have built numerous TYPO3-Installations, are experienced in working with git, and have even now and then had a look into the code of the core - but none of us ever contributed directly to the central piece of TYPO3.

Thinking about what lies ahead, my head spins: Whatever we changed in these days would eventually be played out on more than 500,000 installations worldwide. Better be careful with whatever we do!

But first of all, our friendly hosts from the agency “undkonsorten“ catered for a good atmosphere: coffee and drinks, bread and spread, and fruit and vegetables are awaiting us in the kitchen. In a large workroom, a huge table offers enough space for everyone. Straight after arrival, everyone moves in behind their computers and begins to work.
Our task schedule can be viewed on forger.typo3.org. There  the pending tickets are pre-sorted, waiting for us to tackle them. As expected - three weeks after the release of version 9.5 - the priority is on bug fixing.

At the beginning, an experienced mentor takes us newbies aside, and we practice the correct workflow. As soon as everything is clear, we jump right in at the deep end. The first thing to start with is to review existing patches.

This turns out to be surprisingly time-consuming. We always start with a ticket that reports an error and for which a patch has already been written. Our first task is to reproduce the bug in the current version 9.5.0. Once we have done that, we apply the patch and then re-check whether the bug has now been fixed. If we can confirm this, the patch gets a "+1". Four of these ratings are required before a core member can merge it into the current code.

As the days go by, we become faster and faster, and soon even we newbies are busy not only reviewing existing patches, but also writing new ones.

We immediately notice how much responsibility comes with it: Is it really allowed to delete this line with " ", which the RTE produces under certain circumstances? Doesn't it break the frontend in some installations? It's reassuring to have core team members at the table who can answer such questions: You may, you even should - because this line is a historical remnant and should be removed anyway.

While working we can finally close some 15 year old tickets. Especially with the old tickets, often just checking turns out to be sufficient: No, the bugs reported there no longer exist in versions 8.7 and 9.5. Not because they have got fixed, but because the code has become cleaner and more sophisticated over the time. And clean code doesn't produce these bugs in the first place.
Some tickets are quite simple, others surprisingly difficult. Some require a longer discussion, others have even to be postponed because they raise difficult conceptual questions that need to be put back for the time being.

Most of these discussions take place in the kitchen; it becomes a meeting place where the big questions of TYPO3 and the small ones of everyday life are discussed. By the fourth day at the latest, it feels like everyone is living together in a big shared flat.

132 closed tickets finally go into version 9.5.1. A large part of it has been done in the four days in Berlin. We had a lot of fun, laughed a lot together, and still worked intensely. When I left, I understood well why so many sprint participants keep coming back. I'm sure I'll be back at some point, too
 

]]>
Development TYPO3 CMS
news-1847 Wed, 31 Oct 2018 16:30:00 +0100 This Month in TYPO3 - October 2018 - Issue #7 https://typo3.org/project/news/this-month-in-typo3/this-month-in-typo3-october-2018-issue-7/ October was mainly dominated by the release of TYPO3 v9 LTS. A lot of extensions are already compatible with v9 and also the first projects have been updated or freshly created. Community news-1845 Tue, 30 Oct 2018 12:00:00 +0100 TYPO3 v9.5.1 LTS and v8.7.20 LTS released https://typo3.org/article/typo3-v951-lts-and-v8720-lts-released/ The TYPO3 Community announces versions 9.5.1 LTS and 8.7.20 LTS of the TYPO3 Enterprise Content Management System. We are announcing the releases of TYPO3 v9.5.1 LTS and v8.7.20 LTS, as scheduled.

These versions are a maintenance releases and contain bug fixes only.
For details about the releases, please visit the following websites:

Download

Find the packages under https://get.typo3.org/

]]>
Development TYPO3 CMS
news-1846 Tue, 30 Oct 2018 11:57:46 +0100 T3CON Membership Upgrade Campaign https://typo3.org/article/t3con-membership-upgrade-campaign/ Upgrading has never been easier. Join the special TYPO3 Association membership upgrade campaign starting at T3CON and receive special awards. Start now and

upgrade your membership

This campaign ends at the end of December. Read more about TYPO3 Association memberships or become a member.

Upgrading to 

Bronze

Silver

Gold

Platinum

Pin and ribbon with stars

Possibility to win a free tete-a-tete dinner with the President1

 

Honorable mention in an upgrade campaign-related association tweet and article at typo3.org

 

Extra €200 event vouchers2

 

 

1

2

Possibility to win a free booth at a TYPO3 event of your choosing2

 

 

Free tete-a-tete dinner with the President for up to two people3

 

 

 

 
1 For you or one other person from your company in connection with an event where you and the President are both present within 12 months.
2 Valid for 12 months.
3 The people must be from your company. Valid for 12 month.

]]>
Community Association
news-1827 Mon, 22 Oct 2018 16:10:56 +0200 What are People Saying About TYPO3 v9 LTS? https://typo3.org/article/what-are-people-saying-about-typo3-v9-lts/ Have you cracked open the latest TYPO3 v9 LTS yet? We really felt the spirit of the community on release day as people responded with thanks and recognition to the core team who worked so hard on this release. Community news-1823 Tue, 02 Oct 2018 11:00:00 +0200 TYPO3 v9 LTS - You’re the One That I Want https://typo3.org/article/typo3-v9-lts-youre-the-one-that-i-want/ Today, after 1.5 years of dedicated work and meeting the self-set goal of publishing five intermediate Sprint Releases as scheduled, we are now proud to announce that the new major version TYPO3 v9 LTS is available for download. Development news-1825 Tue, 02 Oct 2018 10:59:00 +0200 TYPO3 v9 LTS Press Release — in Many Languages https://typo3.org/project/press/press-releases/v9-lts/english/ The official TYPO3 Association and Company press release is out. Read it in your own language and start spreading the news. Association Press news-1824 Mon, 01 Oct 2018 21:10:00 +0200 This Month in TYPO3 - September 2018 - Issue #6 https://typo3.org/project/news/this-month-in-typo3/this-month-in-typo3-september-2018-issue-6/ The September edition is rather brief since everybody is busy preparing for the upcoming release of TYPO3 9 LTS, either by contributing to the TYPO3 core, updating extensions to be compatible with TYPO3 9.5 or organizing a release party. Community news-1822 Tue, 25 Sep 2018 11:29:02 +0200 Events Committee: call for participation https://typo3.org/article/events-committee-call-for-participation/ One of the tasks of the TYPO3 Association is to organize events for our community. Currently we organize the TYPO3 Developer Days, T3CON, Certifuncation and the Snowboard tour. These events are organized by different groups of enthusiastic people from the community, and as Association we support that. The first quarter of this year we interviewed many people from the community who are involved with the organisation of TYPO3 events. From these talks we deduced that there is a need for optimizing the process of organizing events.

That’s why we are looking for committee members. We are aiming for a 4 member committee of volunteers who are interested and in a way experienced in process optimization and/or events organization. Interested? Than read on!

Why we are doing this

Basically every event is identical. Only the goal, culture and ambiance are different. With the work from the Event Committee we aim to make the organization of events less time consuming so that more people are willing to help organizing an event. Also, with the work of the Event Committee we hope to prevent frustrating mistakes.

The TYPO3 Events Committee

At present the TYPO3 Events Committee is in reengineering mode. Board members of the TYPO3 Association have taken the task to kickstart this Committee again.

With the 4 people that form the new Events Committee, we won’t be organizing events, only facilitating and optimizing the organization of events. It creates and maintains the runbook, the selection of event partners, and works towards benchmarks of costs, all in the aim of simplifying the organisation of successful events.

First point of Contact (SPoC) in the Association for the Events Committee is the Vice President: Ric van Westhreenen. 

Interested to join?

If you want to become one of the 4 members of the Event Committee, like to optimize processes, and work towards the ingredients for a successful events cookbook, please contact us by writing an e-mail to Ric van Westhreenen. 

join now

]]>
Association
news-1821 Thu, 13 Sep 2018 22:17:00 +0200 Call for budget application ideas - TYPO3 Association Budget 2019 https://typo3.org/article/call-for-budget-application-ideas-typo3-association-budget-2019/ The Expert Advisory Board (EAB) presents the available funds and asks the TYPO3 community to submit their ideas for the 2019 TYPO3 Association budget. Total Funds available for 2019

In coordination with the Treasurer of the TYPO3 Association, the EAB is releasing the available budget sum for 2019. By releasing the budget amount earlier than in previous years we want to increase transparency, put the application process in a realistic context and encourage applicants to apply for the funds available.

Total Funds available for 2019: €900,000

Please consider this amount a forecast - it may change according to the actual financial situation.

Distribution of Funds

As explained earlier, the funds will be distributed among 3 pools:

Innovation, Education and Events Pool

Budgeted amount: €250,000

For this pool, we have a transparent two-step application process. The first step is for the TYPO3 community members to submit their ideas via the short form below. We have made the process so simple that it should not take an applicant longer than 15 minutes to contribute their idea.

Ideas can be submitted from now until 14th October 2018:
Submit your budget application idea

For the second step, the ideas will be put forward for rating in the Association member poll before a final strategic selection is made by the EAB. The selected ideas will be eligible for a budget application submission.

Development Pool

Budgeted amount: €350,000 (according to GA 2016 and 2017)

This pool is available for the TYPO3 core team to fund development and product marketing initiatives. It is managed on behalf of the core team by TYPO3 GmbH. Applications for funding need to be submitted to TYPO3 GmbH.

TYPO3 GmbH is responsible for the management of this budget via their own accountability structure. By making this budget pool available, the TYPO3 Association remains the largest single funder of the initiatives of the TYPO3 core team and thus contributes heavily to the further development of the TYPO3 CMS product.

Infrastructure Pool

Budgeted amount: €300,000

This pool is available for the TYPO3 Association board to fund operational and infrastructure work. It includes budget positions for contracts with vendors and regular service providers (e.g. data center for hosting, legal assistance), coverage of travel expenses and work time expenses for maintenance costs. New for 2018 will be that all travel expenses from the infrastructure pool will be paid out of a central pot that is the responsibility of the Association president. The advantage of this is that travel costs can be streamlined and leftover budget identified more easily throughout the year.

There is one combined budget application for this infrastructure pool.

Member Involvement

The members of the TYPO3 Association stay involved in the budget process. The following opportunities exist to contribute and give feedback:

Member Poll

In October, the EAB will ask its members to rate the ideas submitted to the Innovation, Education and Events Pool and to give feedback to the distribution of funds in the other two pools. The EAB will take the results of the member poll into consideration for the finalization of the 2019 Association budget and strategy.

Submission of Ideas

The submission of ideas to the Innovation, Education and Events pool is open to everyone and we would like to encourage the TYPO3 Association members to play an active role here. We have a larger budget amount available than in earlier years for strategic positioning of TYPO3, and this is a unique chance to contribute.

Questions

The EAB remains available by email to answer your questions and will publish a consolidated FAQ should the need arise.

Contact the EAB: eab(at)typo3.org

Budget Committee

We will start now, to set up a budget committee, which will be responsible to do the whole budget process (initiate, evaluate ideas, check budgets during the year.). The committee will be lead by one member of the Board of the TYPO3 Assocation. Any member who likes to be part of the committee can apply via mail  eab(at)typo3.org.

Summary

The budget process for the 2019 Association budget is now launched. We are looking forward to receiving your ideas and feedback.

]]>
Association
news-1820 Fri, 07 Sep 2018 12:50:00 +0200 This Month in TYPO3 - August 2018 - Issue #5 https://typo3.org/project/news/this-month-in-typo3/this-month-in-typo3-august-2018-issue-5/ With a slight delay here is the recap of what happened in August in the TYPO3 universe. Despite summer vacation season really a lot has happened! Happy reading! Community news-1819 Fri, 07 Sep 2018 11:57:31 +0200 Want to Improve TYPO3? Join a Community Team. https://typo3.org/article/want-to-improve-typo3-join-a-community-team/ TYPO3 is built through the contributions of volunteers. Want to get involved? Find out what skills are needed, what’s happening right now, and who to contact. Thank you to the TYPO3 Community Team Leads for helping out with this article on top of everything they do for the project and community.

The community contribution section here on TYPO3.org is the hub for everything related to community events and TYPO3 CMS improvements. No matter your prior experience and interests, you can find a way to share your skills where they’re needed most.

The easiest way to do that is by finding a team of people to work with. Bonus: Research suggests the social recognition you get will help keep you motivated.

What Motivates Open Source Contribution?

In some ways you know it’s right to contribute to open source, but you might feel inhibited to start. You’re not alone. Researchers found patterns in the barriers that prevent newcomers from contributing, and perhaps you can relate. Most people who stay away from contribution do so because they don’t have time: it takes away from earning money, they have limited skills and knowledge, or they have trouble setting up an appropriate development environment.

Researchers found that open source contributors were more motivated to contribute when the process was clear, when they would get a “feel good factor” or improve their reputation, and most importantly, when they needed those fixes themselves, as soon as possible.

Volker Neuenhaus of Pagemachine AG is lead on the TYPO3 Design Team. Volker tells me that he enjoys the social side of contribution. “Both me personally and our company benefit from getting to know interesting people when working with teams or visiting events.” And of course, as he said, the better TYPO3 gets with contribution, “the better it is for everyone.”  

Researchers also found that individuals were more likely to contribute code to open source projects when they focused on the benefits of improving their professional reputation and self-development. That’s why contributors get shout-outs for their ongoing involvement in  monthly “Developer Appreciation Day” posts on typo3.com.

Stefan Busemann, of in2code GmbH, and product owner of the typo3.org Team, echoed the findings about self-development. He said to keep people motivated, “the most important thing is a good spirit, and also that people should profit from their work–earned reputation and also skills, especially for technologies they don’t know so far.” Stefan said there are many ways he personally benefits from contribution. “I learn a lot from other people. In all the projects I am involved in I have found new friends and I built up a personal network where I can receive help; My business also benefits from the positive image we create with our contributions.”

If code contributors are motivated by personal development, on the other hand, the same researchers found those contributing documentation were motivated by altruism. Want to make yourself feel good? Contribute to documentation!

And now’s your chance, as the the Documentation Team is asking the community to step up and get involved. Martin Bless, certified TYPO3 integrator and Documentation Team Lead told me, “We just had the second ever T3DocTeam sprint in July 2018, the previous one was in 2014.” They’ve grown the team too, “After being more or less only one person in the ‘team’ we are now three.” Like most of the TYPO3 community, they prefer to meet via Slack and they’ve moved away from email because “it doesn't work well and is too time consuming.”

Right now they are focused on getting the word out to inspire people to get involved. Martin said “Our first task is to elaborate on our mission statement in our team document.” They are open to new ideas too. “If somebody wants to come up with a ‘meta issue’ about TYPO3 documentation, feel free to do that as an issue in our team document.”

The best way to validate your professional reputation and gain the feel-good factor of altruism is by connecting to others, and that’s where teams come in.

Why Getting Involved in a Team Will Help

Four ways to contribute to TYPO3 include writing code for and testing TYPO3 core or extensions, writing documentation, and supporting other users online. Yet if you look at a list of open issues, it may be hard to see where to start.

Like other open source CMS communities, TYPO3 contribution is organized into teams. By dividing the big project down into smaller groups, people can work together to motivate each other. “There is nothing like a magic trick” to get people involved says Volker. He tends to ignore it when people don’t respond and instead keeps the door open, making sure to keep asking people to get involved.

Browse the list of community teams here to find where you can contribute the most.

There are ten teams working together to improve TYPO3 CMS, from teams like the Development, Design and Documentation teams, to teams that grow the audience such as the Academic and Content teams. Community team members are tapped right into the centre of each initiative and can quickly guide you where to start.

TYPO3 Contribution Teams

Each team coordinates online meetings, in-person events, and sprints. Check out meet the community to discover more and find the community team you think you can contribute to most.

TYPO3 Development 

This team is dedicated to developing and maintaining the central parts of TYPO3 CMS. They recently welcomed new Core Team Members!

Right now: The Core Team is getting ready for TYPO3 CMS v9.5 LTS release on 2 Oct. 2018. Meanwhile, they are reorganizing the contribution workflow to define the goals and make it easier for new contributors to get involved.

What’s next? TYPO3 Core Code Sprint Berlin: Berlin, Germany, 25–28 October 2018

Design

The Design Team is responsible for the branding, design, and visual communication of TYPO3 CMS (not for the design of the CMS itself!)

Right now: Do you have design skills? They would love to grow the team so it’s a great time to get involved. They just had a Design Team sprint in August.

What’s next? Keep an eye out for sprints listed in the community events calendar.

Documentation

The Documentation Team provides exhaustive, quality documentation about TYPO3 products for all users, with the help of the community.

Right now: It’s easy to get involved. Most pages say "Edit me on GitHub" so you can use a pull request or GitHub issue. Follow this tutorial on how to contribute to docs.typo3.org (video 4:32)  

What’s next? Best way to keep in touch is the #typo3-documentation Slack channel.

Education & Certification 

The committee is responsible for the TYPO3 education strategy, enabling easy access to learning materials, as well as official certifications.

What’s next? Follow @typo3education for updates.

Content 

The Content Team work on blog posts like this one. We need your help to write, translate, and proofread content. No coding skills are required. You can support us on a regular basis or when you have time.

Right now? Contact Mathias Bolt Lesniak directly to get involved.

Also related: Communication Coordination Committee. The Committee coordinates the communication and marketing of the TYPO3 GmbH and the TYPO3 Association, through a unified workflow and production pipeline.

Security

Security is taken very seriously by the developers of TYPO3. The TYPO3 Security Team handles incidents and responds according to strict rules to keep TYPO3 as secure as possible.

Server Administration

The TYPO3 Server Administration Team maintains the server infrastructure of the TYPO3 project. They also administer several central services and websites.

Right now? They are looking for people with experience and interest in configuration management or monitoring who can join bi-weekly online meetings.

What’s next? Follow @TYPO3server on Twitter.

TYPO3.org 

The TYPO3.org Team develops and maintains the TYPO3.org website, the Extension Repository, Events and Certification Listings, and much more.

Right now? The bottleneck is frontend developers, especially those who are able to adapt an existing design and add new functionality.

What’s next? Sign up for the TYPO3.org sprint Sept. 12–14 in Rosenheim, Germany. Join the Slack channel #t3o-development to keep in touch.

Academic 

The TYPO3 Academic Committee is made up of TYPO3 Association members from universities that use TYPO3 CMS for their homepages.

What’s next? TYPO3 University Day 2018 in Mainz, Germany on 25–26 September. Use the hashtag  #T3UD18 to follow updates.

Ready to get Started?

To get involved in contribution you will need three things:

Once you start contributing it’s easy, and if you’re stuck on where to get started, come into TYPO3 Slack and talk with the community.

]]>
Community
news-1818 Tue, 04 Sep 2018 14:00:00 +0200 TYPO3 v9.4.0 released https://typo3.org/article/typo3-v940-released/ One small step for a Sprint Release, but one giant leap towards the new LTS version! Today, we are excited to announce the release of TYPO3 version 9.4, which is the last planned Sprint Release before the Long Term Support (LTS) release. Development news-1817 Thu, 23 Aug 2018 14:16:52 +0200 Our Journey from India to T3DD18 in Germany https://typo3.org/article/our-journey-from-india-to-t3dd18-in-germany/ The TYPO3 Developer Days 2018 (T3DD18) in Dusseldorf, Germany, drew over 200 eager TYPO3 developers from around the globe. They came to trade knowledge, explore TYPO3, and to grow the TYPO3 community. With a lot of excitement, we flew from Bhavnagar India and to Dusseldorf, Germany. It was a journey of 6000+ km distance between India and Germany, and more than 20 hours of travelling. 

Being the part of the community for more than four years, it was our very first live TYPO3 event. The amazing days of the event became a memory to cherish for life. When we weren’t focusing on TYPO3, we joined the karaoke and hung out together to strengthen our friendships within the TYPO3 community.

]]>
Community
news-1816 Tue, 21 Aug 2018 10:30:00 +0200 TYPO3 v8.7.19 LTS released https://typo3.org/article/typo3-v8719-lts-released/ The TYPO3 Community announces version 8.7.19 LTS of the TYPO3 Enterprise Content Management System. We are announcing the release of TYPO3 v8.7.19 LTS, as scheduled.

This version is a maintenance releases and contains bug fixes only.

For details about the release, please visit the following website:

https://get.typo3.org/release-notes/8.7.19

Download

Find the packages under https://get.typo3.org/

]]>
Development TYPO3 CMS
news-1815 Mon, 20 Aug 2018 14:07:29 +0200 Recap: TYPO3 GmbH Review Fridays July and August 2018 https://typo3.org/article/recap-typo3-gmbh-review-fridays-july-and-august-2018/ As usual, the TYPO3 GmbH office opened its doors for interested developers for a day of tackling the review queue. It’s becoming an institution, and we were very happy to have Netherlands guest to both dates. On 6th of July, WIND Internet sent us three of their developers, a big shoutout goes to Jord de Jong, Rudy Gnodde and Robert van Kammen. Jürgen Venne from Schaffrath completed the little crowd.

Together, we made 15 patches ready to be merged into the master branch of the TYPO3 core. They contained mostly smaller sized changes and paved the path for bigger changes, that the core team members are preparing.

Don’t underestimate the power and value of cleanup patches or documentation improvements, those are badly needed both by users of TYPO3 as well as developers who build on this base. So even if we did not tackle the big brand new features, this work was necessary and precious. More of the same had been prepared during the day, which was merged later, and also the backports to the stable branches are not counted here.

We concluded our workday with a visit to the local beer garden, where we had dinner and some time to talk and catch up with each other. This time is as important as the working time, as it allows us to connect over our shared passion: TYPO3.

Thank you Rudy, Robert, Jürgen and Jord for this effective Review Friday. I look forward to welcome you again in the TYPO3 GmbH office for more of the same.

The August issue of Review Friday was shifted to the second week of the month, due to the Code Sprint that took place in Dresden the week before. This time, the office was almost too small for all the participants: Mona Muzaffar came from Rheinschafe, again Jürgen from Schaffrath, the new employee of TYPO3 Gmbh Benjamin Kott, Tim Schreiner from arndtteunissen and Riny van Tiggelen, Richard Vollebregt and Richard Haeser from MaxServ.

Richard and his colleagues came to discuss and work on the SEO integration features they prepare for TYPO3. Read about their experience on Richard’s Blog Post.

Jürgen also had his own agenda and preferred the protected space in the TYPO3 GmbH office over his own workspace, to advance on the File List rework.

So it was left to Tim, Mona, me and later on also to Richard and Riny to get the count of open reviews down. 10 patches were merged to master, and lots of advancement was made especially on older issues. To unblock work on such patches, rebasing the current code and taking up conversation with the people involved is a time consuming, but rewarding work. There is an undeniable feeling of satisfaction, when one can resume work on an issue that has been abandoned for some time.

This time, we took the dinner to the Altstadt, where we had a nice late meal near the river Rhine. When Mathias Schreiber also joined us for the evening, it was a perfect conclusion for a day full of talk, little and bigger successes on the code zone of TYPO3. We kept talking and sharing stories until deep into the night.

I also want to thank all the people that put up with our activity during the review fridays and supported us by also contributing remotely. We would not have been able to tackle so many issues without help from the rest of the community.

Do you think you can do what we do each month? Reviewing patches, giving feedback, fixing bugs, filing tickets and such activities? We are glad you see you join on the next event, which will take place September 7th in Düsseldorf. If this is too far away for you to travel, just meet us remotely in Slack. We will be there all day, starting 9am and as long as someone still wants to continue.

If you wish to come to the office, please just do so. Bring your laptop, everything else (wifi, food, coffee, energy drinks, beverages, sweets and energy plugs) will be provided. A little hint on Facebook or Slack is appreciated, but not mandatory.

Let’s have fun together, making the world - at least our little TYPO3 one - better by removing as many bugs as we can, and spend time connecting over our favorite CMS.

We look forward meeting you!

Yours, Anja

Next TYPO3 GmbH Review Friday: September 7th
Also, did you know there's a Code Sprint in Berlin coming up at the end of October? Register here now!

]]>
Development Community TYPO3 CMS
news-1814 Tue, 14 Aug 2018 08:14:05 +0200 Report of the QSA 3-2018 https://typo3.org/article/report-of-the-qsa-3-2018/ Report from the Board meeting in Düsseldorf, Germany, 21st–22nd June 2018. Our quarterly summit of the TYPO3 Association (QSA) took place during Developer Days. We met in the Headquarter of the TYPO3 GmbH and used this opportunity to get in touch with our community and of course - meet all employes of the TYPO3 GmbH. This meeting was held as a working sprint. We set up smaller working groups, to create concrete results.

As usual we started with a short recap of our activities of the last month and compared the progress with our project plan (https://typo3.org/project/association/association-projects/). Then we split up in different working groups. 

Initiate an events committee

In the past we had an events committee, which organized official events of the TYPO3 Association. We think it is helpful to reintroduce that committee, but shift the focus of their work. They should be responsible to coordinate all official events and setup the general infrastructure (like a general ticketing system). Further they should coordinate and integrate the collaboration with the TYPO3 company. 

The committee ensures that each official event has a working organizingteam and an operations manual. At the moment many events are “reinvented” every year. 

Ric von Westhreenen is your contact person, if you would like to contribute, or if you have further questions.

Contribution appreciation

Peter Kraume kickstarted the idea to provide better Contribution appreciation. We want to make the work of so many people more visible, and look for ideas for the best ways to show our appreciation.

At the moment we are collecting ideas, discuss questions like:
peer to peer appreciation vs. institutionalized recognition
that people have different conceptions on the ways to get gratitude, e.g. they don’t want to appear on stage
that appreciation must be authentic

More communication toward both T3A members and general TYPO3 audience
THIS MONTH IN TYPO3 NEWS: a project has been set up by Peter Kraume for this periodical news intended to be published on the typo3.org web site. Tools for gathering and selecting information for the news have been defined and on their way to be set up. We need to find people who want take over this task and run it regularly. We will probably have the launch of this new communication activity some months before the scheduled deadline

GDPR Working group

Our working group checked, the results of the introduction of our new processes and documented the new processes. Since May 2018 Karen Falkenberg is our data privacy officer and does take care of all data privacy requests. 

Membership management and typo3.org integration

Stefan Busemann and Anja Leichsenring finished a concept to introduce a self service area for members and further typo3.org integration. It will be possible to improve our member and certification listing by using a unified data source. 

The implementation of these integrations will start in autumn.

TYPO3 GmbH Supervisory Board Meeting 

The supervisory Board of the TYPO3 company used the chance and held its meeting in the headquarters. Together with the Board new proceedings were introduced, which clarify responsibilities. Alain Veuve stepped back from the Supervisory Board, as he is involved in operations. His successor is Ric van Westhreenen.

Marketplace

The project is making progress. Boris Hinzer presented a frontend design for desktop, tablet and phone. The integration of designs has started. At the moment tax questions are open.

TYPO3 less technical 

Petra Hasenau is looking for ways to promote TYPO3 less technically. We could try to view not only “TYPO3” as a product, but also its value, spirit, history: Where do we come from? What were the ideas in the past (we like to be the rebels)? The next steps are to gather more information and talk to people (inside and outside of the TYPO3 community)

Budget management

Since this budget period, we are fostering the usage of our reimbursement tool. This tool was introduced some years ago mainly for the CMS team. As it provides a lot of benefits for budget owners and users, we want improve this service. We defined user stories for further development and documented the whole process.

TYPO3 house

Last but not least, we discussed the TYPO3 house idea again. We could have a central place, to meet, work, sleep. The advantage could be that we would have always a location for sprints and all TYPO3 activities. But we would be bound to one location. So we collected further ideas, like having a plane (we need more members for this idea), a ship or for the beginning regular open sprints (where different teams can join freely, work on their agenda, but also use the chance to interact with other teams). The last idea will be tested in the next year. 

Outlook and project overview

Our next meeting will take place in October before the T3CON in Berlin. If you are interessed, to see all our projects or if you like to contribute, check out our projects page.

]]>
Association
news-1813 Tue, 14 Aug 2018 08:07:43 +0200 Supervisory Board Report 1st & 2nd Quarter of 2018 https://typo3.org/article/supervisory-board-report-1st-2nd-quarter-of-2018/ The supervisory board of the TYPO3 service company (TYPO3 GmbH) reports about the activities in the first half of 2018. The Supervisory Board met next to the Developer Days at the 21st of June in Düsseldorf. We can look back to the first full year of operations of our company. Overall the start was very successful. Instead of creating a (planned) loss, we were able to create a small profit.

A team around Mathias Schreiber is set up and runs stable. The company was mainly focussed on setting up processes, finding the right employees and partners and, of course, creating new offerings. 

Supervisory Board Changes

Alain Veuve steps back from his position in the supervisory Board. He wants to be more active in operative work of TYPO3 GmbH and this would lead to conflict of interests. The Board of TYPO3 Association decided to call Ric van Westhreenen into the Supervisory Board. We like to thank Alain for his work on the Board.

New proceedings for the Supervisory Board were introduced by the Board of the TYPO3 Association. Clear rules define now how often the supervisory Board meets, and when and to whom to report. 

Report of activities in TYPO3 GmbH

We can report many activities in our company:

Community & Events

  • Closed reevaluation of Academic Committee collaboration
  • Live-stream of first T3C Dresden (26-27 January 2018)
  • Live-Stream of T3C Venlo (9-10 March 2018)
  • Attended Google CMS Summit  and represented TYPO3 (15.03.18)
  • Attended Erasmus+ Meetings
  • Attended the TYPO3 Communication Coordination Committee (T3C3) meetings
  • Supported T3DD18

Internal Processes

  • Improved CRM facade
  • Improved case studies on typo3.com
  • Set up own DNS infrastructure

Products

  • Education Package started
  • Completed Project Reviews
  • Created a new product:  In-House Certification
  • Started collaboration with DRUD
  • Created 50+ Blogposts
  • Created 30+ videos

 
Development 

  • Held code sprint Frankfurt
  • Held code sprint in Padua
  • Hosted education sprint
  • Hosted trainer network sprint

Financial Situation

We have preliminarily closed 2017 with a small revenue and will be profitable at a low level. The closing of books is expected to be finished soon. 

In our business plan we targeted EUR 767k for the 2nd 12 months of operations of the TYPO3 GmbH. In this period from 1 January to 31 May 2018, TYPO3 GmbH generated revenues of at least EUR 968k. Financial results for the same period show a loss of EUR 39 k.  On the spending side, the TYPO3 GmbH was able to fund as much work and initiatives as ever before, resulting in a lot lower spending by the TYPO3 Association. 

Given this, the TYPO3 GmbH is on track financially. However, the 3rd year of operations comes with the challenge of reaching revenue of EUR 2.2 M. 

Outlook

In the next months the TYPO3 GmbH will focus on organizing some of the official events. 

  • Organizing “TYPO3 University Day 2018”
  • Organizing “TYPO3 Developer Days 2019”
  • Organizing T3CON18
  • Organizing “TYPO3 Award 2018”
  • Google AdWords extension
  • Increase partners
  • Increase sales
  • Move mailservers

The next report should be expected towards the end of October, 2018.

]]>
Association
news-1812 Tue, 14 Aug 2018 07:46:50 +0200 Report on the typo3.org Team Sprint in Düsseldorf (Jun 2018) https://typo3.org/article/report-on-the-typo3org-team-sprint-in-duesseldorf-jun-2018/ From 19th to 24th of July our team met in Düsseldorf, next to the TYPO3 Developer Days. Our focus for the sprint mainly bugfixing and introduce necessary GDPR functions.  

Next steps

Our next sprint in September will focus at my.typo3.org. We want add personal profile pages and introduce unified data listings (members, certifications) at typo3.org.

Participants of the sprint

Thomas Löffler, Stefan Busemann, Harry Glatz, Boris Schauer, Marcus Schwemer, Ryan Klarhölter, Sanjay Chuahan, Keval Pandya, Andreas Nedbal, Miro Olma

]]>
Community
news-1811 Tue, 31 Jul 2018 11:00:00 +0200 TYPO3 9.3.3, 8.7.18 and 7.6.31 released https://typo3.org/article/typo3-933-8718-and-7631-released/ The TYPO3 Community announces the versions 9.3.3, 8.7.18 LTS and 7.6.31 LTS of the TYPO3 Enterprise Content Management System. We are announcing the release of the following TYPO3 updates:

All versions are maintenance releases and contain improvements only.

Recent TYPO3 versions unfortunately introduced some regressions with the previous security releases which were:

#85547 Avoid PHP warning when using Phar archive with open_basedir (fixed in 9.3.3, 8.7.18, 7.6.31)
#85570 Allow form definitions to be moved or put to recycle folder (fixed in 9.3.3, 8.7.18)
#85608 Allow "defaultValue" for select form elements (fixed in 9.3.3, 8.7.18)
#85544 The form upgrade wizard must update all plugin settings (fixed in 9.3.3, 8.7.18)
#85426 Declare middleware dependencies of redirects (fixed in 9.3.3)
#85252 Avoid SQL error in indexed search administration (fixed in 9.3.3)

The previously released upgrade wizard "Rename form definition file extension from .yaml to .form.yaml" did not migrate custom finisher settings defined in content elements. Thus and in case system extension form is used, the mentioned upgrade wizard has to be executed again in order to migrate the remaining settings as well. More information about the migration path in general has been mentioned in TYPO3-CORE-SA-2018-003.

We are sorry for any inconveniences these regressions might have caused.

Download

TYPO3 can be installed in various ways. For example the traditional way by using the source package at get.typo3.org or the modern way by setting up a project using composer, to name just two. Further details can be found in the according release notes:

]]>
Development TYPO3 CMS
news-1799 Fri, 27 Jul 2018 13:40:00 +0200 This Month in TYPO3 - July 2018 - Issue #4 https://typo3.org/project/news/this-month-in-typo3/this-month-in-typo3-july-2018-issue-4/ The highlight event of July certainly was the CertiFUNcation Day. But there are also many other noteworthy things happening in the TYPO3 community. Happy reading! Community news-1798 Wed, 25 Jul 2018 12:49:40 +0200 A new structure for the TYPO3 Core team https://typo3.org/article/a-new-structure-for-the-typo3-core-team/ The TYPO3 Core Team started a restructuring process led by Oliver Hader and me. Over the following weeks working modes, processes and current requirements will be evaluated and ultimately result in a new and more sustainable team structure with an efficient working mode. Background

Back in the beginning, the TYPO3 Core Team was a closed group of people developing TYPO3 behind the curtain. In 2007 that changed, the core mailing list was opened to the public and everyone was invited to start contributing patches - via mail attachment. Frequent and reliable contributors were occasionally invited to join the team, the product and the team grew. Dedicated release managers were assigned to take care of one specific release, releasing whenever they considered the version done. Previous release managers came together in the so-called “Release Team” supporting the current one. Over time the release team additionally worked on overall topics and strategies and slowly merged into the so-called TYPO3 Product Team. This team structure - consisting of a product team working more strategically and ‘long-term’ - and a core team “bundling” core mergers was not changed since then.

The CMS market changed quite a bit through these years bringing with it new challenges - technological, organisational and communication wise. In light of these changes we decided to overhaul our dated structure.

Changes: New Challenges, More Responsibilities, Bigger Project

In our current CMS world, the TYPO3 Core Team needs to tackle coordination with stand-alone projects like Fluid, get involved in bigger PHP community initiatives like the development of PSR-14 and keep track of a myriad of technological innovations in addition to contributing code and supervising contributors. Collaboration with other community teams like documentation and marketing became more important through growth of the project and neglecting these topics for a while result in a higher workload necessary to straighten out these topics.

Releasing no longer only involves packaging and providing the packages but our professional demand is to have marketing and press material ready, documentation updated and a stable and usable product at the same time - hence more coordination and organisation is needed.

On top, it’s part of our job to constantly assessing the viability of current and future technological solutions on a fast-changing market and the planned integration of modern technology.

Restructuring has begun - Stay Tuned

A restructuring process has been started and will happen throughout the following weeks - it will change the basic setup of the team, define how we work together, closely intertwined with each other with common roadmap and common goals - intersecting with other teams and collaborating professionally, efficiently while still having fun pushing the product forward.

Oliver Hader and me will lead that process - being part of the community and core team since ten years and more both have a lot of experience with TYPO3, the community and the team. Both of us having led the core team before can use the past adventures as well as our knowledge of our current challenges to lead us to a better team and working mode, and eventually being even more open for new contributors.

Expected Result and Next Steps

As a result of the restructuring process we will have a new structure and a new working mode that is sustainable, future-proof, adaptable to changes, transparent to newcomers, efficient and still fun.

We expect the process to take about two to three months, during which time the current development will continue - putting a focus on our precious v9 LTS release coming up, where all contributors are welcome to join the efforts.

If you want to contribute take a look at our Contribution Walkthrough or join the CodeSprint in Dresden at the beginning of August.

Stay tuned for further news on this topic. In the meantime: Happy coding!

]]>
Development Community TYPO3 CMS
news-1793 Thu, 12 Jul 2018 10:02:00 +0200 TYPO3 9.3.1, 8.7.17 and 7.6.30 security releases published https://typo3.org/article/typo3-931-8717-and-7630-security-releases-published/ The TYPO3 Community announces the versions 9.3.1, 8.7.17 LTS and 7.6.30 LTS of the TYPO3 Enterprise Content Management System. We are announcing the release of the following TYPO3 updates:

All versions are security releases and contain important security fixes - read the corresponding Security Advisories here:

Some security fixes require a specific upgrade path, make sure you read the instructions in the advisories carefully. If you are using the form extension, under certain circumstances a manual step is needed as well as executing the upgrade wizards. See TYPO3-CORE-SA-2018-003

Download

TYPO3 can be installed in various ways. For example the traditional way by using the source package at get.typo3.org or the modern way by setting up a project using composer, to name just two. Further details can be found in the according release notes:

]]>
Development TYPO3 CMS
news-1792 Wed, 11 Jul 2018 12:51:17 +0200 Italian Book Release: Extbase and Fluid https://typo3.org/article/italian-book-release-extbase-and-fluid/ A new Italian book is now available. How to program and implement TYPO3 extensions? This book provides all you need to know to get up and running with Extbase and Fluid, one of the many ways to build extensions. TYPO3 extensions play a major role in the day-to-day business of developing TYPO3 sites. To become a seasoned TYPO3 developer, one of the basics you need to learn is how to program and implement these extensions. There are many different ways to build TYPO3 extensions, for instance:

  • With the pi-based infrastructure
  • Based on Extbase and Fluid 
  • Write extensions from scratch with pure PHP code
  • Or use any PHP framework you like

Jump start your Extbase and Fluid skills

To acquire the comprehensive skill set of Extbase and Fluid, a good starting point is a book that is now available in ItalianTYPO3 Extbase: Sviluppo Estensioni Moderne per TYPO3 CMS con Extbase & Fluid (Italiano).

You’ll find the English version here: TYPO3 Extbase: Modern Extension Development for TYPO3 CMS with Extbase & Fluid and the German version here: TYPO3 Extbase: Moderne Extensionentwicklung für TYPO3 CMS mit Extbase & Fluid.

]]>
Community
news-1791 Thu, 28 Jun 2018 10:16:41 +0200 How to Use Slack in the TYPO3 Community https://typo3.org/article/how-to-use-slack-in-the-typo3-community/ Slack simplifies communication and brings our global community together, creating a virtual shared workspace where conversations are documented and accessible. It is a free software client that is available on many platforms.

Thanks to Slack, the TYPO3 community is able to:

  • Chat (via group chat or direct messaging)
  • Exchange files
  • Call and make presentations using video or audio
  • Get notified of updates via email when they are offline

What will I find in Slack?

A great environment for communicating with many different channels (groups). Here are some of the important channels for the TYPO3 community to get you started:

  • #announcements: the TYPO3 project announcement channel–you will automatically join this channel, but you cannot post there
  • #typo3-cms: TYPO3 CMS support channel
  • #typo3-cms-coredev: TYPO3 CMS core development channel
  • #random: have fun, share anything you like
  • #T3DD: TYPO3 Developer Days channel
  • #typo3-documentation: Documentation Team–if you have any questions or suggestions regarding documentation
  • #t3o-team: typo3.org–if you are having trouble with or questions about your typo3.org website

 ... and there are many more for you to discover!

You can also start one-to-one chats by starting a conversation with a single user.

Stick to the rules

When using Slack, we ask you to please stick to the TYPO3 community code of conduct.

N.B. If you have a support question, please ask it on Stack Overflow first. Slack is a very handy and fast tool for getting answers, but it is not a publicly available resource. To increase the visibility of TYPO3 and TYPO3 related questions on the web, please ask your support question on Stack Overflow and then paste it into Slack. Following your discussion please make sure the result (hopefully the right answer!) is added to Stack Overflow to help the wider community.

How do I sign up to the TYPO3 Community Slack?

Just visit my.typo3.org and login (or register if you don’t have an account yet). You can use this link to create and connect your Slack account.

What if I already have a Slack account?

You can also connect your existing Slack account with your typo3.org user profile and become part of the TYPO3 Slack community. Soon we will add a new feature where you can choose to display your Slack profile in your typo3.org user profile–watch this space.

]]>
Community
news-1790 Wed, 27 Jun 2018 23:40:00 +0200 This Month in TYPO3 - June 2018 - Issue #3 https://typo3.org/project/news/this-month-in-typo3/this-month-in-typo3-june-2018-issue-3/ June has been a very busy month for the TYPO3 community with exciting events like Developer Days, new TYPO3 releases, and new TYPO3 Core Team members. Community news-1789 Wed, 27 Jun 2018 09:44:13 +0200 Say hello to our new Core Team Members! https://typo3.org/article/say-hello-to-our-new-core-team-members/ The TYPO3 Core Team is proud to announce three new members: Please welcome Mathias Brodala, Anja Leichsenring and Ralf Zimmermann. Development Community TYPO3 CMS news-1784 Wed, 13 Jun 2018 08:58:00 +0200 TYPO3 Site Package Tutorial https://typo3.org/article/typo3-site-package-tutorial/ Today, the TYPO3 Documentation Team published a tutorial that describes the steps required to turn a basic design template into a fully working, mobile-responsive website. Following the steps of the Site Package Tutorial, written by Michael Schams, you can build a modern extension with all relevant files stored at a central point. Changes can easily be tracked in version control. TYPO3 supports several methods for implementing websites, but this approach is both flexible and professional. At the same time, the process is not overly complicated and does not require any programming knowledge.

TYPO3 requires some initial configuration and a design template to provide the visual appearance of a site. A basic TYPO3 installation has only the foundation (“framework”) of a website. There are no pages, no default themes and even when you access the frontend, the system returns an error message by default.

The development of a website can be approached in several ways. While standard websites usually consist of HTML documents that contain text, with images, videos, styles, etc., referenced, TYPO3 features a clean separation between design, content and functionality of a website. Developers and integrators can easily add simple, as well as sophisticated functions to the enterprise content management system.

Benefits of a Site Package

A Site Package extension comes with a number of benefits. Extensions are a powerful way to get the most out of TYPO3, and can be installed to extend the core system with new functions and features. By using version control software, such as Git, developers can revert a change or switch back to a previous point in time with the click of a button. This is not only useful for individual developers, but allows teams to track who made which change, why, and when.

Another important benefit of a TYPO3 extension is that dependencies on other extensions, as well as the supported TYPO3 versions, can be defined. This makes deployment easier and more fail-safe. When the Site Package extension is installed in an empty TYPO3 instance, all dependent extensions can be downloaded from the TYPO3 Extension Repository and installed automatically.

When building a website without using an extension, template files are often stored in the fileadmin/ directory of a TYPO3 instance — the “user space”. Files in this directory are indexed by TYPO3's File Abstraction Layer (FAL), creating irrelevant and avoidable records in the database. Additionally, files in fileadmin/ are typically meant to be publicly accessible by convention. To avoid disclosing sensitive system information (see the TYPO3 Security Guide for further details), configuration files should not be stored there.

In virtue of the motto "TYPO3 inspires people to share!", the Site Package extension can also be shared with the community via the official TYPO3 Extension Repository or in a publicly accessible version control system, such as GitHub.

The Tutorial

The Site Package Tutorial walks the reader through every step on the way to building a basic Site Package. It uses modern and well-known libraries, such as Bootstrap and jQuery, and contains the example code you need to create a fully working TYPO3 website. Screenshots ensure that even beginners to TYPO3 will reach their goal.

After completing the tutorial, you will not only know how to build the TYPO3 website in a modern way, but you will also know how to use the Site Package in your own installations. The extension is ready-to-use and can be extended and adjusted according to your needs.

With simple static HTML/CSS templates as the starting point, the Site Package Tutorial covers the following topics:

  • Split the design template files into Fluid templates (Layout, Templates, and Partial)

  • Apply Fluid Styled Content TypoScript

  • Include the Bootstrap framework and jQuery library as external resources

  • Build a fully functional TYPO3 extension

  • Install the Site Package extension via the Extension Manager

  • Create some initial pages, their TypoScript templates, and preview a page in the TYPO3 backend

  • Develop a simple navigation menu using TypoScript and Fluid

  • Apply TypoScript to render the content of a page

The final extension contains only six files without HTML/CSS. Only two files contain PHP code. It is also worth pointing out that the Site Package extension does not require any third party extensions and works in an empty, newly installed TYPO3 instance.

The tutorial is based loosely on the three-part video series by Mathias Schreiber and Benjamin Kott, on how to set up a TYPO3 site from scratch by building a Site Package extension.

Aimed at Integrators and Developers

The tutorial is written for TYPO3 integrators and developers. It requires a basic understanding of HTML, CSS and JavaScript. Readers should have some knowledge of TYPO3 and the administrative interface (the Backend). No software programming experience is required.

About Michael Schams

Michael Schams is an international open source technology advocate. He holds a master’s degree in computer science and is a regular contributor to technical journals. With many years' experience in using and developing TYPO3, Michael is a well-known member of the TYPO3 community and involved in several activities and projects around the open-source content management system. He is the author of the TYPO3 Security Guide and co-author of three TYPO3 books.

Michael is currently based in Melbourne (Australia) and consults with clients across the globe to achieve best outcomes in the digital space, web hosting, IT infrastructure, IT security, and cloud computing/storage.

About the Documentation Team

The TYPO3 Documentation Team provides comprehensive, quality documentation for TYPO3 products for all users. The team not only writes, publishes and maintains official documentation for TYPO3, but also supports the TYPO3 Core Team and other teams in their documentation efforts.

The Site Package Tutorial can be found at docs.typo3.org, the central place for official TYPO3 documentation.

]]>
Community