Skip to content

Commit 1c36150

Browse files
[TASK] Make introduction quick and short (#5089)
* [TASK] Make introducition quick and short Releases: main, 13.4, 12.4 * [TASK] Add minor language corrections Releases: main, 13.4, 12.4 --------- Co-authored-by: Sarah McCarthy <[email protected]>
1 parent f808799 commit 1c36150

File tree

2 files changed

+91
-62
lines changed

2 files changed

+91
-62
lines changed
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
.. include:: /Includes.rst.txt
2+
3+
.. _system-overview:
4+
.. _overview:
5+
6+
===============
7+
System Overview
8+
===============
9+
10+
The TYPO3 system is multi-layered. The backend and frontend user interfaces
11+
sit on top of the application layer, which in turn sits on top of the infrastructure
12+
layer. The webserver, database and PHP in the infrastructure layer are
13+
prerequisites for running TYPO3.
14+
15+
The TYPO3 Core primarily consists of an API (Application Programming Interface),
16+
which defines a framework for managing content in the project. The API
17+
includes functionality for content storage, user permissions and access, content
18+
editing, and file management. This functionality is delivered via system
19+
**extensions** that use the API. All of the content is stored in a database
20+
that TYPO3 accesses via the API.
21+
22+
Extensions are clearly defined parcels of code, such as plugins, backend
23+
modules, application logic, skins, and third-party apps.
24+
25+
The most important thing to note is that the TYPO3 CMS consists solely
26+
of extensions. The most basic functions are packaged in a system extension called
27+
"core".
28+
29+
.. figure:: /Images/Graphics/Typo3CmsStructure.svg
30+
:alt: TYPO3 System layers diagram
31+
:class: with-border
32+
:width: 800px
33+
34+
Diagram showing the layers of the TYPO3 system
35+
36+
.. _system-overview-application:
37+
38+
Application layer
39+
=================
40+
41+
The TYPO3 Core framework interacts with system and 3rd party extensions via
42+
the TYPO3 extension API.
43+
44+
The core and extensions interact with each other seamlessly and operate as a
45+
single, unified system.
46+
47+
.. _system-overview-ui:
48+
49+
User interface layer
50+
====================
51+
52+
The backend is the **content-creation** side. It is an administrative area
53+
where you can manage content and configuration based on the extensions that are
54+
installed.
55+
56+
The frontend is the **content-delivery** side. Typically a website, it is the
57+
meeting point for templates, CSS, content, and logic from extensions,
58+
delivering your project to the world.
59+
The frontend doesn't have to be a website, it can be a native mobile
60+
application, a web application built in a frontend framework, or an API to
61+
interface with other systems.
Lines changed: 30 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -1,83 +1,51 @@
11
.. include:: /Includes.rst.txt
2-
32
.. _introduction:
43

54
============
65
Introduction
76
============
87

9-
.. _system-overview:
10-
.. _overview:
11-
12-
System Overview
13-
===============
14-
15-
The TYPO3 system is multi-layered. The backend and frontend user interfaces
16-
sit on top of the application layer, which in turn sits on the infrastructure
17-
layer. The webserver, database and PHP in the infrastructure layer are
18-
prerequisites for running TYPO3.
19-
20-
TYPO3 Core primarily consists of the API (Application Programming Interface),
21-
which defines a framework for managing the project content. The base features
22-
of the API include content storage, user permissions and access, content
23-
editing, and file management. These features are delivered via system
24-
**extensions** that use the API. All of the content is stored in a database
25-
that TYPO3 then accesses via the API.
26-
27-
Extensions are clearly confined code additions, such as plugins, backend
28-
modules, application logic, skins, and third-party apps.
29-
30-
The most important thing to note is that everything is an extension in TYPO3
31-
CMS. Even the most basic functions are packaged in a system extension called
32-
"core".
8+
TYPO3 is a content management system based on PHP.
9+
The :ref:`TYPO3 - Getting Started Tutorial <t3start:start>` gives you an
10+
introduction to the core concepts of TYPO3 and will help you to kickstart your
11+
first project.
3312

34-
.. figure:: /Images/Graphics/Typo3CmsStructure.svg
35-
:alt: TYPO3 System layers diagram
36-
:class: with-border
37-
:width: 800px
13+
.. _introduction-installation:
3814

39-
Diagram showing the layers of the TYPO3 system
15+
A basic TYPO3 installation
16+
==========================
4017

18+
Installation with Composer is covered in the Getting Started Guide
19+
(see :ref:`Installation <t3start:installation_index>` chapter).
4120

42-
Application layer
43-
-----------------
21+
You can also `download TYPO3 from our official page <https://get.typo3.org/version/13>`_
4422

45-
The TYPO3 Core framework interacts with system and 3rd party extensions via
46-
the TYPO3 extension API.
23+
If you are starting out we would suggest using the latest TYPO3 version with
24+
long term support.
4725

48-
The core and extensions interact with each other seamlessly and operate as a
49-
single, unified system.
26+
.. _introduction-site-package:
5027

51-
User interface layer
52-
--------------------
28+
A basic site package
29+
====================
5330

54-
The backend is the **content-creation** side. It is the administrative area
55-
where you manage content and configuration based on the extensions that are
56-
installed.
31+
To get started you need a basic
32+
`site package <https://docs.typo3.org/permalink/t3coreapi:site-package>`_.
5733

58-
The frontend is the **content-delivery** side. Typically a website, it is the
59-
meeting place for templates, CSS, content, and logic from extensions,
60-
delivering your project to the world.
61-
The frontend doesn't have to be a website, it could be a native mobile
62-
application, a web application built in a frontend framework, or an API to
63-
interface with other systems.
34+
You can use the `official Site Package Builder <https://get.typo3.org.ddev.site/sitepackage>`_
35+
to generate one for you or follow the :ref:`site package tutorial <t3sitepackage:start>`.
6436

65-
.. _introduction-installation:
66-
67-
A basic installation
68-
====================
37+
.. _introduction-getting-help:
6938

70-
To follow this document, it might help to have a totally trimmed down
71-
installation of TYPO3 with *only* the Core and the required system
72-
extensions at hand.
39+
Getting help with TYPO3
40+
=======================
7341

74-
The installation process is covered in the :doc:`Getting started
75-
Guide <t3start:Index>`.
76-
You should perform the basic installation steps and not install any
77-
distribution. This will give you the "lightest" possible version of TYPO3.
42+
`Meet the TYPO3 Community <Meet the TYPO3 Community>`_. You can chat with us
43+
`on Slack <https://typo3.org/community/meet/chat-slack>`_, go to meetings in
44+
your `local user group <https://typo3.org/community/meet/user-groups>`_ or
45+
meet us at `events <https://typo3.org/community/events>`_.
7846

79-
In your basic installation, go to the :guilabel:`Admin Tools > Extensions`
80-
module. You will see all extensions installed by Composer are activated by
81-
default.
47+
You can discuss TYPO3 related questions in the https://talk.typo3.org/ forum.
8248

83-
.. include:: /Images/AutomaticScreenshots/Introduction/ExtensionsMinimalList.rst.txt
49+
If you think you have found a bug in the TYPO3 Core code, have a look at our
50+
`issue tracker on forge <https://forge.typo3.org/projects/typo3cms-core/issues>`_
51+
where you can check if the bug has already been reported or not.

0 commit comments

Comments
 (0)