danielsiepmann/tea
danielsiepmann/tea
1
0
mirror of https://github.com/FriendsOfTYPO3/tea.git synced 2024-11-22 08:36:12 +01:00
Code Activity

[TASK] Explain the extension name (#741)

Browse source 
Some might find the extension name confusing.
We therefore explain why we don't add `_example` or something else.

Resolves: #692
This commit is contained in:
Daniel Siepmann 2023-02-08 13:31:39 +01:00 committed by GitHub
parent 02ee56e042
commit fa77cef5f2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
Documentation/Introduction.rst
View file

@ -24,6 +24,19 @@ continuous integration (CI).
Use `EXT:extension_builder <https://extensions.typo3.org/extension/extension_builder>`__ Use `EXT:extension_builder <https://extensions.typo3.org/extension/extension_builder>`__
in order to kickstart a new extension. in order to kickstart a new extension.
.. _why-is-this-extension-called-tea:
Why is this extension called "tea"?
===================================
Good extension names cover the domain of their purpose.
This extension is about managing teas. That's why the name "tea" is a good fit.
We could also add `_example` to the name in order to state that this extension is an example.
But that would already break with our goal to provide a best practice.
This is not related to the `tea package manager <https://tea.xyz/>`__.
.. _presentation-online-days-2021: .. _presentation-online-days-2021:
Presentation at the TYPO3 Online Days 2021 Presentation at the TYPO3 Online Days 2021