docs: start SQL diagrams and thinking about season implementation

Author: aureateAnatidae

apps/docsite/docs/Internal/concepts.md

@@ -0,0 +1,8 @@
+---
+title: Concepts and Vocabulary
+---
+
+# Disambiguation
+
+## Match/Set
+When we refer to the games played between players, which are reported to Grindcord, we use the term "match" over "set". Despite "set" being more common to refer to a past game, it shadows the term "set", which is a reserved word in programming (the data structure).

apps/docsite/docs/Internal/database.md

@@ -2,7 +2,80 @@
 title: Database Design
 ---
 
-This file outlines the structure of the entities stored by Grindcord, and the rationale in their design.
+This file outlines the structure of the entities stored by Grindcord, and the rationale in their design. An emphasis is placed on database entities in their role as storage, rather than their function.
+
+In an effort to support compatibility with every database management system (DBMS) supported by Knex.js, we avoid the use of arrays and enums.
+
+Matches are reported to the backend. These reports contain the data:
+
+- The Discord server in which the match was played
+- The users who played
+- Match count (3-0)
+- The fighters used by each respective user
+
+##### External Dependencies
+
+A user of Grindcord SHOULD NOT be stored explicitly in our database. A [`GuildMember`](https://discord.com/developers/docs/resources/guild#get-guild-member) is an external dependency provided by Discord. A [`GuildMember`](https://discord.com/developers/docs/resources/guild#get-guild-member)'s `user_id` on the [`user`](https://discord.com/developers/docs/resources/user#user-object) field SHOULD be considered a primary key for our purposes.
+
+A guild SHOULD NOT be stored explicitly in our database. A [`Guild`](https://discord.com/developers/docs/resources/guild#get-guild) is an external dependency provided by Discord. A `Guild`'s `guild_id` SHOULD be considered a primary key for our purposes.
+
+```mermaid
+erDiagram
+    direction LR
+    Guild
+    GuildMember
+```
+
+We split this into three tables.
 
 ```mermaid
-```
+erDiagram
+    direction LR
+    Match {
+        int         match_id    PK
+        int         season_id   PK
+        datetime    created_at
+    }
+    MatchPlayer {
+        int         match_id    FK,PK
+        string      user_id     PK
+        int         win_count
+    }
+    MatchCharacter {
+        int         match_id    FK,PK
+        string      user_id
+        int         fighter_number
+    }
+    Match ||--|{ MatchPlayer: "is played by"
+    MatchPlayer ||..|{ MatchCharacter: "uses"
+```
+
+##### Entity Relation Diagram for Matches, storing the data that would be reported by a user.
+
+The winner of the match can be inferred by selecting the `MatchPlayer` record with the highest `win_count` among records with the same `match_id`.
+
+Note that `guild_id` is not stored by the `Match` table. When a match is reported for a particular `guild_id` (a unique ID assigned by Discord for a particular Discord server), the match is reported for that "guild's" current season (see below).
+
+```mermaid
+erDiagram
+    direction LR
+    Match {
+        int         match_id
+        int         season_id
+        datetime    created_at
+    }
+    Season {
+        int         season_id
+        string      guild_id
+        datetime    start_at
+        datetime    end_at
+    }
+    Match }|--|| Season: "was played during"
+    Guild ||--o{ Season: "has a current or past"
+```
+
+##### Entity Relation Diagram for Seasons.
+
+A guild's "current" season is a `Season` record for which the `guild_id` matches, and the system datetime is between `start_at` and `end_at`.
+
+In addition, a `Season` in which participants will be designated an individual tier. Participants in a `Season` are `GuildMember` who report having participated in a `Match` during a `Season`.

apps/docsite/src/components/HomepageFeatures/index.tsx

@@ -11,32 +11,33 @@ type FeatureItem = {
 
 const FeatureList: FeatureItem[] = [
   {
-    title: 'Easy to Use',
+    title: 'Handle the boring stuff',
     Svg: require('@site/static/img/undraw_docusaurus_mountain.svg').default,
     description: (
       <>
-        Docusaurus was designed from the ground up to be easily installed and
-        used to get your website up and running quickly.
+          Grindcord is designed to assist in all the bureaucracy of running a leaderboard
+          so that you can get right back to the fun part of engaging in competition.
       </>
     ),
   },
   {
-    title: 'Focus on What Matters',
+    title: 'Easy, Simple, and Extensible',
     Svg: require('@site/static/img/undraw_docusaurus_tree.svg').default,
     description: (
       <>
-        Docusaurus lets you focus on your docs, and we&apos;ll do the chores. Go
-        ahead and move your docs into the <code>docs</code> directory.
+          Grindcord is accessible to anyone from competitors, to server admins, to TOs,
+          whether or not they have technical experience, and especially supports those with
+          experience to use Grindcord to its full potential.
       </>
     ),
   },
   {
-    title: 'Powered by React',
+    title: 'Open-source, self-hostable',
     Svg: require('@site/static/img/undraw_docusaurus_react.svg').default,
     description: (
       <>
-        Extend or customize your website layout by reusing React. Docusaurus can
-        be extended while reusing the same header and footer.
+          Grindcord is created by competitors, for competitors. We invite anyone,
+          regardless of experience, to use Grindcord for their own purposes.
       </>
     ),
   },

apps/docsite/src/pages/index.tsx

@@ -21,7 +21,7 @@ function HomepageHeader() {
           <Link
             className="button button--secondary button--lg"
             to="/docs/intro">
-            Docusaurus Tutorial - 5min ⏱️
+                Get started with Grindcord
           </Link>
         </div>
       </div>
@@ -33,8 +33,8 @@ export default function Home(): ReactNode {
   const {siteConfig} = useDocusaurusContext();
   return (
     <Layout
-      title={`Hello from ${siteConfig.title}`}
-      description="Description will go into a meta tag in <head />">
+      title={`Welcome to ${siteConfig.title}`}
+      description="Tools for competitive Smash communities">
       <HomepageHeader />
       <main>
         <HomepageFeatures />