diff --git a/README.md b/README.md
index 78b14528..e432ad2b 100644
--- a/README.md
+++ b/README.md
@@ -1,93 +1,116 @@
-# antsibull -- Ansible Build Scripts
-[](https://matrix.to/#/#antsibull:ansible.com)
-[](https://github.com/ansible-community/antsibull/actions/workflows/nox.yml)
-[](https://github.com/ansible-community/antsibull/actions?query=workflow%3A%22๐ท+dumb+PyPI+on+GH+pages%22+branch%3Amain)
-[](https://codecov.io/gh/ansible-community/antsibull)
-[](https://api.reuse.software/info/github.com/ansible-community/antsibull)
-
-Tooling for building various things related to Ansible
+# **Antsibull** โ *Ansible Build Scripts* ๐
+
+### A powerful tool for building various Ansible-related things! ๐ฏ
+
+
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
-Scripts that are here:
+---
-* antsibull-build - Builds Ansible 6+ from component collections ([docs](https://github.com/ansible-community/antsibull/blob/main/docs/build-ansible.rst))
+## ๐ง **Scripts Available**
-Related projects are [antsibull-changelog](https://pypi.org/project/antsibull-changelog/) and [antsibull-docs](https://pypi.org/project/antsibull-docs/), which are in their own repositories ([antsibull-changelog repository](https://github.com/ansible-community/antsibull-changelog/), [antsibull-docs repository](https://github.com/ansible-community/antsibull-docs/)). Currently antsibull-changelog is a dependency of antsibull. Therefore, the scripts contained in it will be available as well when installing antsibull.
+โจ **`antsibull-build`** โ Builds Ansible 6+ from component collections.
+๐ [Documentation](https://github.com/ansible-community/antsibull/blob/main/docs/build-ansible.rst)
+๐ Related projects:
+ - [antsibull-changelog](https://pypi.org/project/antsibull-changelog/)
+ - [antsibull-docs](https://pypi.org/project/antsibull-docs/)
-You can find a list of changes in [the Antsibull changelog](https://github.com/ansible-community/antsibull/blob/main/CHANGELOG.md).
+๐ **Changelog**
+You can find all the changes in the [Antsibull changelog](https://github.com/ansible-community/antsibull/blob/main/CHANGELOG.md).
-antsibull is covered by the [Ansible Code of Conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
-## Licensing
+๐จ Covered by the [Ansible Code of Conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
-This repository abides by the [REUSE specification](https://reuse.software).
-See the copyright headers in each file for the exact license and copyright.
-Summarily:
+---
-- The default license is the GNU Public License v3+
- ([`GPL-3.0-or-later`](LICENSES/GPL-3.0-or-later.txt)).
-- `src/antsibull/_vendor/shutil.py` includes code derived from CPython, licensed
- under the Python 2.0 License ([`Python-2.0.1`](LICENSES/Python-2.0.1.txt)).
+## ๐ก๏ธ **Licensing**
-## Versioning and compatibility
+This repository follows the [REUSE specification](https://reuse.software).
+๐ผ The default license: **GNU Public License v3+** ([Details here](LICENSES/GPL-3.0-or-later.txt)).
+๐ก Code derived from CPython is licensed under Python 2.0 ([Details here](LICENSES/Python-2.0.1.txt)).
-From version 0.1.0 on, antsibull sticks to semantic versioning and aims at providing no backwards compatibility breaking changes **to the command line API (antsibull)** during a major release cycle. We might make exceptions from this in case of security fixes for vulnerabilities that are severe enough.
+---
-We explicitly exclude code compatibility. **antsibull is not supposed to be used as a library.** The only exception are potential dependencies with other antsibull projects (currently, none). If you want to use a certain part of antsibull as a library, please create an issue so we can discuss whether we add a stable interface for **parts** of the Python code. We do not promise that this will actually happen though.
+## ๐ข **Versioning & Compatibility**
-## Development
+Since version **0.1.0**, antsibull follows **semantic versioning** ๐งฎ and ensures no breaking changes to the command line API during a major release cycle.
-Install and run `nox` to run all tests. That's it for simple contributions!
-`nox` will create virtual environments in `.nox` inside the checked out project
-and install the requirements needed to run the tests there.
+โ **Note:** antsibull is not meant to be used as a library.
---
-antsibull depends on the sister antsibull-core, antsibull-changelog,
-antsibull-docs-parser, antsibull-docutils, and antsibull-fileutils projects.
-By default, `nox` will install development versions of these projects from
-Github.
-If you're hacking on antsibull-core, antsibull-changelog, antsibull-docs-parser,
-antsibull-docutils and/or antsibull-fileutils alongside antsibull,
-nox will automatically install the projects from `../antsibull-core`,
-`../antsibull-changelog`, `../antsibull-docs-parser`, `../antsibull-docutils`,
-and `../antsibull-fileutils` when running tests if those paths exist.
-You can change this behavior through the `OTHER_ANTSIBULL_MODE` env var:
-
-- `OTHER_ANTSIBULL_MODE=auto` โ the default behavior described above
-- `OTHER_ANTSIBULL_MODE=local` โ install the projects from `../antsibull-core`,
- `../antsibull-changelog`, `../antsibull-docs-parser`, `../antsibull-docutils`,
- and `../antsibull-fileutils`.
- Fail if those paths don't exist.
-- `OTHER_ANTSIBULL_MODE=git` โ install the projects from the Github main branch
-- `OTHER_ANTSIBULL_MODE=pypi` โ install the latest version from PyPI
+## ๐ป **Development**
+
+### Quick Start
+
+๐ To run tests, install and run `nox`. Thatโs it! ๐
+It will create virtual environments in `.nox` and handle everything for you! ๐ก
---
-To run specific tests:
+## ๐ ๏ธ **Antsibull Development Projects**
+
+Antsibull depends on several projects:
+`antsibull-core`, `antsibull-changelog`, `antsibull-docs-parser`, `antsibull-docutils`, `antsibull-fileutils`.
+
+Use the `OTHER_ANTSIBULL_MODE` environment variable to customize how these dependencies are installed:
+
+1. **auto** โ Default behavior.
+2. **local** โ Install from local paths.
+3. **git** โ Install from the GitHub main branch.
+4. **pypi** โ Install the latest version from PyPI.
-1. `nox -e test` to only run unit tests;
-2. `nox -e lint` to run all linters;
-3. `nox -e formatters` to run `isort` and `black`;
-4. `nox -e codeqa` to run `flake8`, `pylint`, `reuse lint`, and `antsibull-changelog lint`;
-5. `nox -e typing` to run `mypy`.
-6. `nox -e coverage_release` to build a test ansible release.
- This is expensive, so it's not run by default.
-7. `nox -e check_package_files` to run the generate-package-files integration tests.
- This is somewhat expensive and thus not run by default.
-8. `nox -e coverage` to display combined coverage results after running `nox -e
- test coverage_release check_package_files`;
-Run `nox -l` to list all test sessions.
+## ๐งช **Running Specific Tests**
-To create a more complete local development env:
+You can run various tests using `nox` by executing the commands below. Each command corresponds to a specific testing type:
-``` console
+| Command | Description |
+|---------------------------------------------|---------------------------------------------------------------------|
+| `nox -e test` | ๐ **Run Unit Tests**: Execute all unit tests. |
+| `nox -e lint` | ๐งน **Run Linters**: Execute all linters to check code style. |
+| `nox -e formatters` | โจ **Run Formatters**: Execute `isort` and `black` for formatting. |
+| `nox -e codeqa` | ๐ **Run Code Quality Checks**: Execute `flake8`, `pylint`, `reuse lint`, and `antsibull-changelog lint`. |
+| `nox -e typing` | ๐งพ **Run Type Checking**: Execute `mypy` for type validation. |
+| `nox -e coverage_release` | ๐๏ธ **Build Test Ansible Release**: This is expensive, so it's not run by default. |
+| `nox -e check_package_files` | ๐ฆ **Generate Package Files Tests**: This is somewhat expensive and thus not run by default. |
+| `nox -e coverage` | ๐ **Display Combined Coverage**: Shows coverage results after running the specified tests. |
+
+### ๐ Additional Commands
+
+- **List All Test Sessions**: Run `nox -l` to see all available test sessions.
+
+### ๐ **Note**
+Some tests, like `coverage_release` and `check_package_files`, are resource-intensive and are not run by default. Make sure to consider your environment's capacity before executing these commands!
+
+---
+
+## โ๏ธ **Complete Local Development Setup**
+
+Follow these steps to clone and install antsibull along with its dependencies:
+
+```bash
git clone https://github.com/ansible-community/antsibull-changelog.git
git clone https://github.com/ansible-community/antsibull-core.git
git clone https://github.com/ansible-community/antsibull-docs-parser.git
@@ -95,24 +118,64 @@ git clone https://github.com/ansible-community/antsibull-docutils.git
git clone https://github.com/ansible-community/antsibull.git
cd antsibull
python3 -m venv venv
-. ./venv/bin/activate
+source ./venv/bin/activate
pip install -e '.[dev]' -e ../antsibull-changelog -e ../antsibull-core -e ../antsibull-docs-parser -e ../antsibull-docutils
-[...]
nox
```
-## Creating a new release:
-
-1. Run `nox -e bump -- `. This:
- * Bumps the package version in `src/antsibull/__init__.py`.
- * Creates `changelogs/fragments/.yml` with a `release_summary` section.
- * Runs `antsibull-changelog release` and adds the changed files to git.
- * Commits with message `Release .` and runs `git tag -a -m 'antsibull ' `.
- * Runs `hatch build --clean` to build an sdist and wheel in `dist/` and
- clean up any old artifacts in that directory.
-2. Run `git push` to the appropriate remotes.
-3. Once CI passes on GitHub, run `nox -e publish`. This:
- * Runs `hatch publish` to publish the sdist and wheel generated during step 1 to PyPI;
- * Bumps the version to `.post0`;
- * Adds the changed file to git and runs `git commit -m 'Post-release version bump.'`;
-4. Run `git push --follow-tags` to the appropriate remotes and create a GitHub release.
+## ๐ Creating a New Release
+
+Follow these steps to create a new release smoothly:
+
+### 1. ๐ง Bump the Version
+Run the following command to start the release process:
+
+```bash
+nox -e bump --
+```
+
+This will:
+
+ โข ๐ Update the package version in src/antsibull/__init__.py.
+ โข ๐ Generate a new changelog fragment in changelogs/fragments/.yml with a summary section.
+ โข ๐ Run antsibull-changelog release and stage the files for git.
+ โข ๐ฆ Commit the changes with the message Release . and create a tag:
+
+ ```bash
+ git tag -a -m 'antsibull '
+ ```
+
+ โข ๐ ๏ธ Build an sdist and wheel using hatch build --clean, and clean up old artifacts in the dist/ folder.
+
+### 2. ๐ Push Changes
+
+Push the changes and tags to your repository:
+
+```bash
+git push
+```
+
+### 3. ๐๏ธ Publish the Release
+
+Once the CI tests pass on GitHub, publish the release to PyPI with:
+
+```bash
+nox -e publish
+```
+
+This will:
+- ๐ Publish the package to PyPI using hatch publish.
+- ๐ Bump the version to .post0 for post-release.
+- ๐ Commit the version bump with:
+
+ ```bash
+ git commit -m 'Post-release version bump.'
+ ```
+
+### 4. ๐ง Push Final Changes
+
+Finally, push the new tags and changes:
+
+```bash
+git push --follow-tags
+```