chore(docs): reorder README.md

README.md

@@ -4,45 +4,6 @@ This module creates a SES Identity.
 It also supports further configuration like the usage of a configuration set for the identity, or adding a custom FROM domain.
 Optionally it creates validation records for SPF, DKIM and DMARC in a given Route 53 Zone.
 
-# Contents
-
-## package.json
-
-The `package.json` is required for the [semantic-release](https://semantic-release.gitbook.io/semantic-release/). This is controlled via a Github Actions workflow.
-
-## pre-commit-config.yaml
-
-We rely on [pre-commit](https://pre-commit.com/) hooks to ensure the good code quality. This is also checked by a CI pipeline but recommended to use locally. It's also responsible for creating [terraform-docs](https://terraform-docs.io/).
-
-## .github/workflows
-
-We have several default workflows prepared.
-
-### checkov
-
-[checkov](https://www.checkov.io/) scans the terraform manifests for common misconfigurations. By default the root of the repository is scanned but if you have a repo with submodules (like for e.g. [makandra/terraform-aws-modules](https://github.com/makandra/terraform-aws-modules) you may want to alter the path of the GitHub action.
-
-### conventional-commits
-
-We want to enforce [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) to ensure our `semantic-release` works correctly.
-
-### precommit
-
-We want to ensure that all our rules in the `pre-commit` configuration are applied.
-
-### semantic-release
-
-Whenever new commits are merged into the `main` branch we want a new release to be created.
-
-### tflint
-
-Terraform linter for finding possible errors, old syntax, unused declarations etc. Also it enforces best practices. See [tflint](https://github.com/terraform-linters/tflint).
-By default the root of the respository is scanned but if you have a repo with submodules (like for e.g. [makandra/terraform-aws-modules](https://github.com/makandra/terraform-aws-modules) you should add every submodule to the workflow matrix.
-
-# Recommended Repo configuration
-
-We recommend protecting the `main` branch and to allow new code pushes only via Pull Requests. This way it's ensured that all tests pass before a new release is pushed.
-
 <!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
 ## Requirements
 
@@ -93,3 +54,43 @@ We recommend protecting the `main` branch and to allow new code pushes only via
 | <a name="output_ses_domain_identity_arn"></a> [ses\_domain\_identity\_arn](#output\_ses\_domain\_identity\_arn) | The ARN of the SES domain identity |
 | <a name="output_spf_record"></a> [spf\_record](#output\_spf\_record) | The SPF record for the domain. This is a TXT record that should be added to the domain's DNS settings to allow SES to send emails on behalf of the domain. |
 <!-- END OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
+
+
+# Contents
+
+## package.json
+
+The `package.json` is required for the [semantic-release](https://semantic-release.gitbook.io/semantic-release/). This is controlled via a Github Actions workflow.
+
+## pre-commit-config.yaml
+
+We rely on [pre-commit](https://pre-commit.com/) hooks to ensure the good code quality. This is also checked by a CI pipeline but recommended to use locally. It's also responsible for creating [terraform-docs](https://terraform-docs.io/).
+
+## .github/workflows
+
+We have several default workflows prepared.
+
+### checkov
+
+[checkov](https://www.checkov.io/) scans the terraform manifests for common misconfigurations. By default the root of the repository is scanned but if you have a repo with submodules (like for e.g. [makandra/terraform-aws-modules](https://github.com/makandra/terraform-aws-modules) you may want to alter the path of the GitHub action.
+
+### conventional-commits
+
+We want to enforce [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) to ensure our `semantic-release` works correctly.
+
+### precommit
+
+We want to ensure that all our rules in the `pre-commit` configuration are applied.
+
+### semantic-release
+
+Whenever new commits are merged into the `main` branch we want a new release to be created.
+
+### tflint
+
+Terraform linter for finding possible errors, old syntax, unused declarations etc. Also it enforces best practices. See [tflint](https://github.com/terraform-linters/tflint).
+By default the root of the respository is scanned but if you have a repo with submodules (like e.g. [makandra/terraform-aws-modules](https://github.com/makandra/terraform-aws-modules)) you should add every submodule to the workflow matrix.
+
+# Recommended Repo configuration
+
+We recommend protecting the `main` branch and to allow new code pushes only via Pull Requests. This way it's ensured that all tests pass before a new release is pushed.