feat: add more technical docs

Author: jonathanlo411

book/technical-systems/blog-web.md

@@ -0,0 +1,23 @@
+---
+name: Blog Website
+---
+
+# Team Spiral Racing Blog Website
+The Team Spiral Racing Blog Website serves as a front end to all of the articles stored in MongoDB.
+
+## Code Setup
+The source code is hosted on [GitHub](https://github.com/Team-Spiral-Racing/blog) under the Team Spiral Racing [GitHub org](https://github.com/Team-Spiral-Racing).
+
+## Deployment
+Hosting is done by GitHub pages being deployed off of the `gh-pages` branch. There is a custom build step that uses "Hugo" to compile the Markdown files into a static HTML/CSS website. `CNAME` is directly injected during the build step. 
+
+### Application
+The application looks complicated but is quite simple. Effectively you only need to pay attention to the following directories:
+- `/content/posts`: This is where all of the blogs are posted.
+- `/assets`: Non dynamic image file store.
+- `/config/_default`: How you configure the themes and website.
+
+This website is built via Hugo using the Blowfish theme. Blog files are published via the Team Spiral Racing Website and CMS is managed by the TSR Data Service
+
+## Containerization
+A Docker image is built every single time a release is pushed. Pushing releases will kick off the application and update the changelog.

book/technical-systems/data-service.md

@@ -11,5 +11,10 @@ The source code is hosted on [GitHub](https://github.com/Team-Spiral-Racing/data
 ## Deployment
 Hosting is done by [Vercel](https://vercel.com/). Although CRON jobs are offered, they are extremely limited. Instead, CRON jobs are kicked off by REST API request from the aforementioned [cron-job.org](https://cron-job.org/en/). In cron-job.org, a POST method is sent at 12:15 AM, 6:15 AM, 12:15 PM, 6:15 PM to scan for new events in the past 6 hours. Each REST request contains a Bearer token which the application will cross check with `CRON_SECRET` to ensure that no other person is calling the API. The reason why there is a 15 minute boundry is due to Vercel recieving many requests from cron-job.org in peak hours causing denials.
 
+### Application
+Inside the TSR Data Service, there are the following jobs.
+1. YouTube: Scrapes Team Spiral Racing YouTube for info and later processes them. Currently it records down times.
+2. Blog: Acts as an API to publish via Git objects to GitHub. Checks for diffs between the blogs in MongoDB and syncs them at midnight.
+
 ## Containerization
 A Docker image is built every single time a release is pushed. Pushing releases will kick off the application and update the changelog.

book/technical-systems/introduction.md

@@ -7,4 +7,5 @@ index: 1
 This page contains information about how the technical systems are set up for Team Spiral Racing. This includes things like website, deployments, and DNS.
 
 ## Architecture
-The website has a somewhat micro-service based architecture with CRON jobs pulling information from various sorces. The core of the TSR technical system is the [TSR Website](/technical-systems/tsr-web).
+The website has a somewhat micro-service based architecture with CRON jobs pulling information from various sorces. The core of the TSR technical system is the [TSR Website](/technical-systems/tsr-web).
+![](/technical-systems/TSR-Achitecture.drawio.png)