[RELEASE] 13.0.0 -- TYPO3 v13 compatibility, features & bugfixes

- support of site sets
- support of TYPO3 country API
- improve accessibility of fe forms
- enable conditions for multistep forms together with EXT:powermail_cond

Related: #943

Author: mschwemer

Readme.md

@@ -1,7 +1,7 @@
 # TYPO3 Extension powermail
 
 Powermail is a well-known, editor-friendly, powerful and easy to use mailform extension for TYPO3 with a lots of
-features (spam prevention, marketing information, optin, ajax submit, diagram analysis, etc...)
+features (spam prevention, marketing information, optin, ajax submit, diagram analysis, etc...).
 
 ## 1. Documentation overview
 
@@ -12,7 +12,6 @@ features (spam prevention, marketing information, optin, ajax submit, diagram an
 * [Documentation for developers](/Documentation/ForDevelopers/Index.md)
 * [Documentation for developers](/Documentation/ForDevelopers/Index.md)
 * [FAQ](/Documentation/FAQ/Index.md) (with a lot of stuff and best practice)
-* [Changelog](/Documentation/Changelog/Index.md)
 * [Support](/Documentation/Support/Index.md)
 * [Additional links](/Documentation/Links/Index.md)
 
@@ -27,7 +26,7 @@ Quick guide:
 
 ## 3. Administration corner
 
-### 3.1. Versions and Support
+### 3.1 Versions and Support
 
 | Powermail   | TYPO3     | PHP       | Support/Development                           |
 |-------------|-----------|-----------|-----------------------------------------------|
@@ -44,11 +43,7 @@ Do you need free support? There is a kind TYPO3 community that could help you.
 You can ask questions at https://stackoverflow.com and tag your question with `TYPO3` and `Powermail`.
 In addition there is a slack channel in the TYPO3 slack `ext-powermail`.
 
-### 3.2. Changelog
-
-Please look into the [changelog of powermail](/Documentation/Changelog/Index.md)
-
-### 3.3. Suggested Extensions for powermail
+### 3.2 Suggested Extensions for powermail
 
 - **email2powermail** Automatically convert emails to a link to a powermail form [Link](https://github.com/einpraegsam/email2powermail)
 - **powermailrecaptcha** Google recaptcha [Link](https://github.com/einpraegsam/powermailrecaptcha)
@@ -57,25 +52,20 @@ Please look into the [changelog of powermail](/Documentation/Changelog/Index.md)
 - **powermail_cond** Add conditions (via AJAX) to powermail forms for fields and pages [Link](https://github.com/einpraegsam/powermail_cond)
 - **powermail_fastexport** Extend powermail for faster export to .xlsx / .csv files. This is useful if you have many records to be exported. [Link](https://github.com/bithost-gmbh/powermail_fastexport)
 
-### 3.4. Product Owner
+### 3.3 Product Owner
 
 The product owner and author of the extension is Marcus Schwemer from [in2code](https://www.in2code.de). Beside that every
 in2code colleague is allowed to support further development if she/he wants. In addition there are a lot of other
 contributors that helped to improve the extension with their *Pull Requests* - thank you for that!
 
-### 3.5. Release Management
+### 3.4 Release Management
 
 Powermail uses **semantic versioning** which basically means for you, that
 - **bugfix updates** (e.g. 1.0.0 => 1.0.1) just includes small bugfixes or security relevant stuff without breaking changes.
 - **minor updates** (e.g. 1.0.0 => 1.1.0) includes new features and smaller tasks without breaking changes.
 - **major updates** (e.g. 1.0.0 => 2.0.0) normally includes basic refactoring, new features and also breaking changes.
 
-We try to mark breaking changes in the [changelog](/Documentation/Changelog/Index.md)
-with a leading **!!!** and try to explain what to do on an upgrade (e.g. VieHelper name changed from vh:foo to vh:bar in templates).
-
-Based on `release early, release often` we try to release new versions as often as possible into TER and to github/packagist.
-
-### 3.6. Automatic Testing
+### 3.5 Automatic Testing
 
 #### Behaviour tests
 
@@ -92,7 +82,7 @@ See [readme.md](/Tests/Behavior/readme.md) for some more information about behat
 At the moment powermail offers many unit tests that have to be passed before every release. See more information
 about unit tests or code coverage in powermail in the [readme.md](/Tests/Unit/readme.md)
 
-### 3.7. Code quality
+### 3.6 Code quality
 
 Beside respecting PSR-12 and TYPO3 coding guidelines, it's very important for the project to leave a file cleaner as before.
 Especially because it's a really large extension with a lot of functionality and a history of over 17 years (!) and of course some
@@ -105,7 +95,7 @@ Current quality tools are:
 - php linter
 - TypoScript linter
 
-### 3.8. Contribution
+### 3.7 Contribution
 
 **Pull requests** are welcome in general! Nevertheless please don't forget to add a description to your pull requests. This
 is very helpful to understand what kind of issue the **PR** is going to solve.
@@ -116,7 +106,7 @@ to accept only bugfixes if I can reproduce the issue.
 even more complicated in usability for an edge case feature. Please discuss a new feature before.
 
 
-### 3.9. Development
+### 3.8 Development
 
 Compile and minify (uglify) JavaScript, compress CSS:
 
@@ -129,17 +119,17 @@ $ ./node_modules/.bin/gulp
 
 ## 4. Screenshots
 
-### 4.1. Example form with bootstrap classes:
+### 4.1 Example form with bootstrap classes:
 
 ![Example form](Documentation/Images/frontend1.png "Example Form")
 
 
-### 4.2. Backend module mail list:
+### 4.2 Backend module mail list:
 
 ![Backend Module](Documentation/Images/backend1.png "Backend Module")
 
 
-### 4.3. Backend module reporting:
+### 4.3 Backend module reporting:
 
 ![Backend Module2](Documentation/Images/backend2.png "Backend Module2")