Spelling, terms and glossary
Spelling
This section defines how to spell certain trademark and product names. For a list of the TYPO3 terminology and their short descriptions, see Spelling and TYPO3 Terminology.
A
Apache,
API,
B
backend,
backend user,
Backend Users (module),
blog post, blogger, blogging,
C
code sprint,
command line, run something at the command line,
command-, run a command-line spell-checker,
Changelog,
checkbox,
Classic mode,
Composer,
Core Team, TYPO3 Core Team,
Core, TYPO3 Core,
Core extension,
cross-,
Crowdin,
CSV (comma separated values),
D
Data Processor,
DBAL,
DB Check (module),
Docker,
Docker Compose,
Doctrine,
Documentation Team, TYPO3 Documentation Team,
Data,
E
Edit on Git,
Edit on Git,
Edit on Git,
Extbase,
Extension Manager
extension,
F
Flex,
Fluid,
Fluid Styled Content,
Form,
frontend,
frontend rendering,
G
Git,
Git,
H
how to document,
how-, a how-,
I
Inno,
Introduction Package,
L
Link,
Linux,
M
Markdown,
mark up the text,
markup ,
Maria,
My,
mac, outdated: Mac, Mac OS X,
model-,
MVC,
N
nginx,
O
Open Source,
P
page TSconfig,
Php,
PHPStan,
PHPUnit,
PHP CS Fixer,
PHP_,
PNG,
Postgre,
Q
quick start,
R
Records (module),
re, re,
richt text editor,
RTE,
S
sitepackage,
Sphinx,
style guide , Styleguide ,
SVG,
system extension (not: 'sys extension'),
T
TCA,
TCE,
TCEforms,
TCEmain,
textrole,
third party extension,
toctree,
TSconfig,
TYPO3,
TYPO3 Core, Core,
TYPO3 Core Engine,
TYPO3 Core Team, Core Team,
TYPO3 Core Engine,
TYPO3 v12, TYPO3 v12., TYPO3 v12 LTS, TYPO3 version 12,
Typo,
U
UNIX,
V
View,
W
Windows, Microsoft Windows,
windows, modal windows,
Terms
How to use these terms:
- Backend Users
- Written as a proper noun when referring to the TYPO3 backend module for managing backend user accounts and groups, found at System > Backend Users. Before the module reorganization in TYPO3 v14, it was listed under "Admin Tools". Lowercase "backend user" still applies when talking about the user accounts themselves, not the module.
- Changelog
- The collection of per-release Core documentation entries (Breaking Change, Feature, Deprecation, Important) published for each TYPO3 Core version. Also referenced as "Core Changelog". Linked from upgrade guides across many TYPO3 documentation repositories, not just this one.
- Classic mode
- A TYPO3 installation mode where the full source tree, including the TYPO3 Core and all extensions, lives inside the web root. Contrast with Composer mode, where dependencies are managed by Composer outside the web root.
- DB Check
- Written as a proper noun when referring to the TYPO3 backend module (provided by typo3/cms-lowlevel ) for checking database consistency and integrity, found at System > DB Check.
- Fluid Styled Content
- The name of the TYPO3 system extension ( typo3/cms-fluid-styled-content ) that provides the default Fluid-based rendering for content elements. Also used adjectivally, for example "Fluid-Styled Content templates".
- Records
- Written as a proper noun when referring to the Contents > Records backend module, used to find or create records independently of their page context. Lowercase "records" still applies when talking about database records in general, not the module.
- reStructuredText
- Use
reas abbreviation.ST - reST
- reStructuredText is a 'Markup Syntax and Parser Component of Docutils'.
- TYPO3
- Always and everywhere written with capital letters.
- third party extension
- Do not write "3rd party extension".
- ViewHelper
- Our community agreed on this spelling.