docs: rewrite home page

Author: jahn-junior

docs/index.rst

@@ -12,24 +12,25 @@ Charmcraft
     reference/index
     release-notes/index
 
-Charmcraft is a tool designed to simplify the creation, building, and sharing of a
-:external+juju:ref:`Juju charm <charm>`.
-
-When you initialise a charm with Charmcraft, you automatically get all the crucial
-project files, pre-populated with helpful template content. These files are such that
-they can be packed right away; however, to make them meaningul for the application you
-are charming, you'll want to customise the YAML and
-:external+ops:doc:`ops <index>`-powered Python in these files. For certain types of
-applications (Django, FastAPI, Flask, Go), if you initialise with a suitable
-Charmcraft extension, things are even easier -- just tweak a few values in the
-YAML and you get a fully functioning charm. Either way, once you're pleased with
-what you've got, you can again use Charmcraft to publish your charm
-on `Charmhub`_.
-
-You can create, build, and share a charm any way you want, but with Charmcraft you get
-state-of-the-art results in record time.
-
-If you're a charm author, you *must* use Charmcraft!
+Charmcraft is the official command-line tool for initializing, packaging, and publishing
+:external+juju:ref:`Juju charms <charm>`.
+
+When initializing a project, Charmcraft generates all the necessary files, pre-populated
+with template content, which can be further catered to an application using Charmcraft's
+array of extensions. Packing a charm is similarly streamlined, as Charmcraft will
+automatically fetch project dependencies and compile any modules before producing the
+final charm artifact. When it comes time to publish a charm on `Charmhub`_, Charmcraft
+provides tools for charm authors to register a charm's name, upload its associated
+resources, and release revisions to channels.
+
+Charmcraft simplifies every step of the charming process, enabling charm authors to
+bypass boilerplate steps and focus on the contents of their charms. Additionally,
+Charmcraft's seamless integration with tools such as :external+ops:doc:`Ops <index>` and
+Charmhub provides charm authors with a truly comprehensive toolkit for charm
+development.
+
+For those looking to add your applications to a Juju deployment, Charmcraft will prove
+to be an invaluable tool.
 
 
 In this documentation

docs/reference/files/charmcraft-yaml-file.rst

@@ -362,10 +362,10 @@ and the lib version (in ``"<api version>[.<patch version>]"`` string format).
 **Status:** Optional. Recommended for Kubernetes charms.
 
 **Purpose:** The ``charm-user`` key  allows charm authors to specify that their charm
-hook code does not need to be run as root. This key, in combination with ``uid`` + ``gid``
-fields in ``containers``, allows the charm to be run rootless. If set to ``root``,
-the charm runs as root. If set to ``sudoer`` or ``non-root``, the charm runs as a user
-other than root. If the value is ``sudoer``, the charm will be run as a user
+hook code does not need to be run as root. This key, in combination with ``uid`` +
+``gid`` fields in ``containers``, allows the charm to be run rootless. If set to
+``root``, the charm runs as root. If set to ``sudoer`` or ``non-root``, the charm runs
+as a user other than root. If the value is ``sudoer``, the charm will be run as a user
 with access to sudo to elevate its privileges.
 
 **Structure:** The key consists of a single value. One of ``root``, ``sudoer`` or

docs/reference/files/metadata-yaml-file.rst

@@ -437,10 +437,10 @@ Examples:
 **Status:** Optional. Recommended for Kubernetes charms.
 
 **Purpose:** The ``charm-user`` key  allows charm authors to specify that their charm
-hook code does not need to be run as root. This key, in combination with ``uid`` + ``gid``
-fields in ``containers``, allows the charm to be run rootless. If set to ``root``,
-the charm runs as root. If set to ``sudoer`` or ``non-root``, the charm runs as a user
-other than root. If the value is ``sudoer``, the charm will be run as a user
+hook code does not need to be run as root. This key, in combination with ``uid`` +
+``gid`` fields in ``containers``, allows the charm to be run rootless. If set to
+``root``, the charm runs as root. If set to ``sudoer`` or ``non-root``, the charm runs
+as a user other than root. If the value is ``sudoer``, the charm will be run as a user
 with access to sudo to elevate its privileges.
 
 **Structure:** The key consists of a single value. One of ``root``, ``sudoer`` or