From fa77cef5f222e0b5ddda0b110badb3961e9d5313 Mon Sep 17 00:00:00 2001 From: Daniel Siepmann Date: Wed, 8 Feb 2023 13:31:39 +0100 Subject: [PATCH] [TASK] Explain the extension name (#741) Some might find the extension name confusing. We therefore explain why we don't add `_example` or something else. Resolves: #692 --- Documentation/Introduction.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/Documentation/Introduction.rst b/Documentation/Introduction.rst index c04ef53..e1ee7c3 100644 --- a/Documentation/Introduction.rst +++ b/Documentation/Introduction.rst @@ -24,6 +24,19 @@ continuous integration (CI). Use `EXT:extension_builder `__ 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 `__. + .. _presentation-online-days-2021: Presentation at the TYPO3 Online Days 2021