The TYPO3 project has four main websites. This page explains what kind of content goes where and, in general terms, who is responsible for that content.
The four websites are:
typo3.com — Explain and promote TYPO3 as a product and professional solution.
typo3.community — Introduce people to the TYPO3 community and help them connect with and participate in it.
typo3.org — Explain and build confidence in the TYPO3 Project, its organization, and long-term sustainability.
news.typo3.com — News and events about and concerning TYPO3 and what happens in the TYPO3 ecosystem.
With very few exceptions, all four sites contain only original content produced by the TYPO3 Association, the TYPO3 Company and their partners, or members of the TYPO3 Community.
Why TYPO3? (Could TYPO3 be the right solution for me?)
Content Lifecycle
Evergreen; product and marketing
Funnel Position
Awareness → Consideration → Conversion
Main Audience
Decision-makers, businesses, marketers, digital leaders, agencies
Topics
Product capabilities, use cases, solutions, services, partners, certifications, training, customer success, business benefits
CTA Examples
Try TYPO3, find a partner, get in touch
Editorial Responsibility
TYPO3 Company
This website positions itself around the product and its professional offerings, including support, integrations, certifications and training.
It is designed to move visitors moving people from “I have a digital/content-management problem” to “TYPO3 might be a suitable solution” and eventually toward a concrete action.
Content belongs here when its primary purpose is to communicate:
What TYPO3 CMS is and what it does
Business and organizational use cases
Enterprise, public-sector and other solution scenarios
Product capabilities and differentiators
Professional services and support
TYPO3 Company Partners
Certifications and training
Customer success and case studies
typo3.org (Trust)
Core Question
Can I trust TYPO3? (Who stands behind TYPO3, and why should I trust this project?)
Content Lifecycle
Evergreen; institutional/project content
Funnel Position
Trust → Commitment
Main Audience
Existing users, Association Members, contributors, stakeholders, journalists, interested public
Topics
Organization, governance, strategy, finances, membership, policies, project structure, official information
CTA Examples
Become an Association member, learn about the governance
Editorial Responsibility
TYPO3 Association
This website the is place for information about the TYPO3 project's governance and the Association's role (by extension also the TYPO3 Company), while directing product-oriented visitors to typo3.com.
It is less about selling the CMS and more about explaining the project behind it. It provides the institutional context that makes an open-source project credible and sustainable. It becomes particularly important after initial awareness, when people want to understand who is behind TYPO3, how decisions are made and whether the project is trustworthy for long-term use.
Website topics include:
The TYPO3 Project and its structure
TYPO3 Association and TYPO3 Company governance
Governance and decision-making
Strategy and long-term direction
Association membership
Finances and funding
Policies and legal information
Official project information
typo3.commmunity (Participate)
Core Question
How can I be part of TYPO3? (How can I participate and find my place in TYPO3?)
Content Lifecycle
Evergreen; participation/community content
Funnel Position
Engagement → Participation → Advocacy
Main Audience
Contributors, developers, editors, community members and newcomers
Topics
How to contribute, teams, community groups, communication channels, collaboration, mentoring, community culture
CTA Examples
Join the community, ask the community, contribute to TYPO3, share your knowledge, join a sprint
Editorial Responsibility
TYPO3 Association
This website's funnel starts where the conventional customer funnel ends: Someone has moved from being interested in TYPO3 to wanting to use, contribute to, learn from or connect with the community.
TYPO3 describes participation as extending far beyond coding. Contributors include people who write documentation, develop software, organize events, translate, work on accessibility, participate in governance, mentor others, etc.
The content answers questions such as:
How can I contribute?
Where can I meet other TYPO3 people?
Which teams and committees exist?
How do I get involved?
Where do discussions happen?
How can I learn from others?
How can I organize or join community activities?
What opportunities are there for contributors?
What are the community's values and ways of working?
news.typo3.com (Follow)
Core Question
What is happening? (What's happening in TYPO3 right now?)
This site is the dynamic editorial layer connecting the other three sites. News is about things that happen, while the other sites primarily provide the stable context around those things. It helps maintain awareness and engagement among people who already know TYPO3, while also creating content that can attract people who do not.
It's all about about communicating developments, stories, and events, while remaining a repository of historical articles that may still be relevant or draw visitors.
The news categories should encompass all of TYPO3:
Best Practice & Learning
Developer & Technology
Market & Sell
Personal Stories & Opinions
Product Updates
Showcase & Success
The Project
Additionally, two categories serve specific and utilitarian purposes:
Newsletter
Security
Association and Company Content Responsibilities
In general terms, the TYPO3 Association is responsible for community-contributed articles and the TYPO3 Company for content created by or for their internal content department. In practice, this divides up many of the content topics too.
TYPO3 Association Topics
TYPO3
Maintenance Release News
Security Release News
Development News
TYPO3 Association
Board protocols
Governance
General Assembly
Official opinion pieces
Community opinion pieces
Member and membership news
Reports from teams and committees
Announcing and reporting on community events
Tutorials and best practices (for agencies and other community members)
TYPO3 Company Topics
TYPO3 Product
Feature highlights
Minor and major version releases
Official TYPO3 packages
Official integrations
Official Services
Extended Long-Term Support plans (ELTS)
Certifications
Announcing and reporting on official TYPO3 events
Guides and best practices (decision-makers, end-customers, sales)
Shared Topics
Announcing and reporting on external non-TYPO3 events
Community Contributed News Publishing Pipeline
This page outlines the publication pipeline for community-submitted TYPO3 News articles and events. Content should primarily be submitted through the Content Request Form.
The TYPO3 Company maintains a different pipeline for their internal content and content sourced from official partners. If you're an official partner, feel free to reach out to your contact person for more information.
This swim lane holds Trello cards for content that is still being written.
Needs review or proofreading
Trello cards move into this swim lane when the content they represent has been written and is ready for review and proofreading. The Content Group will pick up cards and assign a proofreader.
Reviewed and returned to author
When an article has been proofread, the Trello card representing it is moved into this swim lane. The author is notified by the proofreader and asked to review changes and suggestions.
Ready to publish
Once an article's author has reviewed and approved an article for publication, the Trello card representing it is moved into this swim lane. Cards in this lane can be published at typo3.org.
Articles in this swim lane usually have an assigned publication date (indicated by the Trello card's deadline field). The Content Group is responsible for assigning publication dates.
Published and ready for next newsletter
After an article or event has been published on typo3.org, the Trello card representing it is moved into this swim lane. The Published URL information in the description is updated and the deadline is set to completed.
Already published in newsletter
Once an article has been included in a published newsletter, the Trello card representing it is moved into this swim lane. The card will automatically be archived and disappear from view.
Blocked
Trello cards representing articles and events, whose progress is somehow blocked, are manually moved into this swim lane.
Labels
Within the Trello board, labels are used to indicate how the news articles or events should be treated.
Labels can be combined, as far as it makes sense.
The labels are listed in the order they have in Trello.
Medium Visibility
Color: yellow
Once published, the article or event should have social media mention.
The exact nature of the visibility outside of typo3.org is decided by the person responsible for social media in the TYPO3 Company.
High Visibility
Color: orange
A higher level of visibility than for the Medium Visibility label. Once published, the article or event should have social media mention at a favorable time, a banner on typo3.org, special graphics, etc.
The exact nature of the visibility outside of typo3.org is decided by the person responsible for social media in the TYPO3 Company.
Time Sensitive
Color: red
The item should be published sooner, rather than later.
From the TYPO3 Company
Color: violet
This article originates in the TYPO3 Company's content pipeline.
Talk with the person responsible for content publication at the TYPO3 Company before changing this item.
Press Release
Color: blue
This item represents a press release and will be published as such.
Visibility Near Deadline
Color: green
This item represents information about a time-limited opportunity, such as a vote or poll. It should be given additional visibility closer to the end of the time-limited period.
The exact nature of the visibility outside of TYPO3’s websites is decided by the person responsible for social media in the TYPO3 Company. For more information, see the list of press contacts.
Date Locked
Color: magenta
The item's publication date must not be changed.
Event
Color: dark gray
The Trello card represents an event, not a news article. Consequently, the information contained in the document should be published as an event, visible in the event listing. Event dates, etc., should be contained within the description text or attached document.
Writing Style Guide
By using this style guide we ensure that all written texts have the same general grammar and writing style — even when many people contribute. This guide should be easy to use, and it is based on the existing proto house style used at typo3.org.
We use the so-called Oxford (or serial) comma, setting a comma before the final “and” or “or” in a list with three or more items.
Examples:
Apples, orange, grapes, and bananas.
I eat Chinese gooseberries and pineapples.
Would you like potatoes, carrots, or leeks?
Currency
Currency values are written using the three-letter ISO code, followed by a space, followed by the value written according to our number style.
Currency symbols, such as € and $ can be used as a shortened form. They are placed in front of the value, with no space separating them.
Examples:
The tickets cost EUR 1,000.
We made a profit of exactly USD 25,060.17.
Grab it now, for just €1.
Dashes
We use an em-dashes with spaces around to mark parenthesis. We use n-dashes without spaces around to mark from–to in a number series.
Examples:
TYPO3 — not any other CMS — is my favorite.
There are 20–25 options available.
Dates
We prefer the international date style: day, month, and year. We always write the month name. Dates written as numbers only will cause confusion for our international audience. Years are always written in four digits.
Month names are normally written in full, but can be abbreviated if you lack space, as rendered by the PHP function date('M.'): Jan., Feb., Mar., Apr., May., Jun., Jul., Aug., Sep., Oct., Nov., and Dec.
Examples:
24 December 2018
12 Sep. 2009
Extensions
All extensions have a proper name in addition to the lowercase extension key. For example:
Name: AWS SDK for PHP
Key: aws_sdk_php
When we write about extensions, we use the proper name with the convention: "The [proper name] extension...".
On the first instance of the extension name in the text, we include the key in paranthesis immediately following the proper name. For example, "The AWS SDK for PHP (aws_sdk_php) extension...".
Where appropriate, on the first instance of the extension name in the text, we also include the link to the extension's page in the TYPO3 Extension Repository.
When we want to refer just to the key, for example in procedural or highly technical content, we prepend the key name with "EXT" in upper case, and we apply code formatting style to the text. For example, EXT:aws_sdk_php.
Numbers are written using a dot “.” as a decimal separator and comma “,” as a thousands separator. We normally use max two decimals. The number of decimals used should reflect the text's need for accuracy.
The thousands separator can be omitted for numbers 1,000–9,999.
A zero should be included before the dot in numbers less than 1.0.
Very large integer numbers (those above 999,999) should be written using million, billion, or trillion, replacing the last six or nine digits.
Numbers less than ten are spelt out, unless they are dates or part of a list with larger values.
Emphasis
We use italics for emphasis on single words or compound words. Bold text is used to increase visibility on words, compound words, parts of sentences, and sentences. We never use underlined text.
Examples:
Becoming a member is very important.
This year’s accounts are looking very good.
This text is not underlined for emphasis.
Examples:
The Association has 12,481 members.
The function nesting limit is set to 1000.
That is exactly 99.96% true.
The file has more than 30 million lines.
All of the three million TYPO3 users are geniuses.
Keeping diacritics is preferred, but not required.
Place names should always be introduced with their country. State or region is optional, but recommended where it can avoid misunderstanding. When not otherwise explained in context, the country and state/region is postfixed, separated by comma(s): [Place Name], [State/Region, ][Country].
Names of states and regions are never abbreviated.
Warning
Please note that transliterations are language-dependent. Both Japanese and Chinese use similar characters, so the characters for the Japanese town of Ōzora (大空町) is transliterated Ōzora-chō, while an errouneous Chinese transliteration may be *dakongting. TYPO3's built-in transliterator uses German transliteration, which is different to most English. In slugs, Gümüşhane in Turkey will erroneously be transliterated as *guemueshane, rather than gumushane.
Examples:
There are more than a hundred TYPO3 agencies in Munich, Germany.
New York, Lincolnshire, United Kingdom
Düsseldorf is the capital city of North Rhine-Westphalia, Germany.
The Swedish city of Gothenburg is north of Malmö.
Have you ever been to Ozora?
You'll find there's more than one Kandovan in Iran.
Portmanteaus With Single-Letter Prefix
Except for the word email, portmanteaus with single-letter prefixes, such as e-commerce and e-governance must be written with a dash separating the prefix from the rest of the word.
For product names and trademarks, the spelling and capitalization used by the owner should be used.
Examples:
e-commerce
e-governance
email
E-Governance In Title Case
eMac
Quotes
Exact quotes are written between double quotation marks. Quotes within quotes are written between single quotes. For long quoted sections, we use indented block quotations without quotation marks. Periods and commas are placed within quotation marks. Colons and semicolons are placed outside of quotation marks.
Changes and omissions within quotes are [in brackets].
Examples:
I felt great each time he said “I love TYPO3.”
“I love TYPO3,” he said enthusiastically.
He said he “ha[d] no idea why people said ‘hello’ all the […] time.”
The poem goes:
Roses are red
Violets are blue
Title Case
We capitalize all principal words of a title, including the first and the last words. We do not capitalize articles, prepositions or conjunctions that have fewer than four letters, such as:
a
an
and
at
but
by
for
in
nor
of
on
or
so
the
to
up
yet
To make things easy, use AP capitalization at capitalizemytitle.com, and be aware that we are using a somewhat simplified rule.
Examples:
TYPO3 Is Great
How to Configure Your Development Environment
Lists of Common Keywords
Global South
Anti-colonial
Civil society
Cost-effective
Democracy
Democratic principles
Digital infrastructure
Digital transformation
Efficient
Governance
Local
Locally-led
Non-exploitative
Secure
Skill development
Strategy (esp. cohesive strategy)
Sustainability
Examples
Sustainable, non-exploitative local economic cycles
Based on a cohesive strategy, solid governance, and a parallel program of local technical skill development
A cost-effective, efficient, and secure web presence
Government
Digital sovereignty
Governance
Secure
Strategy (esp. cohesive strategy)
Images and Licensing
Advertorial images for marketing and publicity purposes should be able to be shared and distributed by any community member without creating licensing issues. Therefore, when creating any image material relating to posts on typo3.org, please make sure to use images with one of the following licenses:
CC BY
This license allows reusers to distribute, remix, adapt, and build upon the material in any medium or format, so long as attribution is given to the creator. The license allows for commercial use.
When using a CC BY licensed image, credit must be given to the creator.
CC BY-SA
This license allows reusers to distribute, remix, adapt, and build upon the material in any medium or format, so long as attribution is given to the creator. The license allows for commercial use. If you remix, adapt, or build upon the material, you must license the modified material under identical terms.
When using a CC BY-SA licensed image, credit must be given to the creator and adaptions must be shared under the same license.
CC BY-ND
This license allows reusers to copy and distribute the material in any medium or format in unadapted form only, and only so long as attribution is given to the creator. The license allows for commercial use.
When using a CC BY-SA licensed image, credit must be given to the creator and no adaptations of the work are permitted.
CC 0
CC 0 (CC Zero) is a public dedication tool, which allows creators to give up their copyright and put their works into the worldwide public domain. CC0 allows reusers to distribute, remix, adapt, and build upon the material in any medium or format, with no conditions.
Please stay away from any licenses, forbidding the commercial use, distribution or usage of an image without dedicated agreement from the creator itself.
Guidelines for News Articles
This guide helps authors create useful, accurate, and consistent articles suitable for
news.typo3.com.
For detailed rules on language, grammar, links, dates, numbers, quotations,
and capitalization, see the Writing Style Guide.
These guidelines describe editorial principles. The Content Group
may edit submitted content for clarity, accuracy, consistency,
accessibility, legal compliance, or other legitimate editorial reasons.
AI-generated or AI-assisted content has been checked for accuracy.
1. Defining TYPO3 News
TYPO3 News is the shared platform for news
and events publication for the TYPO3 ecosystem: TYPO3 CMS, the TYPO3
community, teams, initiatives, events, and other activities relevant to
TYPO3.
The TYPO3 Association and TYPO3 Company are the responsible publishers.
The site features original content and does not re-publish articles, with
the exception of English translations of articles published elsewhere in
other languages. Some articles are made available in other languages of
the typo3.com website.
TYPO3 News is an editorial publication, not an advertising platform. Its
purpose is to inform readers, document activities, share knowledge, and help
people understand and participate in the TYPO3 ecosystem.
2. Who Can Contribute
Anyone involved in the TYPO3 community can submit article ideas and content.
You do not need to be a member of a particular team or have a long contribution
history.
If you have useful information but do not feel confident writing the article
yourself, ask for editorial support.
Possible support includes:
Developing an article from an idea
Copyediting and improving readability
Proofreading
Translating content into English
Important
Authors remain responsible for providing accurate information and for having
the necessary rights and permissions for submitted material.
3. What We Publish
TYPO3 News articles cover topics such as:
News about TYPO3 CMS development and releases
Reports from TYPO3 teams, units, and initiatives
Community news and community projects
Event announcements and event reports
Solutions to problems and other useful technical content
Interviews and profiles
Governance and organizational news
Announcements from the TYPO3 Association or TYPO3 Company
Stories about people contributing to TYPO3
Relevant developments in open source, web development, and related
technologies
TYPO3 News has an international audience with different levels of technical
knowledge.
Write for readers who may be:
Experienced TYPO3 developers
TYPO3 editors and integrators
Agency or business professionals
Community members
People discovering TYPO3 for the first time
People interested in open source and web technologies
Do not assume that every reader knows the history or context. Provide
enough information for the reader to understand why the article matters.
Explain specialized terms when they are important to understanding the
article. Link to useful explanations where appropriate.
5. Editorial Principles
TYPO3 News content should be:
Useful
Give readers information, knowledge, context, or a clear way to take
action.
Factual
Distinguish facts from opinions, plans, proposals, and expectations.
Transparent
Clearly identify the organization, team, project, or person responsible
for statements and decisions. With very few exceptions, each article is
published under a single writer's full name (byline).
Accessible
Write so that readers with different backgrounds can understand the
main message.
Respectful
Follow the TYPO3 Code of Conduct and treat
people, organizations, and communities fairly.
Non-sensational
Avoid exaggerated claims, clickbait, artificial urgency, and unsupported
superlatives.
Editorial, rather than promotional
Articles should inform readers rather than primarily promote a product,
service, company, event, or person.
6. Types of Articles
Different topics benefit from different formats. Choose the format that best
serves the reader.
News or announcement
Reports something new, such as a release, decision, organizational
change, or important development.
Community report
Describes an activity, project, meeting, sprint, or initiative and its
results.
Event announcement
Provides useful information about an upcoming event and explains why it
is relevant to TYPO3 readers.
Event report
Summarizes what happened at an event, including relevant outcomes,
contributions, and next steps.
Best practice or how-to
Explains how results were accomplished with reference to a concrete
case and problem. Generic tutorials belong in the documentation.
Case studies are not published as TYPO3 News.
Interview or profile
Presents a person, team, or project through questions, answers, or a
structured profile.
Opinion
Presents an individual's perspective or argument. Make it clear that the
content represents an opinion rather than an official TYPO3 position.
Governance or organizational article
Explains decisions, processes, structures, policies, or other
organizational developments. Be precise about what was proposed,
discussed, decided, or implemented.
7. Structure of an Article
A typical news article works well with the following structure:
Headline
Clearly states what the article is about.
Lead
Summarizes the most important information and gives the reader a reason
to continue. Capped at 2–3 short sentences, it is also displayed in news
lists.
Context
Usually 1–3 paragraphs before the first section heading. Contains information
needed to understand the context and background of the article.
Main content
Split the content into descriptive section headings followed by 2–4 paragraphs
of text.
Next steps
Explains what happens next, when this is relevant to the story.
Call to action
If readers can take a useful action, such as registering for an event,
reading documentation, joining a discussion, or testing a release, tell
them how. If the purpose is clear already at the beginning of the article,
a call to action link can also be inserted between Context and Maincontent.
Tip
Use headings to break up longer articles. Cap paragraphs at 2–3 sentences
and give each paragraph one main idea. Do not add information just to make
the article longer.
8. Headlines and Leads
A headline should tell readers what the article is about without requiring
additional context.
Prefer specific headlines over vague or promotional ones.
Good:
TYPO3 14.3.5 and 13.4.33 Security Releases Published
Avoid
Important News You Don't Want to Miss
A lead should communicate the central news quickly. It should normally
answer the most important questions of what happened, who is involved, and
why it matters.
Do not repeat the headline word for word in the lead.
Avoid beginning with generic statements such as "We are excited to
announce..." unless the wording is genuinely relevant to the story.
Follow the Writing Style Guide for title
capitalization and other language rules.
9. Tone and Voice
Use a clear, professional, and approachable tone.
Prefer:
Short, direct sentences
Active voice where it improves clarity
Concrete descriptions
Plain language
Specific names and dates
Factual statements supported by evidence
Avoid:
Marketing language
Unnecessary jargon
Exaggerated claims
Vague corporate language
Excessive use of exclamation marks
Artificial urgency
Language that assumes the reader already agrees with the author
All articles must be written in English. TYPO3 uses American (US) spelling.
See the Writing Style Guide for detailed rules.
10. Attribution and Organizational Identity
The shared news platform brings together content from different parts of
the TYPO3 ecosystem. Readers must be able to distinguish between them.
Use the specific name of an organization, team, or project when it matters.
For example:
"The TYPO3 Association Board approved ..."
"TYPO3 Company announced ..."
"The Core Team released ..."
"The Security Team published ..."
"The TYPO3 Association is asking members to ..."
Avoid statements such as "TYPO3 decided ..." when the decision was actually
made by a specific body.
Do not imply that a personal opinion represents the position of anyone else
unless you are authorized to speak on their behalf.
For governance articles, distinguish carefully between information that was:
Discussed
Proposed
Submitted for review
Approved
Decided
Implemented
Planned
Name people accurately and use their current role when the role is relevant
to the article. Link names to their profile on my.typo3.org.
11. Links
Links should help readers understand the article or take a relevant action.
We prefer relevant TYPO3 web properties where they provide the appropriate
information, but can link to external sites when they provide a concrete
benefit to the reader.
Never use URLs in article text and prefer descriptive link text rather than
"click here", "this", or similar expressions.
Do not link to external content advertising commercial or paid products or
services unless an official TYPO3 endorsement exists.
12. Images
All articles have at least one accompanying image or illustration. If you're
unable to find one, it will be found for you during the publication process.
Images should support the article and provide useful visual context.
Only use images for which TYPO3 has the necessary rights to publish,
distribute, and, where applicable, modify the image.
Refrain from overly editing or cropping images before submitting. Always include
the following information:
Creator or copyright holder
Source
Concrete license
Any required attribution
If people are recognizable in an image, make sure you have their consent
before submitting it.
13. Quotes
Use quotation marks only when restating a person's exact words or quoting
a text. Do not use quotation marks for names or titles.
Minor grammatical corrections or necessary contextual changes must follow
the rules for quotes in the Writing Style Guide.
If a quote was supplied by another source, verify that you have the right
to reproduce it and identify the source where appropriate.
14. Facts and Sources
You are responsible for the factual accuracy of submitted content.
Distinguish clearly between facts and statements.
For example, prefer:
"The TYPO3 Association announced that ..."
over:
"TYPO3 is now the market leader ..."
unless the latter statement can be supported by a reliable source and is
relevant to the article.
Do not present rumors, internal discussions, proposals, or expectations as
facts.
Where a claim is important to the story, provide a source or link that
allows readers to verify it.
15. Promotional and Commercial Content
Articles should focus on information that is useful to readers.
It is not permitted to place any advertisements or other commercial promotion
in articles or make the article a vehicle for commercial gain.
Exceptions to the rule:
Any case where an official TYPO3 endorsement exists.
Open source products where voluntary donations are possible, but they do not
exceed a product's actual costs of design, development, and maintenance.
Examples of articles with commercial intent:
Direct product promotion: The article primarily concerns a commercial
product or service.
Promotional case study: A case study that promotes an agency, vendor, or
service provider, rather than TYPO3.
Commercial dependency or freemium: The article concerns a free product or
service that requires payment to become useful or that requires a commercial
product or service to function.
Commercial upselling: An otherwise useful article directs readers toward
paid services for the next step.
Promotional comparison: A comparison favors a commercial product,
provider, or service without sufficient editorial justification.
Links to commercial services: The article links to pages promoting
commercial products or services.
Lead generation: The article encourages readers to contact a company,
request a quote, book a consultation, or otherwise become a commercial lead.
Commercial testimonials: A story primarily serves as a testimonial for a
commercial product or service.
Educational sales content: A tutorial, technical article, or other
educational content primarily serves to promote the author's commercial
services.
The Writing Style Guide also gives
directions on what commercial content can be linked from articles.
Writers should keep their texts factual and neutral, and not seek to
create, encourage, or participate in conflicts or disputes through their
content.
Unless permission is given by the TYPO3 Association or TYPO3 Company,
articles about sensitive topics can only be published under bylines of
official TYPO3 representatives. These topics include:
Conflicts and disputes
Legal matters (including legal advice)
Security incidents
Internal or confidential information
Information that has not yet been publicly announced
17. AI-Assisted Writing
AI tools may be used to help develop, translate, edit, or proofread an
article, but they do not replace editorial responsibility. Authors remain
responsible for their content.
Do not publish AI-generated claims without checking them against reliable
sources. AI tools can produce plausible but incorrect names, dates, quotes,
statistics, references, and technical information.
How to Get an Article Published in TYPO3 News
Why publish in TYPO3 News?
By providing a steady stream of content about the vibrant activity in the TYPO3 community, we help it grow stronger.
Your news makes a big difference. Reports from events help participants feel recognized for their contributions. News about TYPO3 development, especially from teams and initiatives, keeps everyone in the community in the loop. For newcomers, this steady stream also helps them see where the action is, and where they can get involved.
What do you need to get started?
All community members can submit content for publishing on news.typo3.com. You’ll need a typo3.org account and a TYPO3 Slack account, and you're ready to start.
The TYPO3 Content Group manages a lot of the content on typo3.org. While you don't have to be a member of the group to get published, you can certainly get involved, if you like.
What Types of Submissions are Welcome?
Wondering what kind of content you can submit? Some ideas:
So you’ve got an idea for an article but not confident with writing in English on an international stage?
No problem. We have a diverse international community, and we want to make sure the barriers for participating in publishing content are as low as possible. So if you need help to translate and copy-edit your article, we still want to hear from.
Writing — If you have an idea, we can help find someone to write it for you.
Translation — Bring us an article in any language and we’ll translate it. We also have translators to produce press releases in multiple languages.
Improving/Copyediting — Need some help to improve the readability of your article in English?
Proofreading — A light pass on the English language grammar, spelling, and some error-checking.
Submission Process
Submit
To start, you’ll have to complete the content request form. Tell us about the content you want to submit, and what kind of support you need. Ideally, we’d like to use Google Docs for editing. If you can make it possible to view and comment on the Google Doc, then we can review it and delegate it. Then we’ll request edit access for those individuals or move the document into the shared directory for the TYPO3 Content Team.
Delegate
This will log a ticket into the TYPO3 Content Trello Board. The board is publicly available and you can use it to track the status of your submission.
A member of the Content Group will find your submission in the board. The article will receive a tentatie publication date. This date depends on your article, resource availability, and space in the publication pipeline. We are aiming to keep the time it takes to get something published as short as possible.
Escalate
If you have an urgent request, please come into the #t3a-content-group channel in TYPO3 Slack to tell us you have an urgent matter that needs priority. We will do our best to accommodate your need.
Promote
Your article may be shared on social media and TYPO3’s newsletters, such as the TYPO3 Association Newsletter.
You Can Meet is an optional section in event listings and on event single-view pages on typo3.org. This is a list of people central to the TYPO3 community who will be taking part in the event.
An example You Can Meet listing in an event single-view on typo3.org.
Desired outcome
By highlighting who you can meet at an event, we hope more people will sign up for the events. We also hope that it will work as an invitation to contact the listed people, thereby increasing community involvement and encouraging contribution.
Who can be listed
TYPO3 Association Board members
TYPO3 Association Business Control Committee (BCC) members.
TYPO3 Company Supervisory Board members
TYPO3 Company or Association Employees (designated by the respective board/CEO)
TYPO3 Core Mergers
TYPO3 Team Leads and Co-Leads
Persons appointed by the TYPO3 Association Board
Ordering in lists
Names are first ordered according to the prominence of a person's role:
The role's position the bullet list above.
Any prominence within the role. E.g, president before, vice president, treasurer, secretary, and others, and leader over co-leader.
Alphabetically, by first name.
This is based on the the assumption that the people with the most central positions are most important to meet.
Limit
Only the topmost 10 participants will be listed. This is due to a technical limitation and may be changed in the future.
Requirements
If you're in the list, you're no longer just representing yourself and your company, but you're also a face for people new to TYPO3 to approach about our beloved CMS.
As a representative of TYPO3, you must follow TYPO3's Code of Conduct and the Code of Conduct of the event. When the two codes conflict, the strictest of the codes should be followed.
Meet TYPO3
Every year, many central members of the TYPO3 community are present at external events outside of the TYPO3 community. By advertising these events through TYPO3's websites and social media, potential participants will be encouraged to attend the event and approach the TYPO3 representatives, creating positive synergies for the TYPO3 project and the world-wide open source community.
Opportunities
When representatives of TYPO3 are present at external events, it can be a part of Meet TYPO3 and an opportunity for:
Interaction and collaboration with other open-source communities.
Mutual learning and insights across technological, cultural, and national borders.
Outreach and increased visibility in new and existing markets.
Requirements
Meet TYPO3 event participation has the same requirements as participation in the You Can Meet listing, plus:
Those who would like to participate at a Meet TYPO3 event must apply by email to Mathias Bolt Lesniak.
The event must be listed as an event in the category Meet TYPO3 at typo3.org. The event description must describe the event in positive terms and outline how participation in the event is expected to benefit other participants.
As TYPO3 is participating as a guest at the event, our participation should always be constructive, positive, and support the intention of the event. Inappropriate marketing and sales activities are not allowed.
The people who participate as TYPO3 representatives must write an event report for publication at typo3.org. The report should briefly describe the event and results in respect to the intended Opportunities.
Ticket and Travel Support
A budget is available for covering a single person's participation expenses for each each event:
