|
|
typo3_news.rss.xml - sfeed_tests - sfeed tests and RSS and Atom files |
|
|
 |
git clone git://git.codemadness.org/sfeed_tests (git://git.codemadness.org) |
|
|
 |
Log |
|
|
|
Files |
|
|
|
Refs |
|
|
|
README |
|
|
|
LICENSE |
|
|
|
--- |
|
|
|
typo3_news.rss.xml (111511B) |
|
|
|
--- |
|
|
|
1 <?xml version="1.0" encoding="utf-8"?> |
|
|
|
2 <rss version="2.0" |
|
|
|
3 xmlns:content="http://purl.org/rss/1.0/modules/content/" |
|
|
|
4 xmlns:atom="http://www.w3.org/2005/Atom" |
|
|
|
5 xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers" |
|
|
|
6 xmlns:n="http://typo3.org/ns/GeorgRinger/News/ViewHelpers"> |
|
|
|
7 <channel> |
|
|
|
8 <title>Official typo3.org news</title> |
|
|
|
9 <link>https://www.typo3.org/</link> |
|
|
|
10 <description></description> |
|
|
|
11 <language>en-gb</language> |
|
|
|
12 |
|
|
|
13 <copyright>TYPO3 News</copyright> |
|
|
|
14 |
|
|
|
15 <pubDate> |
|
|
|
16 Sun, 18 Oct 2020 19:29:37 +0200 |
|
|
|
17 </pubDate> |
|
|
|
18 <lastBuildDate> |
|
|
|
19 Sun, 18 Oct 2020 19:29:37 +0200 |
|
|
|
20 </lastBuildDate> |
|
|
|
21 |
|
|
|
22 <atom:link href="https://typo3.org/?type=100" rel="self" |
|
|
|
23 type="application/rss+xml"/> |
|
|
|
24 <generator>TYPO3 EXT:news</generator> |
|
|
|
25 |
|
|
|
26 |
|
|
|
27 <item> |
|
|
|
28 <guid isPermaLink="false">news-2087</guid> |
|
|
|
29 <pubDate> |
|
|
|
30 Sun, 18 Oct 2020 19:18:04 +0200 |
|
|
|
31 </pubDate> |
|
|
|
32 <title>Marketing Sprint—A vision for 2021 |
|
|
|
33 </title> |
|
|
|
34 <link> |
|
|
|
35 |
|
|
|
36 https://typo3.org/article/marketing-sprint-a-vision-for-2021 |
|
|
|
37 |
|
|
|
38 </link> |
|
|
|
39 <description>In our most recent marketing sprint, we opened up the discussion to think more broadly about what we want to achieve with the marketing team, what is in scope, and what the roadmap for 2021 will look like. </description> |
|
|
|
40 <content:encoded> |
|
|
|
41 <![CDATA[ |
|
|
|
42 <p><a href="/event/20201201-typo3-online-marketing-sprint-q4-2020?type=100" class="btn btn-primary">Join the Next TYPO3 Online Marketing Sprint Q4/2020</a></p> |
|
|
|
43 <h2>About the Sprint</h2> |
|
|
|
44 <p>In this sprint, we held open-ended discussions. This was in contrast to the past marketing sprints in which we were still somewhat focused on release communications. </p> |
|
|
|
45 <p>Thank you to twelve attendees, including members of the TYPO3 Marketing Team and newcomers from Canada, Egypt, and Austria! </p> |
|
|
|
46 <ul> <li><strong>General Global Strategy</strong></li> <li><strong>Onboarding Newcomers </strong></li> </ul> |
|
|
|
47 <h2>Notes from the Global Strategy Session</h2> |
|
|
|
48 <p>This group explored: Which markets should we focus on? What does each market need? How can we support local communities? </p> |
|
|
|
49 <p>In the sprint, we had presentations from participants to talk about markets in which they work. They researched the state of TYPO3 in these regions. </p> |
|
|
|
50 <ol> <li>US—Paul Hansen.</li> <li>South America—Carlos Llanos.</li> <li>Egypt, North Africa, Canada—Ahmed.</li> </ol> |
|
|
|
51 <p>Where does the TYPO3 community want to make a push for promotion? US / North America!</p> |
|
|
|
52 <p>What can we do to be more active in those regions? Partnerships, mentorship, and support from experienced agencies. </p> |
|
|
|
53 <p>Questions that came out of this session:</p> |
|
|
|
54 <ul> <li>How to reach digital agencies in the US to have them considering adding TYPO3 to their portfolio?</li> <li>What kind of onboarding, support, or mentoring could be given to those working in digital agencies? </li> </ul> |
|
|
|
55 <h2>Notes from the Onboarding Session</h2> |
|
|
|
56 <p>This group explored: What is the experience of TYPO3 like for newcomers? What can we do to improve it? How can we get this done? Who should be involved? </p> |
|
|
|
57 <p>At the start of the session, this small group focused on defining: What do we mean by onboarding? </p> |
|
|
|
58 <ul> <li>“Onboarding, also known as<strong> organizational socialization</strong>,” whereby people “acquire the necessary knowledge, skills, and behaviors in order to become effective organizational members and insiders.”—<a href="https://en.wikipedia.org/wiki/Onboarding" target="_blank" rel="noreferrer">Wikipedia</a> </li> </ul> |
|
|
|
59 <p>What is out of scope for the marketing team? End-user onboarding which is a product question. </p> |
|
|
|
60 <p>In scope for the marketing team. </p> |
|
|
|
61 <ul> <li><strong>Top of the funnel and onboarding decision-makers.</strong> As soon as people search for TYPO3, they begin their journey. <ul> <li>Who? A mixed audience in a decision-making unit. </li> <li>What? They need introductory information about TYPO3. </li> </ul> </li> <li><strong>TYPO3 Community onboarding</strong> from initial exploration, to entry, to participation, <ul> <li>From “learning about TYPO3” to using it, to being a good open-source citizen, to becoming a contributor. </li> <li>Who? Any TYPO3 user. </li> <li>What? Participation and contribution could be attending events, organizing, direct contribution via Association Membership, user feedback, and software development.</li> <li>Check out: <a href="https://mikemcquaid.com/2018/08/14/the-open-source-contributor-funnel-why-people-dont-contribute-to-your-open-source-project/" target="_blank" rel="noreferrer">The Open Source Contributor Funnel</a>. </li> </ul> </li> </ul> |
|
|
|
62 <p>We realized that improvements in onboarding cannot happen without involving people from across community teams and initiatives. So we have hatched an idea to develop a cross-community sprint on improving the onboarding experience for 2021. Keep an eye out for news! </p> |
|
|
|
63 <h2>A TYPO3 Marketing Roadmap</h2> |
|
|
|
64 <p>Based on the discussions in this sprint, we agreed on a roadmap… </p> |
|
|
|
65 <ul> <li>Q4 Sprint in December—focus on Sales Resources. Competitor comparisons, and resources for decision-makers and sales teams. </li> <li>Q1 2021: An open sprint involving more people from across the community to focus on onboarding and newcomer experiences.</li> </ul> |
|
|
|
66 <p>So we decided until then, we would finish Q3 tasks until the end of 2020.</p> |
|
|
|
67 <h2>Want to Help TYPO3 Compete? </h2> |
|
|
|
68 <p>Join us for the next marketing sprint. </p> |
|
|
|
69 <ul> <li><a href="https://typo3.org/event/20201201-typo3-online-marketing-sprint-q4-2020" target="_blank">TYPO3 Online Marketing Sprint Q4/2020</a> </li> <li>Tue. 1st - Wed. 2nd December 2020. </li> <li>Each day from 13:00 - 17:00 CET. </li> </ul> |
|
|
|
70 <p>We’re going to focus on preparing “battle cards” to help salespeople sell TYPO3 in head-to-head comparisons about TYPO3 versus other open-source CMSs. </p> |
|
|
|
71 <p>If you have experience with any of the following, we’d love your input!</p> |
|
|
|
72 <ul> <li>WordPress</li> <li>Drupal</li> <li>Joomla</li> <li>Jimdo</li> <li>Static CMSs</li> </ul> |
|
|
|
73 <p><a href="/event/20201201-typo3-online-marketing-sprint-q4-2020?type=100" class="btn btn-primary">Register here</a></p> |
|
|
|
74 ]]> |
|
|
|
75 </content:encoded> |
|
|
|
76 |
|
|
|
77 |
|
|
|
78 <category>Community</category> |
|
|
|
79 |
|
|
|
80 <category>Marketing</category> |
|
|
|
81 |
|
|
|
82 |
|
|
|
83 </item> |
|
|
|
84 |
|
|
|
85 <item> |
|
|
|
86 <guid isPermaLink="false">news-2086</guid> |
|
|
|
87 <pubDate> |
|
|
|
88 Thu, 15 Oct 2020 09:00:00 +0200 |
|
|
|
89 </pubDate> |
|
|
|
90 <title>Selling TYPO3—What Salespeople Told Us |
|
|
|
91 </title> |
|
|
|
92 <link> |
|
|
|
93 |
|
|
|
94 https://typo3.org/article/selling-typo3-what-salespeople-told-us |
|
|
|
95 |
|
|
|
96 </link> |
|
|
|
97 <description>Here’s what sixteen salespeople told us about selling TYPO3, and what we’re doing to make their jobs easier so TYPO3 stays competitive. The results of this survey validate work already underway to improve the editor experience and communications.</description> |
|
|
|
98 <content:encoded> |
|
|
|
99 <![CDATA[ |
|
|
|
100 <p>Thank you to the respondents and thank you to my colleague, Liz Robau from <a href="https://openstrategypartners.com" target="_blank" rel="noreferrer">Open Strategy Partners</a> for helping to prepare the survey analysis. I’ll provide a summary of the results, and also show you what the community is already doing to address some of these concerns. </p> |
|
|
|
101 <h2>About the survey</h2> |
|
|
|
102 <p>The idea for this survey was hatched in the <a href="/article/recap-from-the-first-online-marketing-sprint-q2-2020?type=100">Marketing Sprint in May</a>, our first-ever online sprint. We designed and pilot tested the survey in June. Then the survey ran from July to September. We promoted it directly via invitation and through the TYPO3 Association Newsletter. (Which, if you’re not getting it, sign up for your <a href="/project/association/membership?type=100">TYPO3 Association membership</a>!)</p> |
|
|
|
103 <p>This was a long-form qualitative survey, with many open-ended questions with a small, focused sample of people currently selling TYPO3. In the next iteration, we’ll design a shorter quantitative survey. This will mean we’ll select the highest impact questions and turn open-ended questions into multiple-choice questions based on the patterns we saw here. We’ll launch that survey with the outcomes from the next marketing sprint where we’ll be focusing on sales assets. </p> |
|
|
|
104 <p><a href="https://typo3.org/event/20201201-typo3-online-marketing-sprint-q4-2020" target="_blank" class="btn btn-primary">Sign up for the next online Marketing Sprint, 1–2 Dec 2020. </a></p> |
|
|
|
105 <h2>Who Responded to the Survey?</h2> |
|
|
|
106 <p>We were looking for salespeople who work in digital agencies, so this sample is close to what we were looking for with the bulk, <strong>87.5%, of respondents working for a digital agency</strong>. What was surprising is that over half also fulfil project management roles too, and many were highly experienced. </p> |
|
|
|
107 <ul> <li>Many respondents have multiple roles. Over half (56.3%) were also project managers.</li> <li>Respondents were experienced. 50% have been in their current role for 10+ years.</li> <li>They pitch to companies of all sizes. The most common being small companies (11-50 people).</li> </ul> |
|
|
|
108 <p>The nice thing is that most of the respondents have a positive impression of TYPO3. </p> |
|
|
|
109 <ul> <li>Most respondents (87.5%) would recommend TYPO3 to a friend.</li> </ul> |
|
|
|
110 <p>When we run this survey again on a larger sample, we’d expect to see some changes to this make-up. </p> |
|
|
|
111 <h2>What is it Like to Sell TYPO3?</h2> |
|
|
|
112 <p>We asked respondents to tell us what features were strong points, how they opened their conversations with decision-makers. </p> |
|
|
|
113 <ul> <li>About 40% of respondents focus on TYPO3’s flexibility, extensibility, or scalability. For example: “It's applicable to any kind of project size and can really <strong>easily be extended</strong> and personalized.”</li> <li>A separate 25% said they reference the word “enterprise” or “professional” -- probably to highlight its business value. For example, they tell decision-makers “Why TYPO3 is a content management system to build <strong>professional websites</strong>”</li> <li>About 20% used the word “Long Term Support” - referring to <a href="https://typo3.com/products/extended-support" target="_blank" rel="noreferrer">TYPO3 GmbH’s ELTS product</a>. “<strong>Long Time Support</strong>, you can have your website over many updates.”</li> </ul> |
|
|
|
114 <p>This helps us see what salespeople emphasise and in turn, what focus we should have in our recommendations.</p> |
|
|
|
115 <h2>Product Recommendations</h2> |
|
|
|
116 <p>Salespeople see product opportunities based on the kinds of questions they get asked by decision-makers. Often they are competing in an open field against other solutions, so they can see the market gaps against other CMSs. The recommendations were specific and detailed. </p> |
|
|
|
117 <p>Based on this, we recommend that the community prioritize these top “wish list” items to improve sales and marketing. </p> |
|
|
|
118 <ul> <li>Better content editing tools (i.e. grid system, nesting for content elements)</li> <li>Theme editing & out of the box themes</li> <li>Tools for marketers. </li> <li>Fill backend feature-gaps: 2FA, Backend API, Decoupled/Headless TYPO3. </li> </ul> |
|
|
|
119 <p>Over half of all respondents wanted improvements to content editing tools. 33% of respondents listed ‘editor user experience’ as a weakness. They mentioned:</p> |
|
|
|
120 <ul> <li>Editor user experience and The grid system</li> <li>Front end editing</li> <li>Workspaces “(make it right or leave it)” and “More editors-oriented improvements, fewer developer-oriented improvements.”</li> </ul> |
|
|
|
121 <p><strong>The good news is, the community is already mobilised to make improvements in these exact areas. </strong>Far from highlighting unknown issues, this survey validates the direction the community is moving in. </p> |
|
|
|
122 <p>If you’d like to jump in, check out the latest updates from these initiatives. Hop in Slack and ask a question or share a suggestion. </p> |
|
|
|
123 <ul> <li><a href="/article/structured-content-initiative-what-happened-in-may-june-2020?type=100">Structured Content Initiative: Content editing improvements and the layout/grid system</a>.</li> <li>Frontend Editing: <a href="/article/frontend-editing-planning-the-next-major-version?type=100">Planning the Next Major Version</a></li> <li>Workspaces: <a href="/article/workspaces-one-of-typo3s-most-underused-features?type=100">Workspaces—One of TYPO3’s Most Underused Features</a> </li> <li>TYPO3 PWA (Progressive Web Apps) initiative: <a href="/community/teams/typo3-development/initiatives/pwa?type=100">Using TYPO3 as Headless CMS</a>.</li> </ul> |
|
|
|
124 <p><strong>This is heartening and encouraging. We are able to connect the results from this survey and map to initiatives that are now gaining steam. Now is the time to get involved! </strong>Each one of those initiatives could use the insights of sales people and project managers who have direct contact with customers. </p> |
|
|
|
125 <h2>Recommendations for Communications</h2> |
|
|
|
126 <p>Salespeople often create their own materials for selling TYPO3, but they also need authoritative resources to reference and point to. We asked about which materials they currently use, which resources they were aware of, and what they would like to see. </p> |
|
|
|
127 <p>This seems to be an area where we can make a big impact by translating technical features and developments into language that decision-makers and end-user will find helpful. Especially with a new release cycle on the horizon. One respondent said TYPO3 “marketing is felt to be more from the developer's point of view and less from the user's, especially when TYPO3 Versions are explained.” </p> |
|
|
|
128 <p>Based on the results from the survey, these are the recommendations and what we’re doing to address the ideas next. </p> |
|
|
|
129 <ul> <li>Create <strong>more case studies</strong> and detailed feature lists. <ul> <li>TYPO3 GmbH has recently changed the Partner program, introducing an entry-level <a href="https://typo3.com/products/all-about-the-professional-service-listing" target="_blank" rel="noreferrer">Professional Service Listing (PSL)</a>. </li> <li>Partners can <a href="https://typo3.com/case-studies" target="_blank" rel="noreferrer">submit Case Studies to typo3.com</a>.</li> </ul> </li> <li><strong>Publish more competitive comparisons</strong> <ul> <li>In our next <a href="/event/20201201-typo3-online-marketing-sprint-q4-2020?type=100">Marketing Sprint</a>, we’re going to develop ‘battle cards’ with competitive comparisons.</li> </ul> </li> <li>Communications for upcoming releases <ul> <li><strong>Highlight improvements in upcoming releases</strong></li> <li>Highlight any and all improvements to Content Editing and UX</li> <li>In the September marketing sprint, we discussed the need to work more closely with the Core team in communications from the earliest sprint releases. Marketing Team Lead, <a href="/community/meet/you-me-and-typo3/luisa-fassbender?type=100">Luisa Faßbender</a> is now working more closely with the <a href="/community/teams/typo3-development?type=100">TYPO3 Core Team lead, Benni Mack</a>. </li> </ul> </li> <li>Tailor content to clients <strong>outside of DACH region</strong> and emphasize the long-term market position. <ul> <li>In 2021, we’re going to focus on new markets for TYPO3. </li> <li>We’ve had five new people join the Marketing Team from four new countries! </li> </ul> </li> <li>43.8% also mentioned wanting a <strong>TYPO3 demo site. </strong>There are already a few options. But this is also an area where there could be some improvement. <ul> <li><a href="https://bitnami.com/stack/typo3" target="_blank" rel="noreferrer">Bitnami.com TYPO3 stack</a></li> <li><a href="https://www.typo3-websites.eu/en/typo3-cms/test-web-site/" target="_blank" rel="noreferrer">Test web site in stable TYPO3 version 9 LTS—direct access at typo3-websites.eu</a></li> <li><a href="https://www.opensourcecms.com/typo3/" target="_blank" rel="noreferrer">Shared and self-resetting TYPO3 demo at opensourcecms.com</a></li> <li><a href="https://demo.t3terminal.com/?theme=t3t-freelancer" target="_blank" rel="noreferrer">Frontend only at t3terminal.com</a></li> <li><a href="https://typo3muster.de/" target="_blank" rel="noreferrer">Frontend only at typo3muster.de</a> (German language)</li> </ul> </li> </ul> |
|
|
|
130 <p>If you’d like to see the full TYPO3 Sales Survey findings, please join the Marketing Team’s next sprint, or ping us in the <a href="https://typo3.slack.com/archives/C32MH130C" target="_blank" rel="noreferrer">#marketing slack channel</a>. </p> |
|
|
|
131 <h2>What’s Next?</h2> |
|
|
|
132 <p>Join us for the next online marketing sprint. </p> |
|
|
|
133 <p class="indent-1"><strong><a href="/event/20201201-typo3-online-marketing-sprint-q4-2020?type=100" class="btn btn-primary">TYPO3 Online Marketing Sprint Q4/2020</a> </strong><br /> Tuesday 1st and Wednesday 2nd December 2020. <br /> Each day 13:00–17:00 CET</p> |
|
|
|
134 <p>We’re going to focus on preparing sales resources with head-to-head comparisons about TYPO3 versus other open-source CMSs.</p> |
|
|
|
135 ]]> |
|
|
|
136 </content:encoded> |
|
|
|
137 |
|
|
|
138 |
|
|
|
139 <category>Community</category> |
|
|
|
140 |
|
|
|
141 <category>Marketing</category> |
|
|
|
142 |
|
|
|
143 |
|
|
|
144 </item> |
|
|
|
145 |
|
|
|
146 <item> |
|
|
|
147 <guid isPermaLink="false">news-2085</guid> |
|
|
|
148 <pubDate> |
|
|
|
149 Tue, 13 Oct 2020 19:02:54 +0200 |
|
|
|
150 </pubDate> |
|
|
|
151 <title>TYPO3 Market Insights With T3versions.com |
|
|
|
152 </title> |
|
|
|
153 <link> |
|
|
|
154 |
|
|
|
155 https://typo3.org/article/typo3-market-insights-with-t3versionscom |
|
|
|
156 |
|
|
|
157 </link> |
|
|
|
158 <description>T3versions.com is a free online service that uses various fingerprinting technologies to identify whether a website is running TYPO3 and, if so, which major version it’s using. We collect data by performing mass scans of domain lists and by compiling user inputs to our website.</description> |
|
|
|
159 <content:encoded> |
|
|
|
160 <![CDATA[ |
|
|
|
161 <p>The service has been up and running since April 2018 and, since then, we’ve created a database of websites running TYPO3. The database includes statistics about which TYPO3 major and patch versions are in use. </p> |
|
|
|
162 <p>In order to analyze and identify trends from the data collected by t3versions, Ronald Meeuwissen from the TYPO3 marketing team kicked off the “Market Intelligence Team” project. To begin the project, the TYPO3 Marketing Team and TYPO3 GmbH defined several goals and milestones. As part of the first milestone, the following tasks have been outlined and accomplished.</p> |
|
|
|
163 <p><a href="https://www.t3versions.com/statistics-detail/10" target="_blank" class="btn btn-primary" rel="noreferrer">View the latest TYPO3 Statistics</a></p> |
|
|
|
164 <h2>Regularly Check Existing Websites</h2> |
|
|
|
165 <p>In order to visualize statistics and trends, existing data must be updated on a regular basis. Therefore all existing websites in the database will be checked at least once every three months.</p> |
|
|
|
166 <h2>Increase Data Coverage</h2> |
|
|
|
167 <p>There are currently two ways a newly launched TYPO3 website gets added to the t3versions database. Either a user manually enters the website domain into <a href="http://www.t3versions.com/" target="_blank" rel="noreferrer">www.t3versions.com</a> or it’s added when we perform a mass scan of domain lists (with millions of domains), which we acquire once per year.</p> |
|
|
|
168 <p>We discussed creating an API endpoint that performs TYPO3 version checks as a way of adding new TYPO3 websites to the database, and added this functionality to the first version of our API.</p> |
|
|
|
169 <h2>Provide Custom Data Analysis</h2> |
|
|
|
170 <p>To identify trends (e.g., increasing or decreasing usage of TYPO3 in a country), the <a href="/project/association?type=100">TYPO3 Association</a> and <a href="https://typo3.com" target="_blank" rel="noreferrer">TYPO3 GmbH</a> needed the ability to perform custom queries on the data available for TYPO3 websites. This task was completed by creating an API.</p> |
|
|
|
171 <h2>Creating the T3versions API</h2> |
|
|
|
172 <p>Developing the t3versions API was the largest piece of work for our first milestone. The API was created using the popular Django REST Framework, which provides many necessary functions, like authentication, permissions, and rate-limiting. </p> |
|
|
|
173 <p>The first version of the API contains endpoints that perform the following actions:</p> |
|
|
|
174 <ul> <li><strong>Check domains</strong> <ul> <li>Queue a given domain to be checked for TYPO3 usage</li> <li>Query the result of a queued check</li> </ul> </li> <li><strong>Get and query database websites</strong> <ul> <li>Get a list of all TYPO3 websites in the database including a limited set of data (domain, major version, last check).</li> <li>Use several search filters to query the full set of data (excluding patch level version)</li> </ul> </li> <li><strong>Site changes</strong> <ul> <li>Use several search filters to query monitored site changes (e.g. site updated TYPO3 version)</li> </ul> </li> </ul> |
|
|
|
175 <p>All API endpoints require user authentication and specific permissions. </p> |
|
|
|
176 <p>We’re currently working on providing 3rd party services access to endpoints that perform site checks. This will make it possible to automate your own checks for TYPO3 version detection and may also increase the data coverage on t3versions.</p> |
|
|
|
177 <h2>Stabilize Version Analysis</h2> |
|
|
|
178 <p>While developing the API, we identified the following two problems in the t3versions scan engine:</p> |
|
|
|
179 <ol> <li>When a check discovered that a known TYPO3 website was offline or its domain was unreachable, it did not remove the site from the database.</li> <li>When a check got redirected to a non-TYPO3 website from a known website, it did not remove the original site from the database</li> </ol> |
|
|
|
180 <p>Both problems have been fixed and a rescan of all available websites resulted in a removal of 51635 TYPO3 websites from the database. </p> |
|
|
|
181 <h2>Make Scan Results and Statistics More User-Friendly</h2> |
|
|
|
182 <p>When T3versions was created, technical tasks related to the backend took priority over the website’s layout and visual design.</p> |
|
|
|
183 <p>Since completing the first milestone, we replaced the website’s initial CSS with the Bulma CSS Framework. Colors are now more TYPO3-like and the website content—statistics, scan results, etc.—is more readable and user-friendly. </p> |
|
|
|
184 <p>The check result page was also improved, so it’s now clear whether a website is running a community-supported TYPO3 version or not. </p> |
|
|
|
185 <h2>Next Steps</h2> |
|
|
|
186 <p>The work accomplished in the first milestone of the project is now the basis for upcoming improvements and changes to t3versions. Together with TYPO3 GmbH, we will define and add new trend graphs to the website as soon as usable data is available. We’d also appreciate your feedback. Please feel free to shoot us a message and suggest potential new features—we’ll prioritize them with our stakeholders! </p> |
|
|
|
187 <p><a href="https://www.t3versions.com" target="_blank" class="btn btn-primary" rel="noreferrer">Check out the TYPO3 Version Check</a></p> |
|
|
|
188 ]]> |
|
|
|
189 </content:encoded> |
|
|
|
190 |
|
|
|
191 |
|
|
|
192 <category>Community</category> |
|
|
|
193 |
|
|
|
194 <category>Association</category> |
|
|
|
195 |
|
|
|
196 <category>TYPO3 CMS</category> |
|
|
|
197 |
|
|
|
198 <category>Marketing</category> |
|
|
|
199 |
|
|
|
200 |
|
|
|
201 </item> |
|
|
|
202 |
|
|
|
203 <item> |
|
|
|
204 <guid isPermaLink="false">news-2080</guid> |
|
|
|
205 <pubDate> |
|
|
|
206 Wed, 30 Sep 2020 10:00:00 +0200 |
|
|
|
207 </pubDate> |
|
|
|
208 <title>TYPO3 v10 Certification Syllabuses |
|
|
|
209 </title> |
|
|
|
210 <link> |
|
|
|
211 |
|
|
|
212 https://typo3.org/article/typo3-v10-certification-syllabuses |
|
|
|
213 |
|
|
|
214 </link> |
|
|
|
215 <description>Exciting news from the TYPO3 Education Committee: the updated syllabuses for all four TYPO3 certifications are out now. Integrators, developers, consultants, and editors can now use these documents to prepare for the upcoming TYPO3 v10 exams, which will become effective in 2021.</description> |
|
|
|
216 <content:encoded> |
|
|
|
217 <![CDATA[ |
|
|
|
218 |
|
|
|
219 ]]> |
|
|
|
220 </content:encoded> |
|
|
|
221 |
|
|
|
222 |
|
|
|
223 <category>Community</category> |
|
|
|
224 |
|
|
|
225 <category>Education & Certification</category> |
|
|
|
226 |
|
|
|
227 |
|
|
|
228 </item> |
|
|
|
229 |
|
|
|
230 <item> |
|
|
|
231 <guid isPermaLink="false">news-2084</guid> |
|
|
|
232 <pubDate> |
|
|
|
233 Tue, 29 Sep 2020 16:19:48 +0200 |
|
|
|
234 </pubDate> |
|
|
|
235 <title>Workspaces—One of TYPO3’s Most Underused Features |
|
|
|
236 </title> |
|
|
|
237 <link> |
|
|
|
238 |
|
|
|
239 https://typo3.org/article/workspaces-one-of-typo3s-most-underused-features |
|
|
|
240 |
|
|
|
241 </link> |
|
|
|
242 <description>Workspaces is one of TYPO3’s Unique Selling Points, but it is underused and has lacked the necessary developer manpower. Now, you can change this—by using Workspaces and supporting our efforts for TYPO3 v11.</description> |
|
|
|
243 <content:encoded> |
|
|
|
244 <![CDATA[ |
|
|
|
245 |
|
|
|
246 ]]> |
|
|
|
247 </content:encoded> |
|
|
|
248 |
|
|
|
249 |
|
|
|
250 <category>Development</category> |
|
|
|
251 |
|
|
|
252 |
|
|
|
253 </item> |
|
|
|
254 |
|
|
|
255 <item> |
|
|
|
256 <guid isPermaLink="false">news-2083</guid> |
|
|
|
257 <pubDate> |
|
|
|
258 Tue, 29 Sep 2020 10:39:46 +0200 |
|
|
|
259 </pubDate> |
|
|
|
260 <title>TYPO3 10.4.9 and 9.5.22 maintenance releases published |
|
|
|
261 </title> |
|
|
|
262 <link> |
|
|
|
263 |
|
|
|
264 https://typo3.org/article/typo3-1049-and-9522-maintenance-releases-published |
|
|
|
265 |
|
|
|
266 </link> |
|
|
|
267 <description>The versions 10.4.9 and 9.5.22 of the TYPO3 Enterprise Content Management System have just been released.</description> |
|
|
|
268 <content:encoded> |
|
|
|
269 <![CDATA[ |
|
|
|
270 |
|
|
|
271 ]]> |
|
|
|
272 </content:encoded> |
|
|
|
273 |
|
|
|
274 |
|
|
|
275 <category>Development</category> |
|
|
|
276 |
|
|
|
277 <category>TYPO3 CMS</category> |
|
|
|
278 |
|
|
|
279 |
|
|
|
280 </item> |
|
|
|
281 |
|
|
|
282 <item> |
|
|
|
283 <guid isPermaLink="false">news-2082</guid> |
|
|
|
284 <pubDate> |
|
|
|
285 Tue, 29 Sep 2020 08:00:00 +0200 |
|
|
|
286 </pubDate> |
|
|
|
287 <title>TYPO3 Guidebook Update September 2020 |
|
|
|
288 </title> |
|
|
|
289 <link> |
|
|
|
290 |
|
|
|
291 https://typo3.org/article/typo3-guidebook-update-september-2020 |
|
|
|
292 |
|
|
|
293 </link> |
|
|
|
294 <description>In this article we explain the philosophy behind the hands-on guides in the TYPO3 Guidebook and along with an exciting progress update.</description> |
|
|
|
295 <content:encoded> |
|
|
|
296 <![CDATA[ |
|
|
|
297 <p>What a wild ride these last few months have been! After the <a href="/article/typo3-book-report-whos-writing-the-typo3-book?type=100">last update about the book</a> we’ve wrapped up the illustrations, the hands-on guides, and the pieces that turn a piece of writing into a book such as front and back matter, references and a glossary. Writing a book is a challenging and demanding process. In this post, I want to share a bit about what has gone into creating the guides. </p> |
|
|
|
298 <p>We’re excited to be another step along in the process, being able to celebrate handing the book over to our publishers, Apress. </p> |
|
|
|
299 <h2>Where Is the TYPO3 Guidebook At?</h2> |
|
|
|
300 <p>In <a href="/article/typo3-book-report-whos-writing-the-typo3-book?type=100">the last update</a>, I interviewed co-author Felicity Brand so you could know a bit about who is writing this book and what we are up to. </p> |
|
|
|
301 <p>We talked about how the book is written in two parts. </p> |
|
|
|
302 <ul> <li>The first part contains four chapters that cover a showcase of what is possible with TYPO3, then a discussion about design, implementation, and maintenance. </li> <li>The second part contains ten practical guides with procedures to work through some common activities. </li> </ul> |
|
|
|
303 <p>Here’s a bit about me, how I shaped the design of the guides, and how we created them with subject matter experts. </p> |
|
|
|
304 <h2>Pro-Tips on Making a Peanut Butter and Jelly Sandwich</h2> |
|
|
|
305 <p>I’ve been working in creating learning content since 1997 (gasp!); from language learning content, to games, to classroom and e-learning materials. But my very first experience in instructional design was writing steps for making a peanut butter and jelly sandwich when I was around 9 years old. As part of the fun, our teacher got up and attempted to follow our steps. She acted it all out, with real bread, and peanut butter and jelly—it was so funny! </p> |
|
|
|
306 <p>I recall being shocked at the results of not explaining how to get the bag open, assuming something like that was totally obvious. We all refined our procedures, and learned how important the details were. I recall adding a tip about pulling the <em>best</em> bread from the centre of the loaf. Pro-tips.</p> |
|
|
|
307 <p>Little did I know that it would be my first such writing exercise that would lead me to a Masters in learning and technology, and creating hundreds of hours of learning materials, tutorials, elearning, screencasts, and now… collaborating on a book! </p> |
|
|
|
308 <p>What I love about working on this kind of content is being able to listen to subject matter experts, and distil what they know in a way that is comprehensible to newcomers. </p> |
|
|
|
309 <h2>How the Guides Are Designed</h2> |
|
|
|
310 <p>One thing I always find frustrating about tutorials is that they either assume too much prior knowledge or they spend so much time in meandering details that could be summarized, or referenced as prerequisites. So the experience is either “you lost me” or “get to the point.” </p> |
|
|
|
311 <p>That’s why each guide starts by discussing the <strong>why</strong> and then moves into the step-by-step <strong>how</strong>.</p> |
|
|
|
312 <ul> <li>First, we set the stage with the scenario or problem to solve. For example, there’s a guide on creating an area on the site where premium content should only be available for logged-in users. Providing a scenario helps the reader understand the benefits in a real-world context. </li> <li>Next we establish the outcomes. This gives the reader a promise that at the end of the tutorial they would have specific tangible outcomes and learning outcomes. </li> <li>Then we explain the prerequisites. These might be assumed conditions or configurations. This reduces the need to explain everything because we can refer to other guides, or official documentation if needed. </li> <li>After that, the procedures are chunked into steps with numbered tasks. </li> <li>To help learners expand their newfound knowledge, we list out recommended next steps for readers to continue their learning journey.</li> </ul> |
|
|
|
313 <p>Along the way, steps include “expected outcomes” so we can make sure people are on the right track. After creating and testing so much classroom learning material, I’ve always been surprised at just how lost learners can get. Having check-points along the way helps people know “If you don’t see that, you’re on the wrong track, turn back!” </p> |
|
|
|
314 <h2>Distilling Knowledge From Subject Matter Experts</h2> |
|
|
|
315 <p>The guides cover topics from installing, to extending, configuring and troubleshooting. We’ve even included a guide to help you make a business out of selling TYPO3. </p> |
|
|
|
316 <p>We consulted with subject matter experts along the way, and each guide has undergone comprehensive technical reviews and testing. </p> |
|
|
|
317 <p>Mathias Bolt Lesniak and Benni Mack determined the topics for the guides. There are many more topics and we hope to keep writing guides beyond the release of the book, to create a treasure trove of material for the community to use.</p> |
|
|
|
318 <p>Of course, there is more than one way to do things with TYPO3, so the guides only present one method. Most of the guides also discuss “things to consider.” There’s always more than one way to do things, so we weigh pros and cons, and if it’s needed, we explain why we went with a certain approach. Usually it’s for the benefit of the first time learner to have a simple and clear practical exercise. We try to point users to other ways of doing things, best practice and alternative choice. </p> |
|
|
|
319 <h2>What Happens Next?</h2> |
|
|
|
320 <p>We’ve now handed all draft content over to <a href="https://www.apress.com/de" target="_blank" rel="noreferrer">Apress</a> for the next series of steps in book production. We’re aiming to produce in hardcopy and ebook format. The next thing that happens is the production workflow which involves copyediting, proofreading, typesetting and layout.</p> |
|
|
|
321 ]]> |
|
|
|
322 </content:encoded> |
|
|
|
323 |
|
|
|
324 |
|
|
|
325 <category>Association</category> |
|
|
|
326 |
|
|
|
327 <category>TYPO3 CMS</category> |
|
|
|
328 |
|
|
|
329 |
|
|
|
330 </item> |
|
|
|
331 |
|
|
|
332 <item> |
|
|
|
333 <guid isPermaLink="false">news-2081</guid> |
|
|
|
334 <pubDate> |
|
|
|
335 Mon, 28 Sep 2020 18:24:46 +0200 |
|
|
|
336 </pubDate> |
|
|
|
337 <title>Postcards from TechSummer 2020 |
|
|
|
338 </title> |
|
|
|
339 <link> |
|
|
|
340 |
|
|
|
341 https://typo3.org/article/postcards-from-techsummer-2020 |
|
|
|
342 |
|
|
|
343 </link> |
|
|
|
344 <description>Here’s a round-up of impressions from attendees of TechSummer 2020.</description> |
|
|
|
345 <content:encoded> |
|
|
|
346 <![CDATA[ |
|
|
|
347 <ul> <li>Check out the site <a href="https://techsummer20.typo3.com/events" target="_blank" rel="noreferrer">TechSummer 2020</a> for a full list of talks. </li> <li>Videos: <a href="https://www.youtube.com/watch?list=PLhGkM_v-ECnQKeeG2iJnlK50gZtggHEIo&v=UaldHaO1KVU&feature=emb_title" target="_blank" rel="noreferrer">T3OCE 2020 Day 1</a>. Videos from the Saturday are available on YouTube. </li> </ul> |
|
|
|
348 <p>Well done to the organizing teams for putting together this fab event and even coordinating this event remotely.</p> |
|
|
|
349 ]]> |
|
|
|
350 </content:encoded> |
|
|
|
351 |
|
|
|
352 |
|
|
|
353 <category>Community</category> |
|
|
|
354 |
|
|
|
355 |
|
|
|
356 </item> |
|
|
|
357 |
|
|
|
358 <item> |
|
|
|
359 <guid isPermaLink="false">news-2079</guid> |
|
|
|
360 <pubDate> |
|
|
|
361 Tue, 08 Sep 2020 08:09:00 +0200 |
|
|
|
362 </pubDate> |
|
|
|
363 <title>TYPO3 10.4.7 / TYPO3 10.4.8 and 9.5.21 maintenance releases published |
|
|
|
364 </title> |
|
|
|
365 <link> |
|
|
|
366 |
|
|
|
367 https://typo3.org/article/typo3-1047-and-9521-maintenance-releases-published |
|
|
|
368 |
|
|
|
369 </link> |
|
|
|
370 <description></description> |
|
|
|
371 <content:encoded> |
|
|
|
372 <![CDATA[ |
|
|
|
373 <p>The versions 10.4.7 and 9.5.21 of the TYPO3 Enterprise Content Management System have just been released.</p> |
|
|
|
374 <p>The following TYPO3 updates have been released:</p> |
|
|
|
375 <ul> <li>TYPO3 10.4.7 LTS</li> <li>TYPO3 9.5.21 LTS</li> </ul> |
|
|
|
376 <p>Both versions are maintenance releases only.</p> |
|
|
|
377 <p class="alert alert-warning"><strong>Update September 10, 2020<br /> Further release of TYPO3 v10.4.8 LTS affecting composer-based installations</strong><br /> <br /> We've released another TYPO3 v10 release on Thursday, September 10, 2020 – TYPO3 v10.4.8 LTS.<br /> <br /> It seemed like not every TYPO3 user could update to the latest TYPO3 v10 version due to issues regarding resolving dependencies with Symfony 4 (which were accidentally raised to Symfony 5 due to a dependency-of-a-dependency issue). For this reason, we've created an <a href="https://packagist.org/packages/typo3/symfony-psr-event-dispatcher-adapter" target="_blank" rel="noreferrer">intermediate package</a> which is compatible with Symfony 4 + 5. We've included this in TYPO3 v10.4.8 now, so everybody who is using TYPO3 v10 with composer can safely upgrade now. <br /> <br /> TYPO3 installations in non-composer-mode ("zip download") and all TYPO3 v9 versions are <strong>NOT</strong> affected!</p> |
|
|
|
378 <h3>Further upgrade instructions</h3> |
|
|
|
379 <p class="alert alert-success">No database upgrades are required for these maintenance releases.</p> |
|
|
|
380 <h3><br /> Download</h3> |
|
|
|
381 <p>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:</p> |
|
|
|
382 <ul> <li><a href="https://get.typo3.org/release-notes/10.4.7" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/10.4.7</a></li> <li><a href="https://get.typo3.org/release-notes/9.5.21" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/9.5.21</a></li> </ul> |
|
|
|
383 ]]> |
|
|
|
384 </content:encoded> |
|
|
|
385 |
|
|
|
386 |
|
|
|
387 <category>Development</category> |
|
|
|
388 |
|
|
|
389 <category>TYPO3 CMS</category> |
|
|
|
390 |
|
|
|
391 |
|
|
|
392 </item> |
|
|
|
393 |
|
|
|
394 <item> |
|
|
|
395 <guid isPermaLink="false">news-2076</guid> |
|
|
|
396 <pubDate> |
|
|
|
397 Thu, 20 Aug 2020 08:27:59 +0200 |
|
|
|
398 </pubDate> |
|
|
|
399 <title>Frontend Editing—Planning the Next Major Version |
|
|
|
400 </title> |
|
|
|
401 <link> |
|
|
|
402 |
|
|
|
403 https://typo3.org/article/frontend-editing-planning-the-next-major-version |
|
|
|
404 |
|
|
|
405 </link> |
|
|
|
406 <description>After more than 50 releases, it is time to plan the next big step for Frontend Editing in TYPO3. A lot has happened, both in TYPO3 and in other CMSs. What will version 2.0 look like?</description> |
|
|
|
407 <content:encoded> |
|
|
|
408 <![CDATA[ |
|
|
|
409 <p>In June 2020, I met with a group of people from the TYPO3 community to brainstorm about version 2.0 of the <a href="https://extensions.typo3.org/extension/frontend_editing/" target="_blank" rel="noreferrer">Frontend Editing</a> extension. I presented my thoughts and we added items to a wish list. We also set up a working group that will help with testing, ideas, and maybe development. Feel free to join.</p> |
|
|
|
410 <p><a href="https://typo3.slack.com/archives/C9WGPPKK9" target="_blank" class="btn btn-primary" rel="noreferrer">Join #frontend_editing on TYPO3 Slack</a> <a href="https://github.com/FriendsOfTYPO3/frontend_editing" target="_blank" class="btn btn-primary" rel="noreferrer">Join the Project on Github</a></p> |
|
|
|
411 <p>A major release is the time for breaking changes. Support for TYPO3 v8 will be dropped and the code cleaned up, but there was also much positivity around <strong>moving the functionality into the backend—a development time-saver, but also a way to bring the user interface closer to the TYPO3 standard</strong>.</p> |
|
|
|
412 <p>Nobody knows the exact 2.0 change list yet, but the plan is to first make the big changes and later add new features in minor versions. Maybe we’ll see a 2.0 release around New Year.</p> |
|
|
|
413 <h2>Current State and Road Ahead</h2> |
|
|
|
414 <p>Developing the Frontend Editing extension is a journey of discovery. It is now 18 months since I published my first release as the new project lead. My focus has been bugs, speed, and user experience. My perspective: <strong>We have production-ready Frontend Editing today, but we’re only at the first milestone on a much longer journey.</strong></p> |
|
|
|
415 <p>Some of the things that make TYPO3 so great—the clear data/view separation and Fluid templates—is also making it hard to give frontend editing a real plug-and-play feel. You have to manually configure your templates for Frontend Editing. That is because the templates don’t know where record and field property data is coming from.</p> |
|
|
|
416 <p>Frontend-editing-approaches like Gutenberg have been released for Wordpress and Drupal, but <strong>the Gutenberg approach takes a shortcut we will not do in TYPO3: All the editable content is placed within a single rich-text-editing field, mixing both data and view information. It removes the benefit of structured data, affecting scalability, maintainability, performance, etc.</strong> (You might remember a related problem with <a href="https://extensions.typo3.org/extension/templavoila/" target="_blank" rel="noreferrer">TemplaVoilà</a> a number of years back.)</p> |
|
|
|
417 <p>The solution is out there, and luckily some great people in the <a href="/community/teams/typo3-development/initiatives/structured-content?type=100">Structured Content Initiative</a> are chewing on related problems. Maybe the solution is value objects, extending Fluid, or implementing non-intrusive template pre-processing? Who knows.</p> |
|
|
|
418 <h2>Primary Objectives: Move to Backend, Maintenance, and Tests</h2> |
|
|
|
419 <p>You have to break some eggs to make an omelet. Frontend Editing 2.0 will do just that. The first release has three primary objectives that will shift around on a number of things, but also prevent bugs and lower the maintenance effort:</p> |
|
|
|
420 <h3>Frontend Editing in a Backend Module</h3> |
|
|
|
421 <p><strong>Imagine the View module with editing capabilities. Over the last few releases, the responsive TYPO3 backend has made it possible to hide almost the entire user interface.</strong> To see an entire frontend page, you can easily minimize the module list and hide the page tree. </p> |
|
|
|
422 <p>This gives more benefits:</p> |
|
|
|
423 <ul> <li>No need to maintain a separate page tree implementation.</li> <li>Using existing user interface design and conventions.</li> <li>Fewer custom resources and faster page loads.</li> <li>Narrowing down development focus to making the best possible editing experience.</li> </ul> |
|
|
|
424 <h3>Code Cleanup</h3> |
|
|
|
425 <p>Leaner code is both faster to execute and easier to maintain. Removing support for TYPO3 v8 and moving into the Backend does some of the job, but splitting up class methods (some spanning 200 lines of code) will mean easier contribution and debugging too.</p> |
|
|
|
426 <h3>Improved Test Coverage and CI Workflow</h3> |
|
|
|
427 <p>Frontend Editing hooks into the TYPO3 API in places few other extensions do. There is a lot of back and forth involved in adding the frontend editor’s bit of magic. This meandering control flow easily introduces bugs. </p> |
|
|
|
428 <p>The cleaner code will make it easier to write unit and functional tests for the extension. With a new and more comprehensive testing regime in the CI workflow, problems will be easier to detect and fix. The result: <strong>Better stability and less time spent fixing bugs of unclear origin.</strong></p> |
|
|
|
429 <h2>More From the Wish List—Contributions Welcome</h2> |
|
|
|
430 <p><strong>My biggest wish is to increase the number of contributors and contributions to Frontend Editing. Contribution could mean anything from writing code, to testing, to sponsorship. You should not hesitate to make contact</strong> in the <a href="https://typo3.slack.com/archives/C9WGPPKK9" target="_blank" rel="noreferrer">#frontend_editing </a>channel in TYPO3 Slack.</p> |
|
|
|
431 <p>These are some of the things on the wish list:</p> |
|
|
|
432 <ul> <li><strong>Reduce perceived load time</strong> by showing progress and active task information on the load screen.</li> <li><strong>Make Frontend Editing work out of the box</strong>, without modifying templates.</li> <li><strong>Revisit content saving</strong>. Changes are currently stored temporarily in JavaScript until you click the save button.</li> <li><strong>Reduce the need for mouse movement</strong> when editing. <ul> <li>Evaluate the use of drag-and-drop vs. a +-button like in Gutenberg.</li> <li>Move text styling buttons closer to the text being edited.</li> </ul> </li> <li><strong>More closely connect fields to available style choices</strong>. For example, header text alignment is stored in a separate database field.</li> <li><strong>Drag and drop images </strong>to add them to the page.</li> </ul> |
|
|
|
433 <p>Do you have more ideas? <a href="https://github.com/FriendsOfTYPO3/frontend_editing/issues/new" target="_blank" rel="noreferrer">Make a feature request on Github</a> or discuss it in TYPO3 Slack.</p> |
|
|
|
434 <h2>What’s All the Fuss About Frontend Editing?</h2> |
|
|
|
435 <p>Frontend editing is an important feature for beginner editors—and decision makers. In other words: <strong>Easy onboarding makes TYPO3 easier to sell. Buyers are being told to look for it</strong>. Here’s a few examples I found when searching for CMS decision factors: </p> |
|
|
|
436 <ul> <li>“WYSIWYG (What You See Is What You Get) Editors and inline editing are basic requirements of any modern CMS platform”—Mike Johnston at <a href="https://www.cmscritic.com/7-critical-factors-when-choosing-a-cms/" target="_blank" rel="noreferrer">CMSCritic</a>.</li> <li>“You need everyone in your operation who will be working with the system to have enough of an understanding of how it works to do their jobs, particularly such often-used areas as inline editing.”—<a href="https://resources.bayshoresolutions.com/blog/factors-when-choosing-the-best-content-management-system" target="_blank" rel="noreferrer">Bayshore Solutions</a>.</li> </ul> |
|
|
|
437 <p>You may argue that ease of use isn’t everything, and I agree, it’s not. However, “CMS vendors of course trumpet their software’s ease of use.” (<a href="http://www.cmsmyth.com/2012/01/the-ease-of-use-myth/" target="_blank" rel="noreferrer">Jeff Cram</a> at CMS Myth.) We can’t expect clients to always see beyond the marketing fluff. The popularity in other CMSs shows that it's a useful editing feature, and not just a marketing checkbox. It's time to make our favorite CMS even more editor-friendly.</p> |
|
|
|
438 <p><strong>We don’t own the definition of “easy”—and some editors don’t need more than click-and-write—even though the project needs an enterprise CMS.</strong></p> |
|
|
|
439 <p><a href="https://typo3.slack.com/archives/C9WGPPKK9" target="_blank" class="btn btn-primary" rel="noreferrer">Join #frontend_editing on TYPO3 Slack</a> <a href="https://github.com/FriendsOfTYPO3/frontend_editing" target="_blank" class="btn btn-primary" rel="noreferrer">Join the Project on Github</a></p> |
|
|
|
440 <p> <br /> Thanks to everyone who helped review this article. Especially Paul Hansen, who also proofread it.</p> |
|
|
|
441 ]]> |
|
|
|
442 </content:encoded> |
|
|
|
443 |
|
|
|
444 |
|
|
|
445 <category>Development</category> |
|
|
|
446 |
|
|
|
447 <category>Community</category> |
|
|
|
448 |
|
|
|
449 |
|
|
|
450 </item> |
|
|
|
451 |
|
|
|
452 <item> |
|
|
|
453 <guid isPermaLink="false">news-2075</guid> |
|
|
|
454 <pubDate> |
|
|
|
455 Wed, 12 Aug 2020 09:00:00 +0200 |
|
|
|
456 </pubDate> |
|
|
|
457 <title>TYPO3 Joins PHP-FIG as a Member Project |
|
|
|
458 </title> |
|
|
|
459 <link> |
|
|
|
460 |
|
|
|
461 https://typo3.org/article/typo3-joins-php-fig-as-a-member-project |
|
|
|
462 |
|
|
|
463 </link> |
|
|
|
464 <description>TYPO3 has officially joined PHP-FIG as a member project, represented by TYPO3 Project Lead Benni Mack. </description> |
|
|
|
465 <content:encoded> |
|
|
|
466 <![CDATA[ |
|
|
|
467 <p>Benni Mack, <a href="https://b13.com/" target="_blank" rel="noreferrer">CTO of b13</a> and <a href="/community/teams/typo3-development?type=100">TYPO3 Core Project Lead</a> said: </p> |
|
|
|
468 <blockquote><p>“TYPO3 has been benefiting from PHP-FIG's standard recommendations for over 5 years, and participating as an active member in PHP-FIG was long overdue, in helping to shape the future of interoperability of PHP frameworks and Content Management Systems.”</p></blockquote> |
|
|
|
469 <p>The official announcement was posted by PHP-FIG 25 July 2020:</p> |
|
|
|
470 ]]> |
|
|
|
471 </content:encoded> |
|
|
|
472 |
|
|
|
473 |
|
|
|
474 <category>Development</category> |
|
|
|
475 |
|
|
|
476 <category>TYPO3 CMS</category> |
|
|
|
477 |
|
|
|
478 |
|
|
|
479 </item> |
|
|
|
480 |
|
|
|
481 <item> |
|
|
|
482 <guid isPermaLink="false">news-2074</guid> |
|
|
|
483 <pubDate> |
|
|
|
484 Tue, 11 Aug 2020 08:25:00 +0200 |
|
|
|
485 </pubDate> |
|
|
|
486 <title>TYPO3 in Every Country: The TYPO3 Mentorship Program |
|
|
|
487 </title> |
|
|
|
488 <link> |
|
|
|
489 |
|
|
|
490 https://typo3.org/article/typo3-in-every-country-the-typo3-mentorship-program |
|
|
|
491 |
|
|
|
492 </link> |
|
|
|
493 <description>A learning opportunity for the global web development community is about to start. The first six TYPO3 students come from countries in Latin America and Africa.</description> |
|
|
|
494 <content:encoded> |
|
|
|
495 <![CDATA[ |
|
|
|
496 <p>Today, every country—rich and poor—needs digitalization. Government administration, education, and every business rely on software and need to present themselves online. The Covid-19 crisis has only made this more urgent.</p> |
|
|
|
497 <h2>A Life-Changing Opportunity with TYPO3</h2> |
|
|
|
498 <p>Choosing a career in web programming is a great way to earn a decent living and join a global community of like-minded people. I have seen how becoming a web developer can be a life-changing opportunity for youngsters in developing countries. </p> |
|
|
|
499 <p>In the TYPO3 community, we are working with the most competitive open source CMS. It is flexible, performant, and secure, and the best choice for many sectors, from government and universities to corporations and companies of all kinds. Yet, TYPO3 remains little known and used in many parts of the world. Changing that will be a benefit to everyone.</p> |
|
|
|
500 <h2>A Journey to National Capacity Building</h2> |
|
|
|
501 <p>Facing this global opportunity, the TYPO3 Association went where TYPO3 has never gone before. Two years ago we started a journey that soon found its goal: To bring TYPO3 and the TYPO3 community into new parts of the world. </p> |
|
|
|
502 <p>It started in Africa, and little by little it evolved. With the creation of the TYPO3 Community Expansion Committee, and later meeting with web development communities in several African countries, the assistance for the <a href="https://www.gov.rw" target="_blank" rel="noreferrer">government of Rwanda</a> was the high-point thus far. Our collaboration led to their strategic adoption of TYPO3 and national capacity building.</p> |
|
|
|
503 <p>We have continued to reach out to more and more developers and web agencies from different countries. Now, it’s possible to take an important new step, the one that we are happy to announce now.</p> |
|
|
|
504 <h2>Introducing the TYPO3 Mentorship Program</h2> |
|
|
|
505 <p>The International TYPO3 Mentorship Program will introduce new web developers to TYPO3, and help them start using it through a direct, personalized, one-to-one learning process facilitated by experienced mentors from our community. It is targeted at web developers from countries where TYPO3 does not have yet a strong presence. The main goal is to expand TYPO3, the developer community, and the professional CMS market.</p> |
|
|
|
506 <p>Through the course of three months of weekly mentoring sessions the TYPO3 mentees will learn how to build their own TYPO3 website and start using it professionally in their current companies or as freelancers.</p> |
|
|
|
507 <p>From a basic understanding of TYPO3, they will be able to develop their knowledge and to participate in the community, asking questions and sharing their knowledge locally and globally. </p> |
|
|
|
508 <h2>Starting in Africa and Latin America</h2> |
|
|
|
509 <p>The program has been prepared over the past two months. We have reached out to development communities in Africa and Latin America, and raised their interest in TYPO3. We have collected mentee applications and performed interviews to understand their experience and motivation. </p> |
|
|
|
510 <p>Today, we have confirmed participants from Chile, Cuba, Zimbabwe, Rwanda, Benin, and South Africa. Kenya, Uganda, Nigeria, Ethiopia, Ivory Coast, Botswana, and Burundi are countries from which we expect the next wave of registrations. Our outreach activities continue. </p> |
|
|
|
511 <p>Please <a href="javascript:linkTo_UnCryptMailto(%27nbjmup%2Bebojfm%5C%2FipnpspefboAuzqp4%5C%2Fpsh%27);">contact us</a> if you can help to establish a dialogue to promote TYPO3 in other countries. </p> |
|
|
|
512 <h2>Professional TYPO3 Mentors, World-Wide</h2> |
|
|
|
513 <p>We have also found a first group of knowledgeable mentors. They are TYPO3 developers with experience as trainers, teachers, mentors, and coaches. They share the mentees’ diverse international background and come from five different countries. Because we plan for the program to expand, we will need more people as mentors too. If you are interested in becoming one, please reach out to us.</p> |
|
|
|
514 <p>The mentors who commit to the program will have to dedicate at least 2 hours per week for each mentee for 3 months. The effort will bring new people into the community and make TYPO3 spread to new countries. </p> |
|
|
|
515 <h2>Help Expand the Mentoring Budget</h2> |
|
|
|
516 <p>The mentors will be financially compensated, but the current budget is quite limited, allowing only 8 mentor-mentee pairs to be supported through the program. Since we already have a larger number of interested mentees, we will have to find solutions that will allow more people to start their path to learn TYPO3. In order to achieve this, we look for direct financial support from our community. If you are interested in sponsoring the program, please <a href="javascript:linkTo_UnCryptMailto(%27nbjmup%2Bebojfm%5C%2FipnpspefboAuzqp4%5C%2Fpsh%27);">contact us</a> for more information.</p> |
|
|
|
517 <p>We already received the generous support of <a href="https://www.skilldisplay.eu" target="_blank" rel="noreferrer">SkillDisplay</a>. They have offered their platform as a place to organize the learning process and to keep track of progress.</p> |
|
|
|
518 <h2>Coordinated by an International Group</h2> |
|
|
|
519 <p>The committee that has coordinated and organized the activities so far consists of </p> |
|
|
|
520 <ul> <li>Olivier Dobberkau</li> <li>Mathias Bolt Lesniak</li> <li>Tymoteusz Motylewski</li> <li>Alina Fleser</li> <li>Rachel Foucard</li> <li>Daniel Homorodean</li> </ul> |
|
|
|
521 <p>As with the TYPO3 Community Expansion Committee itself, the group is open to more contributors, especially in the activities involving the promotion of TYPO3 in new countries. </p> |
|
|
|
522 <p>We will keep you posted as the program evolves, with summaries in the TYPO3 newsletter and a new dedicated presentation page on typo3.org.</p> |
|
|
|
523 <p>If you would like to get involved in any way, feel free to reach out to me directly at <a href="javascript:linkTo_UnCryptMailto(%27nbjmup%2Bebojfm%5C%2FipnpspefboAuzqp4%5C%2Fpsh%27);">daniel.homorodean(at)typo3.org</a>.</p> |
|
|
|
524 <p> <br /> Copyediting: Mathias Bolt Lesniak • Proofreading: Tony Lush</p> |
|
|
|
525 ]]> |
|
|
|
526 </content:encoded> |
|
|
|
527 |
|
|
|
528 |
|
|
|
529 <category>Community</category> |
|
|
|
530 |
|
|
|
531 <category>Association</category> |
|
|
|
532 |
|
|
|
533 <category>TYPO3 CMS</category> |
|
|
|
534 |
|
|
|
535 |
|
|
|
536 </item> |
|
|
|
537 |
|
|
|
538 <item> |
|
|
|
539 <guid isPermaLink="false">news-2072</guid> |
|
|
|
540 <pubDate> |
|
|
|
541 Mon, 10 Aug 2020 20:39:14 +0200 |
|
|
|
542 </pubDate> |
|
|
|
543 <title>TYPO3 Joins CMS Experts Group |
|
|
|
544 </title> |
|
|
|
545 <link> |
|
|
|
546 |
|
|
|
547 https://typo3.org/article/typo3-joins-cms-experts-group |
|
|
|
548 |
|
|
|
549 </link> |
|
|
|
550 <description>For an open source community-driven project like our CMS, it is important to network and exchange ideas with the industry at large. That’s why the TYPO3 Association is joining CMS analysts, experts, and other vendors in Boye & Co’s CMS Experts Group.</description> |
|
|
|
551 <content:encoded> |
|
|
|
552 <![CDATA[ |
|
|
|
553 <p>Active with meetings in both Europe and North America, the group is a forum created to set the agenda for future industry developments, provide feedback, and share thoughts and ideas around content management.</p> |
|
|
|
554 ]]> |
|
|
|
555 </content:encoded> |
|
|
|
556 |
|
|
|
557 |
|
|
|
558 <category>Community</category> |
|
|
|
559 |
|
|
|
560 <category>Association</category> |
|
|
|
561 |
|
|
|
562 |
|
|
|
563 </item> |
|
|
|
564 |
|
|
|
565 <item> |
|
|
|
566 <guid isPermaLink="false">news-2071</guid> |
|
|
|
567 <pubDate> |
|
|
|
568 Wed, 05 Aug 2020 20:59:48 +0200 |
|
|
|
569 </pubDate> |
|
|
|
570 <title>TYPO3 for Everyone: Join the Remote Accessibility Sprint 2020 |
|
|
|
571 </title> |
|
|
|
572 <link> |
|
|
|
573 |
|
|
|
574 https://typo3.org/article/typo3-for-everyone-join-the-remote-accessibility-sprint-2020 |
|
|
|
575 |
|
|
|
576 </link> |
|
|
|
577 <description>Making TYPO3 accessible is a mission to make the web a little bit better! You can help us with your development and UI/UX skills, accessibility know-how or your documentation or testing experience. The Accessibility Sprint will be an open remote sprint and everyone is welcome to join! </description> |
|
|
|
578 <content:encoded> |
|
|
|
579 <![CDATA[ |
|
|
|
580 <p><strong>Where:</strong> Online! The event will be remote due to the current COVID-19 situation. <br /> <strong>When:</strong> It will take place from October 21–23, 2020. </p> |
|
|
|
581 <p><a href="https://www.eventbrite.com/e/typo3-accessibility-sprint-tickets-114271980570" target="_blank" class="btn btn-primary" rel="noreferrer">Register as a Participant</a></p> |
|
|
|
582 <h3>Who is Organizing?</h3> |
|
|
|
583 <p>The event is organized by the <a href="/community/teams/accessibility?type=100">TYPO3 Accessibility Initiative</a>. The initiative was reinitiated in September, 2019 by members of the TYPO3 community. We provide information on accessibility and give the opportunity to discuss accessibility topics on a regular basis in our <a href="/community/meet/how-to-use-slack-in-the-typo3-community?type=100">TYPO3 Slack</a> channel <a href="https://typo3.slack.com/messages/C108Q9E2C" target="_blank" rel="noreferrer">#cig-accessibility</a> and the monthly TYPO3 Accessibility Hour. </p> |
|
|
|
584 <p>Our goal is to make TYPO3 accessible and improve the knowledge on accessibility for other TYPO3 developers. </p> |
|
|
|
585 <h3>Current Status of TYPO3 Accessibility</h3> |
|
|
|
586 <p>While it is possible to use TYPO3 to create accessible websites, the TYPO3 editing interface is missing support for accessibility in some important places. As a starting point for the initiative, the TYPO3 pagetree was improved during the TYPO3 Initiative Week 2019. It now fully supports keyboard navigation following the best practices described in WAI-ARIA Authoring Practices 1.1. </p> |
|
|
|
587 <p>Since then, a <a href="/article/typo3-accessibility-initiative-needs-your-feedback?type=100">user survey</a> helped to get feedback from users and discover which parts of the TYPO3 backend were lacking in accessibility. As a result, multiple issues have been documented and some of them have already been resolved. There is <a href="https://forge.typo3.org/projects/typo3cms-core/issues?query_id=682" target="_blank" rel="noreferrer">a public custom query to show accessibility issues</a> on Forge, the TYPO3 core issue tracker. </p> |
|
|
|
588 <h3>Ideas & Goals for the Accessibility Sprint</h3> |
|
|
|
589 <p>We want to raise awareness for accessibility in TYPO3. Making TYPO3 more accessible will help every user of TYPO3, and is also a requirement for customers in the public sector, such as universities and governments.</p> |
|
|
|
590 <p>During the sprint we will try to feature live tests by people with disabilities to get an insight into the major issues.</p> |
|
|
|
591 <p>For TYPO3 itself, we will focus on several parts, and we plan to:</p> |
|
|
|
592 <ul> <li>Create developer guidelines for future improvements and education.</li> <li>Enhance consistency with TYPO3 backend components, such as Buttons and Tabs.</li> <li>Improve accessibility for the most important parts of the TYPO3 backend.</li> <li>Create accessibility tests integrated in the TYPO3 Core Bamboo testing suites to ensure the accessibility for future development.</li> <li>Create issues in Forge for all accessibility problems discovered during the sprint to have a collection of improvements to make after the sprint.</li> </ul> |
|
|
|
593 <h3>You’re Welcome to Join Us!</h3> |
|
|
|
594 <p>Join our sprint to make TYPO3 better for everyone, October 21–23, 2020. </p> |
|
|
|
595 <p><a href="https://www.eventbrite.com/e/typo3-accessibility-sprint-tickets-114271980570" target="_blank" class="btn btn-primary" rel="noreferrer">Register as a Participant</a></p> |
|
|
|
596 ]]> |
|
|
|
597 </content:encoded> |
|
|
|
598 |
|
|
|
599 |
|
|
|
600 <category>Community</category> |
|
|
|
601 |
|
|
|
602 <category>TYPO3 CMS</category> |
|
|
|
603 |
|
|
|
604 |
|
|
|
605 </item> |
|
|
|
606 |
|
|
|
607 <item> |
|
|
|
608 <guid isPermaLink="false">news-2069</guid> |
|
|
|
609 <pubDate> |
|
|
|
610 Tue, 28 Jul 2020 11:05:00 +0200 |
|
|
|
611 </pubDate> |
|
|
|
612 <title>TYPO3 10.4.6 and 9.5.20 security releases published |
|
|
|
613 </title> |
|
|
|
614 <link> |
|
|
|
615 |
|
|
|
616 https://typo3.org/article/typo3-1046-and-9520-security-releases-published |
|
|
|
617 |
|
|
|
618 </link> |
|
|
|
619 <description>The versions 10.4.6 and 9.5.20 of the TYPO3 Enterprise Content Management System have just been released.</description> |
|
|
|
620 <content:encoded> |
|
|
|
621 <![CDATA[ |
|
|
|
622 <p>The following TYPO3 updates have been released:</p> |
|
|
|
623 <ul> <li>TYPO3 10.4.6 LTS</li> <li>TYPO3 9.5.20 LTS</li> </ul> |
|
|
|
624 <p>Both versions are security releases and contain important security fixes - read the corresponding Security Advisories here:</p> |
|
|
|
625 <ul> <li><a href="https://typo3.org/security/advisory/typo3-core-sa-2020-007" target="_blank">https://typo3.org/security/advisory/typo3-core-sa-2020-007</a></li> <li><a href="https://typo3.org/security/advisory/typo3-core-sa-2020-008" target="_blank">https://typo3.org/security/advisory/typo3-core-sa-2020-008</a></li> </ul> |
|
|
|
626 <h3>Further upgrade instructions</h3> |
|
|
|
627 <p>No database upgrades are required for these maintenance releases.</p> |
|
|
|
628 <h3>Download</h3> |
|
|
|
629 <p>TYPO3 can be installed in various ways. For example the traditional way by using the source package at <a href="https://get.typo3.org" target="_blank" rel="noreferrer">get.typo3.org</a> 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:</p> |
|
|
|
630 <ul> <li><a href="https://get.typo3.org/release-notes/10.4.6" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/10.4.6</a></li> <li><a href="https://get.typo3.org/release-notes/9.5.20" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/9.5.20</a></li> </ul> |
|
|
|
631 ]]> |
|
|
|
632 </content:encoded> |
|
|
|
633 |
|
|
|
634 |
|
|
|
635 <category>Development</category> |
|
|
|
636 |
|
|
|
637 |
|
|
|
638 </item> |
|
|
|
639 |
|
|
|
640 <item> |
|
|
|
641 <guid isPermaLink="false">news-2064</guid> |
|
|
|
642 <pubDate> |
|
|
|
643 Sun, 26 Jul 2020 15:41:00 +0200 |
|
|
|
644 </pubDate> |
|
|
|
645 <title>Structured Content Initiative—What Happened in May–June 2020? |
|
|
|
646 </title> |
|
|
|
647 <link> |
|
|
|
648 |
|
|
|
649 https://typo3.org/article/structured-content-initiative-what-happened-in-may-june-2020 |
|
|
|
650 |
|
|
|
651 </link> |
|
|
|
652 <description>A lot of things have happened since May 2020, we have made progress on UX concepts, on content block creation, and on rendering strategies. Here is some important information about our latest achievements.</description> |
|
|
|
653 <content:encoded> |
|
|
|
654 <![CDATA[ |
|
|
|
655 <p>The <a href="/community/teams/typo3-development/initiatives/structured-content?type=100">Structured Content Initiative</a> is the core <a href="/community/teams/typo3-development/initiatives?type=100">Strategic Initiative</a> focused on improving the content editing user experience in TYPO3 CMS. Read <a href="/article/structured-content-initiative-what-happened-in-february?type=100">our last update</a> to learn more about what we’ve been working on. </p> |
|
|
|
656 <p><a href="https://my.typo3.org/about-mytypo3org/slack" target="_blank" rel="noreferrer">Connect to TYPO3 Slack</a> and join us in the #cig-structuredcontent channel.</p> |
|
|
|
657 <h2>Two New Surveys</h2> |
|
|
|
658 <p>If you have not yet answered these two new surveys, benefit from a quiet moment this summer to use 5 minutes of your valuable time:</p> |
|
|
|
659 <ul> <li>This survey is about the “mobile first” user experience: <a href="https://forms.gle/DqT6E3tGwCt8ktX16" target="_blank" rel="noreferrer">https://forms.gle/DqT6E3tGwCt8ktX16</a></li> <li>This survey is focused on the “view in the frontend” action: <a href="https://forms.gle/WE86ZaPp4aibuHsc6" target="_blank" rel="noreferrer">https://forms.gle/WE86ZaPp4aibuHsc6</a></li> </ul> |
|
|
|
660 <h2>Not in Our Scope, but on Our Path</h2> |
|
|
|
661 <p>During several workshops on the new backend interface of the future page module, we agreed that the first two steps required to reach this module (choose the module, then select the page) needed to be improved.</p> |
|
|
|
662 <p>Indeed, the module bar and the page tree bar are the two key elements of the TYPO3 backend interface, and it is essential for almost all modules. Among the user responses to our first surveys, many refer to usability or accessibility problems with these first two necessary clicks. We have therefore worked on these two areas with the kind collaboration of the members of the Accessibility initiative. The objectives of the modifications we are going to propose are:</p> |
|
|
|
663 <ul> <li>The actions have to be accessible to all.</li> <li>Interfaces must be mobile first, or at least mobile friendly.</li> </ul> |
|
|
|
664 <h2>Approved Concepts of the Next Module Page</h2> |
|
|
|
665 <p>The following concepts have been approved by the UX Working Group, which means that they will be implemented and tested. If the usability testing of these changes requires adaptations, they will be integrated following the direction of these initial concepts.</p> |
|
|
|
666 <h3>Three Tips: Simplify, Simplify, Simplify (J.Nielsen)</h3> |
|
|
|
667 <p>Having a simplified page module is an important first step because if we add a grid system, we will also add a lot of visual information and interactions.</p> |
|
|
|
668 <p>One of the important problems to solve is that the current backend page module is still very different from the frontend because of a lot of useless information and design. Even if it won’t replace a frontend editing solution, it has to be as similar as possible to the frontend, so that we can find the content we want to change very easily.</p> |
|
|
|
669 <h3>Adding New Content to the Page, or How to Set the Table Efficiently</h3> |
|
|
|
670 <p>Imagine you have to set the table. You have to put a glass in front of your plate:</p> |
|
|
|
671 <ol> <li>You open the cupboard.</li> <li>You choose the glass that best suits what you want to drink.</li> <li>You take it and put it on the table, where it should be.</li> <li>When you have dinner, you will fill it with the drink of your choice.</li> </ol> |
|
|
|
672 <p>Today, with TYPO3, here's how you should do it:</p> |
|
|
|
673 <ol> <li>You touch the place where you want to put your glass …</li> <li>A cupboard containing glasses appears in place of your table</li> <li>You choose the glass that best suits what you want to drink</li> <li>You have to fill it before you put it down! so this involves that: <ol> <li>You open the fridge, </li> <li>You take the drink, </li> <li>You fill the glass,</li> <li>You put the drink back in the fridge, and only then,</li> </ol> </li> <li>You can put the glass down</li> </ol> |
|
|
|
674 <p>We will therefore allow editors to compose their pages in a much more natural way. A way close to what we want to think about when we want to add a new content block to a given position on a page: </p> |
|
|
|
675 <ol> <li>Choose the content.</li> <li>Grab it and drop it where they want to put it.</li> </ol> |
|
|
|
676 <p>Of course that means drag and drop. We were able to confirm in our last survey that drag and drop is very popular with users when this option exists. However, some users, or certain situations make drag and drop not possible, or not comfortable. For this reason, the action of adding new content will always be possible in two ways:</p> |
|
|
|
677 <ol> <li>Drag and drop:<br /> Drag the content and Drop it on the position</li> <li>Click and click:<br /> Click the content and click on the position</li> </ol> |
|
|
|
678 <p>In both cases, the mental pattern remains natural and close to a physical action when you move something (you grab the object and put it down somewhere). This ensures that the action is accessible and can be processed with a touch screen and on a reduced screen.</p> |
|
|
|
679 <h3>The “Add New Content” Button</h3> |
|
|
|
680 <p>Buttons in the TYPO3 backend are numerous. As we wrote above, the page module simplification is mandatory, because we will add new possibilities and we have to make a clean sweep before.</p> |
|
|
|
681 <p>As we will reverse the actions of adding new content, it will no longer be necessary to have a “create new content” button at each possible position in the page: that is to say, above and below each existing content. This will be an undeniable progress in the page visual simplification and will make the contents organisation understanding much more fluid.</p> |
|
|
|
682 ]]> |
|
|
|
683 </content:encoded> |
|
|
|
684 |
|
|
|
685 |
|
|
|
686 <category>Community</category> |
|
|
|
687 |
|
|
|
688 <category>TYPO3 CMS</category> |
|
|
|
689 |
|
|
|
690 |
|
|
|
691 </item> |
|
|
|
692 |
|
|
|
693 <item> |
|
|
|
694 <guid isPermaLink="false">news-2063</guid> |
|
|
|
695 <pubDate> |
|
|
|
696 Wed, 22 Jul 2020 13:16:06 +0200 |
|
|
|
697 </pubDate> |
|
|
|
698 <title>Report from the typo3.org Team 2020—Part 1 |
|
|
|
699 </title> |
|
|
|
700 <link> |
|
|
|
701 |
|
|
|
702 https://typo3.org/article/report-of-typo3org-team-2020-part-1 |
|
|
|
703 |
|
|
|
704 </link> |
|
|
|
705 <description>This is a report from The typo3.org Website Team that looks after the typo3.org website and central subdomains, such as the TYPO3 Extension Repository (TER). Our new “Remote Days” make participation even easier than before.</description> |
|
|
|
706 <content:encoded> |
|
|
|
707 <![CDATA[ |
|
|
|
708 <h2>Team Sprints / Remote Days</h2> |
|
|
|
709 <p>Like all of the TYPO3 teams and nearly the whole of humanity, we also faced the problem named COVID-19. Just before the nationwide lockdown in Germany started in March, we joined a Team Sprint organized by the Server Team.</p> |
|
|
|
710 <p>Our planned sprints for March and May were cancelled and we looked for another option to work together.</p> |
|
|
|
711 <p>In June, we started with the first Remote Day. A Remote Day is defined as a whole day to work on topics and issues, previously organized by the Team Lead and Product Owner. It goes from midnight to midnight for 24 hours. Everyone can contribute on that day, whether from Germany, India, Brazil, or anywhere else.</p> |
|
|
|
712 <p>It started quite well and we announced all Remote Days (15th of each month) until the end of the year. We hope that we will get new contributors and engage known contributors as well.</p> |
|
|
|
713 <p>If you want to contribute, look here and join: <a href="https://notes.typo3.org/2020-t3o-Remote-Days" target="_blank" rel="noreferrer">https://notes.typo3.org/2020-t3o-Remote-Days</a> </p> |
|
|
|
714 <h2>Goals</h2> |
|
|
|
715 <p>Our first goal was to upgrade our biggest project to TYPO3 v10 within a week after the CMS release: typo3.org. We succeeded and 5 days after the <a href="https://typo3.org/article/typo3-v10-lts-safe-and-sound" target="_blank">TYPO3 CMS v10 release</a> we got it running on production.</p> |
|
|
|
716 <p>Our next goals are to upgrade voting.typo3.org to v10 and create a new and modern API for TER, before upgrading it to v10 as well. We’ve already made some progress. </p> |
|
|
|
717 <p>As our main sitepackage extension t3olayout is a few years old, we want to refactor the code and improve the layout and integration for a better, faster, and more beautiful output.</p> |
|
|
|
718 <h2>my.typo3.org</h2> |
|
|
|
719 <p>Our project <a href="https://my.typo3.org/" target="_blank" rel="noreferrer">my.typo3.org</a> moved to a new website, maintained by the TYPO3 GmbH, to have a better interface with the user and member management. This is now the central hub for logging into TYPO3 sites, including a new <a href="https://shop.typo3.com/" target="_blank" rel="noreferrer">online shop for the TYPO3 community</a>. </p> |
|
|
|
720 <h2>Upcoming in the second half of 2020</h2> |
|
|
|
721 <ul> <li>Investigate the success of t3o Remote Day concept</li> <li>Upgrade voting.typo3.org to TYPO3 v10</li> <li>Create/Improve API for TYPO3 Extension Repository</li> <li>Upgrade extensions.typo3.org to v10</li> <li>Improve the t3olayout extension</li> </ul> |
|
|
|
722 <h2>How to get involved</h2> |
|
|
|
723 <ul> <li>Join the upcoming <a href="https://notes.typo3.org/2020-t3o-Remote-Days" target="_blank" rel="noreferrer">t3o Remote Day</a> on the 15th of every month. </li> <li>Get support or come say hi in our <a href="https://typo3.org/community/meet/how-to-use-slack-in-the-typo3-community" target="_blank">TYPO3 Slack channel</a> #t3o-team</li> </ul> |
|
|
|
724 <h2>Big thanks to all contributors from January 1st to June 30th</h2> |
|
|
|
725 <p>(In alphabetical order.)</p> |
|
|
|
726 <ul> <li>Stefan Busemann</li> <li>Riccardo De Contardi</li> <li>Olivier Dobberkau</li> <li>Markus Dübbert</li> <li>Simon Gilli</li> <li>Josef Glatz</li> <li>Jonas Götze</li> <li>Stephan Großberndt</li> <li>Oliver Hader</li> <li>Torben Hansen</li> <li>Marco Huber</li> <li>Johannes Kasberger</li> <li>Christian Keuerleber</li> <li>Peter Kraume</li> <li>David Lemaitre</li> <li>Mathias Bolt Lesniak</li> <li>Thomas Löffler</li> <li>Benni Mack</li> <li>Tomas Norre Mikkelsen</li> <li>Tymoteusz Motylewski</li> <li>Andreas Nedbal</li> <li>Alex Nostadt</li> <li>Sybille Peters</li> <li>Georg Ringer</li> <li>Boris Schauer</li> <li>Daniel Siepmann</li> <li>Andri Steiner</li> <li>Michael Stucki</li> </ul> |
|
|
|
727 ]]> |
|
|
|
728 </content:encoded> |
|
|
|
729 |
|
|
|
730 |
|
|
|
731 <category>Community</category> |
|
|
|
732 |
|
|
|
733 |
|
|
|
734 </item> |
|
|
|
735 |
|
|
|
736 <item> |
|
|
|
737 <guid isPermaLink="false">news-2062</guid> |
|
|
|
738 <pubDate> |
|
|
|
739 Tue, 07 Jul 2020 12:00:00 +0200 |
|
|
|
740 </pubDate> |
|
|
|
741 <title>TYPO3 10.4.5 maintenance release published |
|
|
|
742 </title> |
|
|
|
743 <link> |
|
|
|
744 |
|
|
|
745 https://typo3.org/article/typo3-1045-maintenance-release-published |
|
|
|
746 |
|
|
|
747 </link> |
|
|
|
748 <description>The version 10.4.5 of the TYPO3 Enterprise Content Management System has just been released.</description> |
|
|
|
749 <content:encoded> |
|
|
|
750 <![CDATA[ |
|
|
|
751 <p>The following TYPO3 update has been released:</p> |
|
|
|
752 <ul> <li>TYPO3 10.4.5 LTS</li> </ul> |
|
|
|
753 <p>This version is a maintenance release only.</p> |
|
|
|
754 <h3>Further upgrade instructions</h3> |
|
|
|
755 <p class="alert alert-success">No database upgrades are required for this maintenance release.</p> |
|
|
|
756 <h3>Download</h3> |
|
|
|
757 <p>TYPO3 can be installed in various ways. For example the traditional way by using the source package at <a href="https://get.typo3.org" target="_blank" rel="noreferrer">get.typo3.org</a> 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:</p> |
|
|
|
758 <ul> <li><a href="https://get.typo3.org/release-notes/10.4.5" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/10.4.5</a></li> </ul> |
|
|
|
759 ]]> |
|
|
|
760 </content:encoded> |
|
|
|
761 |
|
|
|
762 |
|
|
|
763 <category>Development</category> |
|
|
|
764 |
|
|
|
765 |
|
|
|
766 </item> |
|
|
|
767 |
|
|
|
768 <item> |
|
|
|
769 <guid isPermaLink="false">news-2056</guid> |
|
|
|
770 <pubDate> |
|
|
|
771 Tue, 30 Jun 2020 09:48:00 +0200 |
|
|
|
772 </pubDate> |
|
|
|
773 <title>This Month in TYPO3 - May 2020 - Issue #17 |
|
|
|
774 </title> |
|
|
|
775 <link> |
|
|
|
776 |
|
|
|
777 https://typo3.org/project/news/this-month-in-typo3/this-month-in-typo3-may-2020-issue-17 |
|
|
|
778 |
|
|
|
779 </link> |
|
|
|
780 <description>Time flies! The release of TYPO3 v10 is already one month ago and the adoption rate is awesome which can be measured by over 400 compatible extensions!</description> |
|
|
|
781 <content:encoded> |
|
|
|
782 <![CDATA[ |
|
|
|
783 |
|
|
|
784 ]]> |
|
|
|
785 </content:encoded> |
|
|
|
786 |
|
|
|
787 |
|
|
|
788 <category>Community</category> |
|
|
|
789 |
|
|
|
790 |
|
|
|
791 </item> |
|
|
|
792 |
|
|
|
793 <item> |
|
|
|
794 <guid isPermaLink="false">news-2055</guid> |
|
|
|
795 <pubDate> |
|
|
|
796 Tue, 30 Jun 2020 09:45:00 +0200 |
|
|
|
797 </pubDate> |
|
|
|
798 <title>This Month in TYPO3 - April 2020 - Issue #16 |
|
|
|
799 </title> |
|
|
|
800 <link> |
|
|
|
801 |
|
|
|
802 https://typo3.org/project/news/this-month-in-typo3/this-month-in-typo3-april-2020-issue-16 |
|
|
|
803 |
|
|
|
804 </link> |
|
|
|
805 <description>April was marked by the long awaited release of TYPO3 v10 LTS. The feedback of the community so far is overwhelming and we have a rock stable new LTS version with already more than 300 compatible extensions!</description> |
|
|
|
806 <content:encoded> |
|
|
|
807 <![CDATA[ |
|
|
|
808 |
|
|
|
809 ]]> |
|
|
|
810 </content:encoded> |
|
|
|
811 |
|
|
|
812 |
|
|
|
813 <category>Community</category> |
|
|
|
814 |
|
|
|
815 |
|
|
|
816 </item> |
|
|
|
817 |
|
|
|
818 <item> |
|
|
|
819 <guid isPermaLink="false">news-2054</guid> |
|
|
|
820 <pubDate> |
|
|
|
821 Fri, 26 Jun 2020 20:40:58 +0200 |
|
|
|
822 </pubDate> |
|
|
|
823 <title>A Special Call-Out for TYPO3 Market Research |
|
|
|
824 </title> |
|
|
|
825 <link> |
|
|
|
826 |
|
|
|
827 https://typo3.org/article/a-special-call-out-for-typo3-market-research |
|
|
|
828 |
|
|
|
829 </link> |
|
|
|
830 <description>We’re asking for your help to find the right audience for two TYPO3 Market Research surveys. Help us reach sales professionals and decision makers to understand how people chose TYPO3. In a few minutes, you can make a big difference!</description> |
|
|
|
831 <content:encoded> |
|
|
|
832 <![CDATA[ |
|
|
|
833 <h3>Why Are We Doing This?</h3> |
|
|
|
834 <p>Marketing Team Lead Luisa laid out <a href="https://typo3.org/article/the-typo3-marketing-teams-2020-vision" target="_blank">the 2020 Vision</a>: to raise awareness, interest, and consideration for decision makers. In the first quarter, we were focused on release communications. For the next phase, we are working more strategically. </p> |
|
|
|
835 <p>Contributor Luana Valentini wrote a recap of our <a href="https://typo3.org/article/recap-from-the-first-online-marketing-sprint-q2-2020" target="_blank">recent online Marketing Sprint</a>. The outcomes include building dashboards, analytics, and data gathering. One of those data points is looking at the decision making process. </p> |
|
|
|
836 <h3>Help Us Reach the Right Audience for this Research</h3> |
|
|
|
837 <p>It’s most likely that the people we need to reach are not reading the typo3.org news articles. But it is likely that each person in our active community does personally know at least one or two people who are the “right” people. They will more than likely respond if you send them a personal request. </p> |
|
|
|
838 <p>Below, we have two surveys and two email templates you can use to send requests for participation to colleagues and customers. Please feel free to customize the text as suits you. </p> |
|
|
|
839 <h3>Survey of Post-Purchase Business Decision Makers</h3> |
|
|
|
840 <p><strong>What will this survey tell us?</strong></p> |
|
|
|
841 <p>This is a survey by the TYPO3 community to find out </p> |
|
|
|
842 <ol> <li>What influenced them to choose TYPO3.</li> <li>What information or support they feel could have helped them in the earliest stages of decision making. </li> </ol> |
|
|
|
843 <p><strong>Who are we trying to reach? Business decision-makers who chose TYPO3. </strong></p> |
|
|
|
844 <p>Anyone involved in the decision-making process. Generally, the decision-making process for a website or web app involves a group of people. So this could include CTOs, CMOs, Marketers, Business Analysts, or anyone involved in or consulted as part of a decision-making process where they finally chose TYPO3 as their content management system. Many developers would go directly to documentation, or even read the code itself. But business decision-makers might have trouble finding the information they need. </p> |
|
|
|
845 <p><strong>Email template to invite decision-makers to participate</strong></p> |
|
|
|
846 <p>Use this email template to send to your customers and colleagues. </p> |
|
|
|
847 <p class="alert alert-dark indent-2">Hello there!!<br /> <br /> As a TYPO3 user who chose TYPO3 over many other options, you have a lot of insight into the decision-making process. The TYPO3 Marketing team is conducting marketing research and would love to hear from you.<br /> <br /> What did you find most interesting about TYPO3? What other options were you considering? This kind of information can help us create better resources and grow the community. <br /> <br /> This survey should take about 10 mins and we are so grateful for your contribution. TYPO3 is “free” to use, with no license fee, but it requires the help and time of many people, like you! <br /> <br /> TYPO3 Market Survey: Post-purchase business decision makers<br /> <br /> English: <a href="https://forms.gle/c82oQjmuB5QNfca3A" target="_blank" rel="noreferrer">https://forms.gle/c82oQjmuB5QNfca3A</a> <br /> German: <a href="https://forms.gle/KA5ng8rTmBnYN4hm9" target="_blank" rel="noreferrer">https://forms.gle/KA5ng8rTmBnYN4hm9</a> <br /> Spanish: <a href="https://forms.gle/xB3L99CTqRESgjU47" target="_blank" rel="noreferrer">https://forms.gle/xB3L99CTqRESgjU47</a><br /> <br /> We hope you can consider this a really valuable contribution. Thank you!<br /> <br /> Kind regards,<br /> <br /> [Your name]</p> |
|
|
|
848 <h3>Survey of TYPO3 Salespeople</h3> |
|
|
|
849 <p><strong>What will this survey tell us?</strong></p> |
|
|
|
850 <p>This is a design for a survey of Salespeople in the TYPO3 community to find out: </p> |
|
|
|
851 <ol> <li>Their perception of TYPO3’s strengths and weaknesses.</li> <li>Their experience winning over or losing to TYPO3 competitors.</li> <li>What information or support they feel could have helped them to sell TYPO3.</li> </ol> |
|
|
|
852 <p><strong>Who are we trying to reach? Sales professionals who sell TYPO3.</strong></p> |
|
|
|
853 <p>People involved in the selling process in a digital agency that sells TYPO3 services and products. Including agency leadership, salespeople, technical sales, sales engineers, project managers, business analysts, or anyone who talks with a decision maker during the process.</p> |
|
|
|
854 <p><strong>Email template to invite salespeople to participate</strong></p> |
|
|
|
855 <p>Use this email template to send to your colleagues. </p> |
|
|
|
856 <p class="alert alert-dark indent-3">Hello there!<br /> <br /> The TYPO3 Marketing team is conducting marketing research and would love to hear from you as a sales professional, or someone involved in the sales process. <br /> <br /> There’s a lot of confusion in the market about what TYPO3 is or does. Since you talk with a lot of decision-makers, you have a perfect perspective to tell us what kinds of things they are struggling with. <br /> <br /> This survey should take about 10 mins, we are so grateful for your contribution. TYPO3 is “free” to use, but it requires the help and time of many people, like you! <br /> <br /> TYPO3 Market Survey: Salespeople<br /> <br /> English <a href="https://forms.gle/4Bivi7AnDGoMQTah6" target="_blank" rel="noreferrer">https://forms.gle/4Bivi7AnDGoMQTah6</a> (If you’d like this translated, please comment below!)<br /> Spanish: <a href="https://forms.gle/JhyZCRwVtonPqWT58" target="_blank" rel="noreferrer">https://forms.gle/yk9yizyCLi8mNKtF9</a> <br /> <br /> We appreciate your time. As a result, the TYPO3 community will be making resources to help you educate customers and close your deals. How does that sound? Please do leave your email address if you’d like us to keep you posted. We will periodically email you when we have any updates and news. <br /> <br /> Kind regards, <br /> <br /> [Your name]</p> |
|
|
|
857 <h3>How Will This Information Help?</h3> |
|
|
|
858 <p>We will share findings and outcomes in our Marketing Team meeting, and you’ll be very welcome to join us! We will also publish a summary here in the News Feed. </p> |
|
|
|
859 <p>We will use the insights to help us implement marketing projects: </p> |
|
|
|
860 <ul> <li>Develop and prioritize messaging that helps decision-makers. </li> <li>Create content to address misconceptions, objections, and provide vital information. </li> <li>Report back any useful information to relevant TYPO3 initiatives. </li> <li>Compare findings in a future survey. </li> </ul> |
|
|
|
861 <p>So please join us if you’d like to get involved in the <a href="https://typo3.org/community/teams/marketing" target="_blank">TYPO3 Marketing Team</a>.</p> |
|
|
|
862 <h3>TYPO3 Marketing Team: Boosting TYPO3!</h3> |
|
|
|
863 <p>By boosting awareness of TYPO3 and helping newcomers and decision-makers get information about TYPO3, we can help grow the market and your business opportunities. And by building resources for salespeople, we can help them educate customers and find the right solutions. It’s a win-win! </p> |
|
|
|
864 <p>Now, we need your help to reach the right audience for this survey. Thank you!</p> |
|
|
|
865 <p>If you have any questions about the survey contact us in the #marketing channel on TYPO3 Slack.</p> |
|
|
|
866 ]]> |
|
|
|
867 </content:encoded> |
|
|
|
868 |
|
|
|
869 |
|
|
|
870 <category>Community</category> |
|
|
|
871 |
|
|
|
872 <category>Marketing</category> |
|
|
|
873 |
|
|
|
874 |
|
|
|
875 </item> |
|
|
|
876 |
|
|
|
877 <item> |
|
|
|
878 <guid isPermaLink="false">news-2053</guid> |
|
|
|
879 <pubDate> |
|
|
|
880 Thu, 25 Jun 2020 19:24:32 +0200 |
|
|
|
881 </pubDate> |
|
|
|
882 <title>TYPO3 v10 Community Content Roundup |
|
|
|
883 </title> |
|
|
|
884 <link> |
|
|
|
885 |
|
|
|
886 https://typo3.org/article/typo3-v10-community-content-roundup |
|
|
|
887 |
|
|
|
888 </link> |
|
|
|
889 <description>TYPO3 v10 came out only two months ago, and wow—how time flies! We wanted to celebrate the contributors in the community, who helped get the word out about TYPO3 by writing blog posts and sharing the news. We knew you’d like to help boost TYPO3’s signal and loved your contributions. If we missed any contributions, please post them in the comments section.</description> |
|
|
|
890 <content:encoded> |
|
|
|
891 <![CDATA[ |
|
|
|
892 <p>You can also submit your links to the next edition of This Month in TYPO3.</p> |
|
|
|
893 <p><a href="/project/news/this-month-in-typo3?type=100" class="btn btn-primary">Submit Your Link to This Month in TYPO3</a></p> |
|
|
|
894 <h3>And the Winner Is…</h3> |
|
|
|
895 <p>In the run up to the release of TYPO3 v10, we <a href="https://typo3.org/article/10-ways-to-get-ready-for-typo3-v10" target="_blank">asked people in the community</a> to make some noise by writing about it and sharing it on Twitter. Then we entered the submissions into a prize draw and selected a random winner. </p> |
|
|
|
896 <p>And the winner is… </p> |
|
|
|
897 <p class="alert alert-success"><a href="https://www.nitsan.in/blog/typo3-update-upgrade/" target="_blank" rel="noreferrer"><strong>The Ultimate Guide to TYPO3 Update/Upgrade</strong></a><br /> by Sanjay Chauhan of <a href="https://www.nitsan.in/" target="_blank" rel="noreferrer">NITSAN Technologies</a> in Bhavnagar, Gujarat, India!<br /> (A little treasure is on its way to you.)</p> |
|
|
|
898 ]]> |
|
|
|
899 </content:encoded> |
|
|
|
900 |
|
|
|
901 |
|
|
|
902 <category>Community</category> |
|
|
|
903 |
|
|
|
904 <category>Marketing</category> |
|
|
|
905 |
|
|
|
906 |
|
|
|
907 </item> |
|
|
|
908 |
|
|
|
909 <item> |
|
|
|
910 <guid isPermaLink="false">news-2052</guid> |
|
|
|
911 <pubDate> |
|
|
|
912 Tue, 23 Jun 2020 08:56:29 +0200 |
|
|
|
913 </pubDate> |
|
|
|
914 <title>Who Does What in the Association Board, 2020? |
|
|
|
915 </title> |
|
|
|
916 <link> |
|
|
|
917 |
|
|
|
918 https://typo3.org/project/association/structure/board |
|
|
|
919 |
|
|
|
920 </link> |
|
|
|
921 <description>Check out the roles and responsibilities for the members of the TYPO3 Association Board in 2020.</description> |
|
|
|
922 <content:encoded> |
|
|
|
923 <![CDATA[ |
|
|
|
924 |
|
|
|
925 ]]> |
|
|
|
926 </content:encoded> |
|
|
|
927 |
|
|
|
928 |
|
|
|
929 <category>Association</category> |
|
|
|
930 |
|
|
|
931 |
|
|
|
932 </item> |
|
|
|
933 |
|
|
|
934 <item> |
|
|
|
935 <guid isPermaLink="false">news-2051</guid> |
|
|
|
936 <pubDate> |
|
|
|
937 Mon, 22 Jun 2020 18:54:57 +0200 |
|
|
|
938 </pubDate> |
|
|
|
939 <title>Mentoring Digital Transformation with TYPO3 |
|
|
|
940 </title> |
|
|
|
941 <link> |
|
|
|
942 |
|
|
|
943 https://typo3.org/article/mentoring-digital-transformation-with-typo3 |
|
|
|
944 |
|
|
|
945 </link> |
|
|
|
946 <description>Tymoteusz Motylewski is a TYPO3 mentor. “It is very satisfying,” he says, and tells me the story of how he started out on the other side; being mentored by others in the TYPO3 community.</description> |
|
|
|
947 <content:encoded> |
|
|
|
948 <![CDATA[ |
|
|
|
949 <p>“That’s where my career started. People answered my silly questions on the web forums. They were helpful and friendly, and after some years I realized I had reached a level where I could help them back.”</p> |
|
|
|
950 <p>Now, himself a <a href="/community/teams/typo3-development?type=100">TYPO3 Core Team</a> member and head of development at Polish agency <a href="https://macopedia.com" target="_blank" rel="noreferrer">Macopedia</a>, Tymoteusz sees mentoring others as a central part of his contribution to the CMS: “Helping others learn TYPO3 is building the community.”</p> |
|
|
|
951 <h2>Building National Competence in Rwanda</h2> |
|
|
|
952 <p>As he tells his story, it becomes clear to me that his mentoring is not limited to Poland—or even Europe. His most recent mentoring experience, in collaboration with the TYPO3 Association, brought him to Central Africa with Alina Fleser and Daniel Homorodean.</p> |
|
|
|
953 <p>“We coached a team of ten people from the <a href="https://www.gov.rw" target="_blank" rel="noreferrer">Rwandan government</a>’s web team. They were responsible for relaunching some 200 official websites for the government. Together, we established a great workflow and got the team on track, and the first few TYPO3 websites went live not many weeks ago.”</p> |
|
|
|
954 <p>Handling projects of this size and impact can be a challenge to anyone, and Tymoteusz’ work went beyond TYPO3, covering best-practice infrastructure, security, deployment, and project management.</p> |
|
|
|
955 ]]> |
|
|
|
956 </content:encoded> |
|
|
|
957 |
|
|
|
958 |
|
|
|
959 <category>Community</category> |
|
|
|
960 |
|
|
|
961 <category>Association</category> |
|
|
|
962 |
|
|
|
963 |
|
|
|
964 </item> |
|
|
|
965 |
|
|
|
966 <item> |
|
|
|
967 <guid isPermaLink="false">news-2050</guid> |
|
|
|
968 <pubDate> |
|
|
|
969 Tue, 09 Jun 2020 19:42:29 +0200 |
|
|
|
970 </pubDate> |
|
|
|
971 <title>Recap from the First Online Marketing Sprint (Q2/2020) |
|
|
|
972 </title> |
|
|
|
973 <link> |
|
|
|
974 |
|
|
|
975 https://typo3.org/article/recap-from-the-first-online-marketing-sprint-q2-2020 |
|
|
|
976 |
|
|
|
977 </link> |
|
|
|
978 <description>For the first time, on 26 and 27 May 2020, an entirely digital marketing sprint has been held. Due to continuing travel restrictions in Europe, the international gathering of TYPO3 enthusiasts met online to strategically advance the TYPO3 project from the perspective of the sales sector, PR experts, and content creators.</description> |
|
|
|
979 <content:encoded> |
|
|
|
980 <![CDATA[ |
|
|
|
981 <p>The participants engaged in lively discussion and strategic planning for two days, in large group hangouts lasting three hours and subsequent breakout sessions.</p> |
|
|
|
982 <h2>The Contributors Were</h2> |
|
|
|
983 <ul> <li>Julian Böhm, <a href="https://typo3.com/" target="_blank" rel="noreferrer">TYPO3 GmbH</a></li> <li>Mathias Bolt Lesniak, <a href="https://www.pixelant.net" target="_blank" rel="noreferrer">Pixelant</a></li> <li>Luisa Faßbender,<a href="https://marketing-factory.de/" target="_blank" rel="noreferrer"> Marketing Factory Consulting GmbH</a></li> <li>John Heaven, <a href="https://openstrategypartners.com/" target="_blank" rel="noreferrer">Open Strategy Partners GmbH</a></li> <li>Carlos Antonio Llanos Zarco,<a href="https://www.icti.es/" target="_blank" rel="noreferrer"> icti</a></li> <li>Ronald Meeuwissen,<a href="https://www.maxserv.com/" target="_blank" rel="noreferrer"> MaxServ</a></li> <li>Jeffrey A. McGuire,<a href="https://openstrategypartners.com/" target="_blank" rel="noreferrer"> Open Strategy Partners GmbH</a></li> <li>Heather McNamee,<a href="https://openstrategypartners.com/" target="_blank" rel="noreferrer"> Open Strategy Partners GmbH</a></li> <li>Silvia Romero Martin, <a href="https://www.icti.es/" target="_blank" rel="noreferrer">icti</a></li> <li>Marco Tiel, <a href="https://typo3.com/" target="_blank" rel="noreferrer">TYPO3 GmbH</a></li> <li>Kai Unterberg, <a href="https://km2.de/" target="_blank" rel="noreferrer">KM2 >> GmbH</a></li> <li>Luana Valentini, <a href="http://www.dfau.de/" target="_blank" rel="noreferrer">DFAU GmbH</a></li> </ul> |
|
|
|
984 <p>But first of all, the organizational heads Heather, Luisa, and Marco started off by presenting the status quo of the marketing tasks already started in Q1. New faces also received a warm welcome to the group before new goals for Q2’s sprint were set.</p> |
|
|
|
985 <h2>Setting New Goals for the Community</h2> |
|
|
|
986 <p>Among these goals was the order of the already submitted topics that registered participants wanted to see on the agenda. There were no restrictions on ideas and thoughts, and even spontaneous suggestions were quickly sorted into the priority list. Thanks to this overview created by Heather, as well as her timekeeping skills, it was possible to formulate tangible goals from which the community will soon benefit. But more about that later.</p> |
|
|
|
987 <h2>Regrouping According to Individual Skills and Knowledge</h2> |
|
|
|
988 <p>As one of two newbies in the group, I noticed after only a few minutes that each participant was able to contribute an equal opinion on the overall result, since the experiences from his or her own everyday agency work almost always provides a helpful insight. This was soon also reflected during the breakout sessions, in which small interest groups of two to four participants were asked to clarify the tasks identified in the priority list.</p> |
|
|
|
989 <h2>Major Topics Discovered</h2> |
|
|
|
990 <p>Following the small interest group discussions, the briefs prepared there were shortly presented to the whole team, and four major areas of concern were identified. These four overarching themes were worked on more intensively on Day 2:</p> |
|
|
|
991 <ul> <li><strong>Analytics</strong>: Who, why, and how do visitors navigate the official websites of the TYPO3 sphere and what can we do with the knowledge gained?</li> <li><strong>Onboarding</strong>: What does the ideal customer journey look like, and how do we optimize it for first-time users?</li> <li><strong>Sales</strong>: What selling points do salespeople need to make TYPO3 shine in its deserved light—especially in competition with other CMSs?</li> <li><strong>Market share</strong>: What is the role of TYPO3 in comparison to other CMSs worldwide?</li> </ul> |
|
|
|
992 <p>Another important consideration has been that multi-language support and visibility in target countries will have to play a greater role in the future in order to increase the reach of TYPO3.</p> |
|
|
|
993 <h2>Day 2: Designing the Road Ahead</h2> |
|
|
|
994 <p>In this spirit, the overall goals of the Marketing Initiative were further sharpened at the beginning of Day 2. Most importantly, the precise phrasing of individual sub-tasks with the main responsible persons and deadlines in mind had to be noted. This will ensure that intermediate goals won’t be overlooked in further meetings and that strategic work can continue.</p> |
|
|
|
995 <h2>Individual Expertise for the Community</h2> |
|
|
|
996 <p>Accordingly, the day was arranged in a very goal-oriented way. Opinions were further exchanged, discrepancies uncovered, ambiguities removed and ultimately agreement was reached. Thanks to the individual expertise that each participant can contribute, and through personal contacts that can be fruitful in the future, everyone left the sprint with tasks tailored to him or her personally.</p> |
|
|
|
997 <h2>New Marketing Appointments Fixed</h2> |
|
|
|
998 <p>Even before the sprint was over, the upcoming events were fixed:</p> |
|
|
|
999 <ul> <li><strong>Tuesday, June 30, 2020</strong>: Open Sprint/Online Workshop: Onboarding pathway for newcomers</li> <li><strong>Tuesday–Wednesday, 1–2 September 2020</strong>: TYPO3 Online Marketing Sprint Q3/2020</li> </ul> |
|
|
|
1000 <h2>Join the Open Sprint/Online Workshop</h2> |
|
|
|
1001 <p>At the Open Sprint all interested community members are welcome to participate in the above mentioned ideal onboarding process for first-time TYPO3 users! After all, it was precisely on this topic that the Sprint's group discussions had shown that many facets must be included in order to help the entire community gain new customers—and thus more TYPO3 enthusiasts. Starting with the on-site acquisition up to the interface and content design of the TYPO3 website.</p> |
|
|
|
1002 <h2>Open Arms for More Marketing Professionals</h2> |
|
|
|
1003 <p>I would like to add that my personal perception gained at numerous TYPO3 events has been confirmed online: A feeling of belonging to a community that pursues the noble goal of advancing the TYPO3 Open Source technology. And of course I’d like to encourage new faces to bring their expertise to the already scheduled sprint for Q3.</p> |
|
|
|
1004 <p>There is still a lot of work ahead of us to increase awareness and market share of TYPO3. While not forgetting one of our key assets: We are the good guys.</p> |
|
|
|
1005 <p><a href="/community/teams/marketing?type=100" class="btn btn-primary">Join the Marketing Team</a></p> |
|
|
|
1006 <p> <br /> Proofreading: Tony Lush</p> |
|
|
|
1007 ]]> |
|
|
|
1008 </content:encoded> |
|
|
|
1009 |
|
|
|
1010 |
|
|
|
1011 <category>Community</category> |
|
|
|
1012 |
|
|
|
1013 <category>Association</category> |
|
|
|
1014 |
|
|
|
1015 <category>Marketing</category> |
|
|
|
1016 |
|
|
|
1017 |
|
|
|
1018 </item> |
|
|
|
1019 |
|
|
|
1020 <item> |
|
|
|
1021 <guid isPermaLink="false">news-2049</guid> |
|
|
|
1022 <pubDate> |
|
|
|
1023 Tue, 09 Jun 2020 10:45:00 +0200 |
|
|
|
1024 </pubDate> |
|
|
|
1025 <title>TYPO3 10.4.4 and 9.5.19 maintenance releases published |
|
|
|
1026 </title> |
|
|
|
1027 <link> |
|
|
|
1028 |
|
|
|
1029 https://typo3.org/article/typo3-1044-and-9519-maintenance-releases-published |
|
|
|
1030 |
|
|
|
1031 </link> |
|
|
|
1032 <description>The versions 10.4.4 and 9.5.19 of the TYPO3 Enterprise Content Management System have just been released.</description> |
|
|
|
1033 <content:encoded> |
|
|
|
1034 <![CDATA[ |
|
|
|
1035 <p>The following TYPO3 updates have been released:</p> |
|
|
|
1036 <ul> <li>TYPO3 10.4.4 LTS</li> <li>TYPO3 9.5.19 LTS</li> </ul> |
|
|
|
1037 <p>Both versions are maintenance releases only.</p> |
|
|
|
1038 <h3>Further upgrade instructions</h3> |
|
|
|
1039 <p class="alert alert-success">No database upgrades are required for these maintenance releases.</p> |
|
|
|
1040 <h3><br /> Download</h3> |
|
|
|
1041 <p>TYPO3 can be installed in various ways. For example the traditional way by using the source package at <a href="https://get.typo3.org" target="_blank" rel="noreferrer">get.typo3.org</a> 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:</p> |
|
|
|
1042 <ul> <li><a href="https://get.typo3.org/release-notes/10.4.4" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/10.4.4</a> </li> <li><a href="https://get.typo3.org/release-notes/9.5.19" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/9.5.19</a> </li> </ul> |
|
|
|
1043 ]]> |
|
|
|
1044 </content:encoded> |
|
|
|
1045 |
|
|
|
1046 |
|
|
|
1047 <category>Development</category> |
|
|
|
1048 |
|
|
|
1049 <category>TYPO3 CMS</category> |
|
|
|
1050 |
|
|
|
1051 |
|
|
|
1052 </item> |
|
|
|
1053 |
|
|
|
1054 <item> |
|
|
|
1055 <guid isPermaLink="false">news-2048</guid> |
|
|
|
1056 <pubDate> |
|
|
|
1057 Wed, 27 May 2020 08:35:00 +0200 |
|
|
|
1058 </pubDate> |
|
|
|
1059 <title>TYPO3 Book Report—Who’s Writing the TYPO3 Book? |
|
|
|
1060 </title> |
|
|
|
1061 <link> |
|
|
|
1062 |
|
|
|
1063 https://typo3.org/article/typo3-book-report-whos-writing-the-typo3-book |
|
|
|
1064 |
|
|
|
1065 </link> |
|
|
|
1066 <description>You might be wondering just who is writing the TYPO3 Guidebook and how the project is coming along. I sat down to interview my colleague Felicity Brand, the TYPO3 Guidebook main author, about her experience, what she’s working on right now, and what’s next on the horizon for the book. If you’d like to keep in touch, subscribe to the TYPO3 Guidebook mailing list and we’ll have some more news for you soon!</description> |
|
|
|
1067 <content:encoded> |
|
|
|
1068 <![CDATA[ |
|
|
|
1069 <p><a href="https://typo3book.us19.list-manage.com/subscribe?u=aad5ade74a10776dff391bb78&id=ef9a2d2965" target="_blank" class="btn btn-primary" rel="noreferrer">Sign Up to the TYPO3 Guidebook Mailing List</a></p> |
|
|
|
1070 <h2>How did you get into technical writing, Felicity?</h2> |
|
|
|
1071 <p>In my former life I was a business analyst, and I always enjoyed the writing aspect of that role. I wrote functional specs, tech specs, and user testing plans. </p> |
|
|
|
1072 <p>I had studied English and loved writing, but technical writing was a new field to me. When I discovered technical writing was a thing you could do, I took a postgraduate course in Melbourne. </p> |
|
|
|
1073 <p>I went through the course with a good set of lecturers, who were active in the technical writing community. That’s how I got started as a tech writer, and have been enjoying it ever since.</p> |
|
|
|
1074 <h2>How did you get into open source?</h2> |
|
|
|
1075 <p>As a technical writer, I had always worked in the corporate world, documenting software and attending conferences in the corporate world. I started hearing more and more about open source and didn’t understand it. </p> |
|
|
|
1076 <p>Fast forward 12 years… and I had a baby and that was a catalyst to change my working life. I needed more control over my schedule and flexible work hours. One of the great things about working in open source is that there are a lot of opportunities to tailor your work-life balance. Even before the Covid-19 pandemic, remote work was common, and there is a lot of focus on the human side of technology, including staying happy and healthy.</p> |
|
|
|
1077 <p>I started with <a href="https://openstrategypartners.com/" target="_blank" rel="noreferrer">Open Strategy Partners</a>, and coincidentally, at the same time I participated in the inaugural Google Season of Docs program. Since then, I joined the embryonic open source project for technical writing, <a href="https://thegooddocsproject.dev/" target="_blank" rel="noreferrer">The Good Docs</a>, and I’m on the steering committee for that. </p> |
|
|
|
1078 <h2>Tell us about The Good Docs and the Google Season of Docs.</h2> |
|
|
|
1079 <p>The idea with The Good Docs is to produce best-practice templates to help open source project maintainers produce their own documentation. My mentor from the Google Season of Docs was the driving force behind this idea. </p> |
|
|
|
1080 <p>During the Season of Docs, I worked in an open source community focused on geospatial software. The Open Source Geospatial Foundation (OSGeo) is an umbrella for a large number of separate OSS projects. They were distributing their software together, but there was inconsistency across all the projects; each was managed by a different project owner and maintainer. So we focused on the quick start guides for each of these projects to make them consistent.</p> |
|
|
|
1081 <p>My mentor wanted me to focus on facilitating these project owners to learn how to do the work, rather than just swooping in, doing the work and leaving. We wanted to enable them to maintain their docs in the future. So we did spend a lot of time on communication. </p> |
|
|
|
1082 <p>Enablement and good communication are two common topics in open source that I feel passionate about. We wanted to continue to work on helping project maintainers create great documentation. So that’s what led to The Good Docs project.</p> |
|
|
|
1083 <p>It has a good, diverse group of people attached to it from Australia, the UK, and the US. We released the alpha versions of the templates at the 2019 <a href="https://www.writethedocs.org/" target="_blank" rel="noreferrer">Write The Docs</a> event in Australia. </p> |
|
|
|
1084 <h2>So you’re really all-in with open source now! That is great! How do you find it? Anything surprising?</h2> |
|
|
|
1085 <p>I find the challenges of group work and getting consensus to be different. When you’re in a business in a hierarchical structure, you know clearly who your stakeholders are. But when you go into an open-source community and it’s all volunteers, you don’t know who to talk to. You want to be respectful because you have an awareness of being part of a larger group. And I’ve come to recognize that help may come from unexpected quarters. </p> |
|
|
|
1086 <p>A friend of mine, who is an open-source developer, said you can’t cut people out who appear to be “onlookers” just watching a conversation take place. You’re never just talking to one person in an open source community context.</p> |
|
|
|
1087 ]]> |
|
|
|
1088 </content:encoded> |
|
|
|
1089 |
|
|
|
1090 |
|
|
|
1091 <category>Community</category> |
|
|
|
1092 |
|
|
|
1093 <category>Association</category> |
|
|
|
1094 |
|
|
|
1095 <category>TYPO3 CMS</category> |
|
|
|
1096 |
|
|
|
1097 |
|
|
|
1098 </item> |
|
|
|
1099 |
|
|
|
1100 <item> |
|
|
|
1101 <guid isPermaLink="false">news-2047</guid> |
|
|
|
1102 <pubDate> |
|
|
|
1103 Fri, 22 May 2020 19:45:40 +0200 |
|
|
|
1104 </pubDate> |
|
|
|
1105 <title>TYPO3 Users, Please Let Us Know Your Feedback! |
|
|
|
1106 </title> |
|
|
|
1107 <link> |
|
|
|
1108 |
|
|
|
1109 https://typo3.org/article/typo3-users-please-let-us-know-your-feedback |
|
|
|
1110 |
|
|
|
1111 </link> |
|
|
|
1112 <description>We are looking for reviews from TYPO3 users to share their experiences with our beloved CMS. This to improve our visibility and help peers who are looking for a reliable, secure, fast, and flexible content management system. </description> |
|
|
|
1113 <content:encoded> |
|
|
|
1114 <![CDATA[ |
|
|
|
1115 <p>The TYPO3 Project has started to use <a href="https://www.g2.com/products/typo3" target="_blank" rel="noreferrer">G2.com</a>, the tech marketplace, as a prominent place to show the TYPO3 Project to millions of business decision-makers each month. </p> |
|
|
|
1116 <p>“Your peers come to G2 to get an inside look at TYPO3 and other business solutions. Adding your personal perspective on TYPO3 will help others pick the right solution based on real user experiences.”</p> |
|
|
|
1117 <h2>Submit Your Review Today</h2> |
|
|
|
1118 <p>As valuable TYPO3 users, we ask you to <a href="https://www.g2.com/products/typo3/take_survey" target="_blank" rel="noreferrer">provide a review of TYPO3 CMS</a>. A review takes only a few minutes and the community as a whole would be thankful for your input! </p> |
|
|
|
1119 <p>Tell us what you like best? What do you dislike? What recommendations would you make for someone embarking on a TYPO3 project? What problems are you solving with TYPO3? And what benefits have you realized using TYPO3? </p> |
|
|
|
1120 <p>Make your voice heard. We want to know!</p> |
|
|
|
1121 <p><a href="https://www.g2.com/products/typo3/take_survey" target="_blank" class="btn btn-primary" rel="noreferrer">Write a Review Today</a></p> |
|
|
|
1122 <h2>Why We Love to Hear Your Feedback</h2> |
|
|
|
1123 <p>We will gather all feedback centrally on <a href="https://www.g2.com/products/typo3" target="_blank" rel="noreferrer">our G2.com landing page</a>. This enables us to verify, check, and process your feedback. The TYPO3 Project would really appreciate your honest input! While there is already <a href="https://docs.typo3.org/m/typo3/guide-contributionworkflow/master/en-us/ReportingAnIssue/Index.html#report-an-issue" target="_blank" rel="noreferrer">an issue queue</a> where people can report bugs or feature proposals, there hasn’t been a place where TYPO3 end users can give their honest feedback about their experience.</p> |
|
|
|
1124 <p>Meanwhile, with more reviews, TYPO3 CMS will also get more visibility on this specific worldwide platform. Every day, decision-makers are researching software options and they love to read experiences from their peers. </p> |
|
|
|
1125 <p><a href="https://www.g2.com/products/typo3/reviews#reviews" target="_blank" rel="noreferrer">See what others say about TYPO3!</a> Give them a like to say thank you, when you feel their insights helped your search. Thank you for your time on behalf of the TYPO3 Project and the Marketing Team.</p> |
|
|
|
1126 <h2>About G2.com</h2> |
|
|
|
1127 <p><a href="https://www.g2.com/" target="_blank" rel="noreferrer">G2</a> is the world’s largest tech marketplace where businesses can discover, review, and manage the technology they need to reach their potential. As a strong Open-Source project TYPO3 is a great option in the Web Content Management Software area. Therefore we need to be out there on G2.com. We are happy to educate, help, and influence new TYPO3 users to join our great community!</p> |
|
|
|
1128 <p class="alert alert-success"><strong>Help increase TYPO3 adoption—join the <a href="/community/teams/marketing?type=100">Marketing Team</a></strong> at the next <a href="/event/20200526-typo3-marketing-sprint-q2-2020?type=100">online marketing sprint: 26–27 May, 2020</a>.</p> |
|
|
|
1129 ]]> |
|
|
|
1130 </content:encoded> |
|
|
|
1131 |
|
|
|
1132 |
|
|
|
1133 <category>Community</category> |
|
|
|
1134 |
|
|
|
1135 <category>Marketing</category> |
|
|
|
1136 |
|
|
|
1137 |
|
|
|
1138 </item> |
|
|
|
1139 |
|
|
|
1140 <item> |
|
|
|
1141 <guid isPermaLink="false">news-2046</guid> |
|
|
|
1142 <pubDate> |
|
|
|
1143 Wed, 20 May 2020 19:35:34 +0200 |
|
|
|
1144 </pubDate> |
|
|
|
1145 <title>Structured Content Initiative—What happened in April? The survey results! |
|
|
|
1146 </title> |
|
|
|
1147 <link> |
|
|
|
1148 |
|
|
|
1149 https://typo3.org/article/structured-content-initiative-what-happened-in-april-the-survey-results |
|
|
|
1150 |
|
|
|
1151 </link> |
|
|
|
1152 <description>As promised in our last article, here’s our latest update from the TYPO3 Structured Content Initiative. Today we’re sharing results from our Survey of TYPO3 Editors.</description> |
|
|
|
1153 <content:encoded> |
|
|
|
1154 <![CDATA[ |
|
|
|
1155 <p>The <a href="/community/teams/typo3-development/initiatives/structured-content?type=100">Structured Content Initiative</a> is the core <a href="/community/teams/typo3-development/initiatives?type=100">Strategic Initiative</a> focused on improving the content editing user experience in TYPO3 CMS. Read <a href="https://typo3.org/article/structured-content-initiative-what-happened-in-february" target="_blank">our last update</a> to learn more about what we’ve been working on. </p> |
|
|
|
1156 <p><a href="https://my.typo3.org/about-mytypo3org/slack" target="_blank" rel="noreferrer">Connect to TYPO3 Slack</a> and join us in the #cig-structuredcontent channel.</p> |
|
|
|
1157 ]]> |
|
|
|
1158 </content:encoded> |
|
|
|
1159 |
|
|
|
1160 |
|
|
|
1161 <category>Development</category> |
|
|
|
1162 |
|
|
|
1163 <category>Community</category> |
|
|
|
1164 |
|
|
|
1165 |
|
|
|
1166 </item> |
|
|
|
1167 |
|
|
|
1168 <item> |
|
|
|
1169 <guid isPermaLink="false">news-2045</guid> |
|
|
|
1170 <pubDate> |
|
|
|
1171 Tue, 19 May 2020 15:30:00 +0200 |
|
|
|
1172 </pubDate> |
|
|
|
1173 <title>TYPO3 10.4.3 and 9.5.18 maintenance releases published |
|
|
|
1174 </title> |
|
|
|
1175 <link> |
|
|
|
1176 |
|
|
|
1177 https://typo3.org/article/typo3-1043-and-9518-maintenance-releases-published |
|
|
|
1178 |
|
|
|
1179 </link> |
|
|
|
1180 <description>The versions 10.4.3 and 9.5.18 of the TYPO3 Enterprise Content Management System have just been released.</description> |
|
|
|
1181 <content:encoded> |
|
|
|
1182 <![CDATA[ |
|
|
|
1183 <p>The following TYPO3 updates have been released:</p> |
|
|
|
1184 <ul> <li>TYPO3 10.4.3 LTS</li> <li>TYPO3 9.5.18 LTS</li> </ul> |
|
|
|
1185 <p>Both versions are maintenance releases only. They aim to reduce and fix side-effects of recent <a href="/article/typo3-1042-and-9517-security-releases-published?type=100">TYPO3 v10.4.2 and v9.5.17 releases</a>.</p> |
|
|
|
1186 <h3>Further upgrade instructions</h3> |
|
|
|
1187 <p class="alert alert-warning"><strong>Upgrade Wizard - Manual actions required</strong><br /> <br /> Sites that were upgraded from an older TYPO3 version to TYPO3 v9 LTS before version 9.5.11 (<9.5.11) most probably require the invocation of <strong><a href="https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.5.x/Important-89269-IntroduceUpgradeWizardForInvalidBackendUserConfiguration.html" target="_blank" rel="noreferrer">"Update backend user configuration array"</a></strong> upgrade wizard - this can be done in the backend interface at <em>Admin Tools > Upgrade > Upgrade Wizard</em>. This wizard was introduced with TYPO3 v9.5.11, the necessity to run it was not emphasized enough back then.</p> |
|
|
|
1188 <h3>Download</h3> |
|
|
|
1189 <p>TYPO3 can be installed in various ways. For example the traditional way by using the source package at <a href="https://get.typo3.org" target="_blank" rel="noreferrer">get.typo3.org</a> 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:</p> |
|
|
|
1190 <ul> <li><a href="https://get.typo3.org/release-notes/10.4.3" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/10.4.3</a></li> <li><a href="https://get.typo3.org/release-notes/9.5.18" target="_blank" rel="noreferrer">https://get.typo3.org/release-notes/9.5.18</a> </li> </ul> |
|
|
|
1191 <h3>Details on side-effects in previous relases</h3> |
|
|
|
1192 <ul> <li>change for <strong>TYPO3-CORE-SA-2020-004</strong> caused side-effects on extension- or user-land code interacting with caches in Extbase, showing deserialization errors for ReflectionService (see <a href="https://forge.typo3.org/issues/91404" target="_blank" rel="noreferrer">Forge issue #91404</a>)</li> <li>change for <strong>TYPO3-CORE-SA-2020-005</strong> causes side-effects for sites that were upgraded from versions before TYPO3 v8 and were upgrade before TYPO3 v9.5.11, e.g. causing problems in the page-tree (see <a href="https://forge.typo3.org/issues/91407" target="_blank" rel="noreferrer">Forge issue #91407</a>) <ul> <li><em>$BE_USER->uc</em> probably can contain class references to stdClass which need to be converted</li> <li>TYPO3 v9.5.11 add a corresponding <strong>Update backend user configuration array</strong> upgrade wizard</li> <li>to be found at Admin Tools > Upgrade > Upgrade Wizard > Update backend user configuration array</li> </ul> </li> <li>change for <strong>TYPO3-CORE-SA-2020-006</strong> introduced a strict referrer check, blocking cross-site requests and thus also blocking single-sign-on (SSO) implementations (see <a href="https://forge.typo3.org/issues/91396" target="_blank" rel="noreferrer">Forge issue #91396</a>)</li> </ul> |
|
|
|
1193 ]]> |
|
|
|
1194 </content:encoded> |
|
|
|
1195 |
|
|
|
1196 |
|
|
|
1197 <category>Development</category> |
|
|
|
1198 |
|
|
|
1199 |
|
|
|
1200 </item> |
|
|
|
1201 |
|
|
|
1202 |
|
|
|
1203 </channel> |
|
|
|
1204 </rss> |
|