TYPO3 has two main websites and act as hubs for distinct target personas. Articles can be suitable for multiple personas, but for simplicity's sake, they usually fit only one of the hubs:
typo3.com: Business Hub
typo3.org: Community Hub
Tip
Cross-posting on both websites can happen, but the article itself should be hosted on only one of the websites. The other website should use an external link to the article and not repeat the content. If uncertain, typo3.com targets higher levels of the funnel, so it's usually the best place to host cross-posted articles.
Original content
Both sites only feature original content and do not re-publish articles from other sources. However, the typo3.org does occasionally publish English translations of articles first published in other languages.
Articles for typo3.com
Note
Articles on typo3.com are published in the Blog.
TYPO3 Product
Presenting the Product
Product Feature Highlights
Major Version Releases
Higher Education Package
Official integrations
Official Services
ELTS
SLA
PSL
Certifications
Project reviews
Announcing Sales-Enablement Materials
Presenting Case Studies
Events
Announcing and reporting official TYPO3 Events
Announcing and reporting community-external events
Press Releases
Guides and best practices (decision-makers, end-customers, sales)
Articles for typo3.org
Note
Articles on typo3.org are published as News.
Community News
Memberships
Team reports
Events
Announcing and reporting Community Events
TYPO3
Maintenance Release News
Security Release News
Development News
Podcast News
Tutorials and best practices (for agencies and other community folks)
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 typo3.com
Color: violet
This article originates at typo3.com and will be linked to the article at typo3.com.
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.
Talk with the person responsible for content publication at the TYPO3 Company before changing this item.
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.org is decided by the person responsible for social media in the TYPO3 Company.
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 without 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
Foreword
A lot of the news on the TYPO3 websites is community-created. This helps create a homebase for our community. The content should be neutral and offer reliable and useful information.
We accept articles about TYPO3 CMS, the TYPO3 community, web technologies, best practices for web development and other open source-related topics. Your content must hold certain licenses to be publishable on the site.
Guidelines
Attention
These guidelines may be updated at any time and without prior notice.
Language
The main language of the TYPO3 community is English. Therefore all articles must be written in English. Translations of an article to additional languages can be offered by the author.
Audience
The readers of our websites are technical and non-technical. Many are users of TYPO3 CMS and part of the TYPO3 community or interested in becoming part of it. They come from many different backgrounds and fields of study. We welcome all to learn more about TYPO3.
Images
Please take care that you use only license free images. Our recommendation is Creative Commons BY-SA 4.0. In any case, we need to know the source / author and concrete license type. This information has to be included in the metadata of this file. If you are depicting people within your pictures, you have to have the consent of depicted people.
Advertising
Generally, it is not permitted to place any advertisements in your article. The content should deliver technical information, best practices, release information, community news.
External Links
Links to external sites are permitted if they create a concrete benefit for the reader. Links to companies’ home pages are permitted as an acknowledgement for contribution to the product development or contribution to an official team.
Authors must respect the values of the TYPO3 community. Details see typo3.org/coc.
Respecting trademarks, copyrights, and project names
The use of trademarks or other projects as the sole or initial term is prohibited unless proof of legal ownership/representation can be confirmed.
Enforcing these guidelines
Our intent is to enforce these guidelines with as much fairness as humanly possible. However, we reserve the right to:
Update these guidelines at any time.
Disable or remove any article from the site, even for reasons not explicitly covered by the guidelines.
Make changes to an article, without the author's consent, particularly in the interest of public safety.
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:
