docs: add basic usage information docs

Author: JacobCoffee

docs/byte/usage/byte.rst

@@ -0,0 +1,18 @@
+==========
+About Byte
+==========
+
+The Discord side of Byte is utilizing the `discord.py <https://discordpy.readthedocs.io/en/latest/>`_. framework.
+
+The structure of Byte is not too complex. There exists a ``bot.py`` file containing the main
+:ref:`Byte` bot class, which includes some on-start utilities like loading cogs and ingesting
+new guilds as they join into the database. The class is called via the :func:`run_bot` function
+to start the bot.
+
+The structure of Byte is not dissimilar to the structure of the server side; it has a ``lib/``
+directory for common backend functionality like utilities, logging, and settings, a ``plugings/``
+directory for the cogs, and a ``views/`` directory for the UI components inside of Discord.
+
+For example, any functionality related to `Astral <https://astral.sh/>`_ is located in the
+``plugins/astral/`` directory, such as ``ruff`` embeds, and it's related views are located in
+``views/astral/``.

docs/byte/usage/index.rst

@@ -1,5 +1,10 @@
+=====
 Usage
 =====
 
 .. toctree::
     :titlesonly:
+    :caption: Byte Usage Documentation
+
+    byte
+    starting

docs/byte/usage/starting.rst

@@ -0,0 +1,5 @@
+=============
+Starting Byte
+=============
+
+.. todo:: This section needs to be written.

docs/web/usage/index.rst

@@ -1,5 +1,9 @@
+=====
 Usage
 =====
 
 .. toctree::
     :titlesonly:
+    :caption: Web Usage Documentation
+
+    server

docs/web/usage/server.rst

@@ -0,0 +1,33 @@
+================
+About the Server
+================
+
+The server side of Byte is utilizing the `Litestar <https://litestar.dev>`_ framework.
+It is an immensely powerful, fast, and easy to use framework that is perfect for Byte.
+
+The server is responsible for handling all of the requests to and from the database,
+as well as serving the frontend to the user; it utilizes the `Jinja2 <https://jinja.palletsprojects.com/en/3.0.x/>`_
+templating engine to do so.
+
+There are a few key components to the server, structured like so:
+
+* ``app.py``: The main entry point for the server where the application factory is defined.
+* ``cli.py``: The command line interface for the server.
+* ``__main__.py``: The entry point for the server when running it via the command line.
+* ``lib/``: A directory containing all of the server's logic, settings, and configuration.
+* ``domain/``: A directory containing all of the server's domain logic, including the database models and routes.
+
+The domain is further broken down into logical components, such as:
+
+* ``db/``: The database models
+
+  .. note:: These once were houses inside the respective domain components, but were moved to a separate directory to
+    make it easier to manage and maintain the database models (but also because circular imports are bad).
+* ``github/``: The GitHub domain logic, including connectivity to GitHub via the
+  `githubkit <https://github.com/yanyongyu/githubkit>`_ library.
+* ``guilds/``: The guilds domain logic, including the guilds routes and any helper functions used to perform CRUD
+  operations on guilds.
+* ``system/``: The system domain logic, mainly for dealing with tasks and healthchecks for the core system.
+* ``web/``: The web domain logic, including the web routes, frontend resources, and templates
+
+This structure allows for a clear separation of concerns and makes it easy to find and maintain the server's logic.

docs/web/usage/starting.rst

@@ -0,0 +1,5 @@
+===============
+Starting Server
+===============
+
+.. todo:: This section needs to be written.

src/byte/bot.py

@@ -23,18 +23,6 @@
 load_dotenv()
 
 
-async def on_member_join(member: Member) -> None:
-    """Handle member join event.
-
-    Args:
-        member: Member object.
-    """
-    await member.send(
-        f"Welcome to {member.guild.name}! Please make sure to read the rules if you haven't already. "
-        f"Feel free to ask any questions you have in the help channel."
-    )
-
-
 class Byte(Bot):
     """Byte Bot Base Class."""