chore: migrate personal reference pages to private notes

Removes templates, music, AI prompts, server setup, and VTubing setup from the public docs site. These pages have been migrated to Naomi's private SilverBullet notes instance where they belong. The server setup doc has been rewritten as a personal runbook rather than staff-facing documentation.
2026-03-02 13:18:01 -08:00
parent b6b3ef01ad
commit 7f311fd7b5
6 changed files with 0 additions and 1607 deletions
@@ -180,14 +180,6 @@ export const navigation = [
        label: "Development Environment",
        link: "/dev/environment",
      },
      {
        label: "Server Setup",
        link: "/dev/servers",
      },
      {
        label: "Naomi's VTubing Setup",
        link: "/dev/vtubing",
      },
      {
        label: "Security Hall of Fame",
        link: "/dev/hall-of-fame",
@@ -857,26 +849,6 @@ export const navigation = [
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
  // #endregion
  // #region Miscellaneous Documents
  {
    label: "Miscellaneous Documents",
    collapsed: true,
    items: [
      {
        label: "Managing Local Music",
        link: "/misc/music",
      },
      {
        label: "Templates",
        link: "/misc/templates",
      },
      {
        label: "AI Prompts",
        link: "/misc/prompts",
      }
    ].sort((a, b) => a.label.localeCompare(b.label)),
  },
  // #endregion
  // #region External Links
  {
    label: "Discord",
@@ -1,428 +0,0 @@
 ---
 title: Server Setup
 ---
 **ESTABLISHING SERVER CONFIGURATION STANDARDS AND SECURITY REQUIREMENTS**
 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
 ### 1.1. Policy Overview
 This Server Setup Documentation (hereinafter referred to as "the Documentation") establishes mandatory standards, procedures, and security requirements for configuring remote servers used to host projects maintained by our organisation. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Security Policy, and all applicable legal protections by reference.
 ### 1.2. Scope and Applicability
 This Documentation applies to all remote servers used to host projects, services, or infrastructure maintained by our organisation. All personnel responsible for server configuration, deployment, or maintenance must comply with the standards set forth in this Documentation.
 **IMPORTANT: Non-compliance with server security and configuration standards set forth in this Documentation may result in security vulnerabilities, service disruptions, or other serious consequences. All server administrators must strictly adhere to these requirements.**
 ### 1.3. Security and Compliance Requirements
 Server configuration must comply with:
 - Our Security Policy and security standards
 - Applicable data protection and privacy regulations
 - Industry best practices for server security
 - All relevant legal and regulatory requirements
 ## 2. PROVISIONING A SERVER
 We use DigitalOcean as our provider. Regardless of your choice, provision a new VPS using the **latest Ubuntu LTS version**. Add your `ssh` key AND Naomi's `ssh` key in the setup process.
 ## 3. SETTING UP USER ACCOUNTS
 You should never run applications on root. SSH into the new VPS to prepare your user.
 ### 3.1. Creating the User Account
 You'll need to set a password for the `root` account first.
 ```bash
 passwd
 ```
 Once you have set a password, ensure that you have provided it to Naomi to store in the vault.
 Create an `NHCarrigan` user for our organisation.
 ```bash
 adduser NHCarrigan
 ```
 Set a **different** password, and provide that to Naomi as well. For all of the user information, use the default blank values.
 Add the new user to the sudoers file.
 ```bash
 usermod -aG sudo NHCarrigan
 ```
 Then sync the SSH keys so we can authenticate as that user.
 ```bash
 rsync --archive --chown=NHCarrigan:NHCarrigan ~/.ssh /home/NHCarrigan
 ```
 While you are there, set the timezone for the server to our business' local timezone.
 ```bash
 sudo timedatectl set-timezone America/Los_Angeles
 ```
 ## 4. PREPARING FOR WEB REQUESTS
 To prepare the server to receive web requests, you'll need to follow a few steps.
 ### 4.1. SSL Certificate Configuration
 :::note
 If the Firewall has been set up, you'll need to temporarily allow port 80 for the certificate to generate.
 :::
 We use LetsEncrypt to provision our SSL certificates. If it is not installed, install it with:
 ```bash
 sudo snap install --classic certbot
 ```
 Then link the snap to our `usr` directory.
 ```bash
 sudo ln -s /snap/bin/certbot /usr/bin/certbot
 ```
 Generate a certificate with:
 ```bash
 sudo certbot certonly --standalone
 ```
 And allow applications to read it:
 ```bash
 sudo chmod -R a+rwx /etc/letsencrypt
 ```
 When you need to renew the certificate:
 ```bash
 sudo certbot renew
 ```
 ### 4.2. NGINX Configuration
 All requests should be routed through NGINX. At no point should an application run directly on ports 80 or 443.
 Install NGINX:
 ```bash
 sudo apt-get install nginx
 ```
 Edit the configuration file:
 ```bash
 sudo emacs /etc/nginx/conf.d/server.conf
 ```
 Use this template to set up a reverse proxy on the standard HTTPS port 443:
 ```nginx
 server {
    listen 443 ssl;
    server_name subdomain.domain.tld;
    ssl_certificate /etc/letsencrypt/live/subdomain.domain.tld/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/subdomain.domain.tld/privkey.pem;
    location / {
        proxy_set_header Host $host;
        proxy_pass https://127.0.0.1:port;
        proxy_redirect off;
    }
 }
 ```
 Validate that the config is correct with:
 ```bash
 sudo nginx -t
 ```
 If so, restart NGINX to apply the changes:
 ```bash
 sudo systemctl restart nginx
 ```
 ## 5. SECURING THE SERVER
 We have a minimum level of security that is required on ALL of our servers. This section should not be treated as the best effort, but as the minimal requirements to comply with our policies.
 ### 5.1. Firewall Configuration
 We use `ufw` as our firewall. First, enable the SSH port.
 ```bash
 sudo ufw allow "OpenSSH"
 ```
 Then, allow the standard HTTPS port and **deny** the standard HTTP port.
 ```bash
 sudo ufw deny http
 sudo ufw allow https
 ```
 Enable the firewall. You may get dropped from the SSH connection.
 ```bash
 sudo ufw enable
 ```
 ### 5.2. Fail2Ban Configuration
 We also use Fail2Ban to block IP addresses which fail to make requests too often.
 Install the tool:
 ```bash
 sudo apt-get install fail2ban
 ```
 Configure the NGINX jail in `/etc/fail2ban/jail.d/nginx-auth.conf`:
 ```ini
 [nginx-auth]
 enabled = true
 filter = nginx-auth
 logpath = /var/log/nginx/access.log
 maxretry = 3
 findtime = 86400
 bantime = 86400
 ```
 Configure the NGINX filter in `/etc/fail2ban/filter.d/nginx-auth.conf`:
 ```ini
 [Definition]
 failregex = ^<HOST> - .* \[.*\] ".*" (4\d{2}) .*$
 ```
 Because we use Cloudflare, you'll need to grab the original IP for all requests. Start by creating a file to store Cloudflare's IPs.
 ```bash
 sudo touch /etc/nginx/cloudflare_ips.conf
 ```
 Then create your script:
 ```bash
 nano ~/update_cf_ips.sh
 ```
 ```bash
 #!/bin/bash
 # Create a temporary file
 temp_file=$(mktemp)
 # Download IPv4 ranges and format each line
 curl -s https://www.cloudflare.com/ips-v4 | while read ip; do
    echo "set_real_ip_from $ip;" >> "$temp_file"
 done
 # Download IPv6 ranges and format each line
 curl -s https://www.cloudflare.com/ips-v6 | while read ip; do
    echo "set_real_ip_from $ip;" >> "$temp_file"
 done
 # Add the real_ip_header directive
 echo "real_ip_header CF-Connecting-IP;" >> "$temp_file"
 # Replace the old file with the new one
 sudo mv "$temp_file" /etc/nginx/cloudflare_ips.conf
 # Test Nginx configuration
 sudo nginx -t
 # If the test is successful, reload Nginx
 if [ $? -eq 0 ]; then
    sudo systemctl reload nginx
    echo "Nginx configuration updated and reloaded successfully."
 else
    echo "Nginx configuration test failed. Please check your configuration."
 fi
 ```
 Make it executable and run it:
 ```bash
 sudo chmod +x update_cf_ips.sh
 sudo ./update_cf_ips.sh
 ```
 If it runs as expected, set it up to run on a CRON.
 ```bash
 sudo crontab -e
 ```
 ```bash
 0 3 * * 1 ~/update_cf_ips.sh
 ```
 Then, update the `/etc/nginx/nginx.conf` to use all of this new logic. This goes at the end of your `http` directive block.
 ```nginx
 # Look at the real IP, not the cloudflare IP.
 include /etc/nginx/cloudflare_ips.conf;
 log_format custom_format '$remote_addr - $remote_user [$time_local] '
                        '"$request" $status $body_bytes_sent '
                        '"$http_referer" "$http_user_agent" '
                        '"$http_x_forwarded_for"';
 access_log /var/log/nginx/access.log custom_format;
 ```
 Confirm the NGINX configuration is correct:
 ```bash
 sudo nginx -t
 ```
 Then restart everything.
 ```bash
 sudo systemctl restart nginx
 sudo systemctl restart fail2ban
 ```
 To view banned IPs:
 ```bash
 sudo fail2ban-client status nginx-auth
 ```
 And to unban them:
 ```bash
 sudo fail2ban-client set nginx-auth unbanip <ip>
 ```
 ## 6. UPLOADING PROJECTS
 To upload a project, you should **not** use `git` to clone the project to the machine. Instead, start by cloning the project to your local environment and navigating to the directory:
 ```bash
 git clone <url>
 cd /path/to/project
 ```
 Then sync the project up to the machine, ignoring any installed packages.
 ```bash
 rsync -av --exclude='node_modules' ./ <server name>:/home/NHCarrigan/<project directory>
 ```
 ## 7. RUNNING PROJECTS
 Now you are ready to start running the project.
 ### 7.1. Node.js Setup
 Most of our projects will run on Node. For a new machine, you'll need to set that up.
 We use `nvm` to manage Node versions. Fetch and run the install script:
 ```bash
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash
 ```
 The script will automatically update the `.bashrc` file to load `nvm` into the PATH. Reload that:
 ```bash
 source ~/.bashrc
 ```
 Install the long-term support Node version.
 ```bash
 nvm install --lts
 ```
 This should automatically set it as the default. When updating, be sure to remove any older versions!
 Finally, install `pnpm` as the package manager.
 ```bash
 npm i -g pnpm
 ```
 ### 7.2. PM2 Process Management
 All of our processes run with PM2 to allow for monitoring and auto-restarts. You'll need to install it.
 ```bash
 pnpm i -g pm2
 ```
 To start a project, use this template:
 ```bash
 pm2 start '<script>' --name '<name>'
 ```
 Then run `pm2 save` to save the application list.
 ## 8. LIMITATION OF LIABILITY AND DISCLAIMERS
 ### 8.1. Reference to Comprehensive Liability Framework
 **IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
 ### 8.2. Server Configuration Disclaimer
 This Documentation establishes mandatory security and configuration standards. However, compliance with these standards does not guarantee:
 - Complete protection against all security threats or vulnerabilities
 - Uninterrupted service availability or performance
 - Compatibility with all applications or use cases
 - Protection against all forms of attack or compromise
 ### 8.3. Security Disclaimer
 While this Documentation establishes security requirements, server administrators are responsible for:
 - Implementing additional security measures appropriate to their specific threat environment
 - Regularly updating and patching all software and dependencies
 - Monitoring server logs and security alerts
 - Responding promptly to security incidents
 - Maintaining compliance with all applicable security regulations and standards
 ### 8.4. Third-Party Services and Tools
 This Documentation references various third-party services, tools, and software packages. Our organisation:
 - Does not guarantee the security, availability, or functionality of third-party services
 - Is not responsible for issues arising from the use of third-party tools or services
 - Recommends that administrators review third-party licenses, terms of service, and security practices
 - Does not provide support for third-party tools beyond what is necessary for project functionality
 ### 8.5. Technical Accuracy Disclaimer
 While we strive to maintain accurate and current information in this Documentation, technical standards, software versions, and security best practices evolve continuously. Server administrators are responsible for:
 - Verifying current software versions and compatibility
 - Adapting configurations to their specific system requirements
 - Ensuring compliance with current security standards and regulations
 - Consulting additional resources for the most current security recommendations
 ## 9. CONCLUSION
 This Server Setup Documentation establishes mandatory standards and procedures for configuring remote servers used to host projects maintained by our organisation. Strict adherence to these requirements is essential for maintaining security, reliability, and compliance with our organisational policies and legal obligations.
 All personnel responsible for server configuration, deployment, or maintenance must familiarise themselves with and comply with the requirements set forth in this Documentation. Questions about server configuration requirements or security standards should be directed to appropriate technical leadership through designated communication channels.
 ---
 *For questions about server configuration requirements or to suggest improvements, please contact technical leadership through the designated channels outlined in our Security Policy.*
@@ -1,54 +0,0 @@
 ---
 title: Naomi's VTubing Setup
 ---
 Naomi uses her VTuber model for all of her client meetings, as well as streaming. Getting the software to work on Linux is a bit of a nightmare, so this page documents how she does so.
 ## 1. OpenSeeFace
 In order to track her webcamera, OpenSeeFace needs to be run independently as a native script.
 ### 1.1. Installation
 This should all be done in your home `~` directory.
 - Begin by cloning the repository:
  - `git clone https://github.com/emilianavt/OpenSeeFace`
  - `cd OpenSeeFace`
 - You will need to prepare Python
  - Install the packages: `yay -Sy python python-virtualenv`
  - Prepare the environment: `virtualenv -p python3 env`
  - Source the environment: `source env/bin/activate`
  - Install the dependencies: `pip3 install onnxruntime opencv-python pillow numpy`
 ### 1.2. Running
 ```
 cd OpenSeeFace
 source env/bin/activate
 python facetracker.py -c 0 -W 1280 -H 720 --discard-after 0 --scan-every 0 --no-3d-adapt 1 --max-feature-updates 900
 ```
 ## 2. VSeeFace
 VSeeFace does not run natively, and will need to run with Wine.
 ### 2.1. Installation
 [Download and run the installer](https://www.vseeface.icu/#download). When selecting a directory, put it in `~/VSeeFace`.
 ### 2.2. Running
 ```bash
 wine ~/VSeeFace/VSeeFace.exe --background-color "#00FF00"
 ```
 The `--background-color` flag creates a green screen background to be chroma-keyed out by OBS.
 ## 3. OBS
 OBS allows for virtual camera, as well as for streaming.
 ### 3.1. Installation
 The `obs-studio-git` AUR package is Naomi's current installation.
@@ -1,94 +0,0 @@
 ---
 title: Managing Local Music
 ---
 **DOCUMENTING LOCAL MUSIC LIBRARY MANAGEMENT PROCEDURES**
 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
 ### 1.1. Policy Overview
 This Music Management Documentation (hereinafter referred to as "the Documentation") provides technical procedures and instructions for managing local music libraries on Linux systems. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
 ### 1.2. Purpose and Scope
 This Documentation describes technical procedures for managing local music libraries. This information is provided for informational purposes and personal use only.
 **IMPORTANT: Users are solely responsible for ensuring that all music acquisition, storage, and management activities comply with applicable copyright laws, licensing agreements, and legal requirements. Our organisation does not condone or support any illegal activities, including copyright infringement or piracy.**
 ### 1.3. Legal Compliance Disclaimer
 All users must ensure that their music acquisition and management activities comply with:
 - Applicable copyright laws and regulations
 - Terms of service of music platforms and services
 - Licensing agreements for music content
 - All relevant intellectual property laws
 Our organisation assumes no responsibility for any illegal activities conducted using information from this Documentation.
 ## 2. ACQUIRING MUSIC
 You are welcome to use any method you wish to *LEGALLY* acquire music. We would never encourage the criminal act of piracy. But maybe you're an artist and you want to archive or back up your own music - in that case, here you go:
 ```bash
 yt-dlp -x --audio-format mp3 <url> --cookies-from-browser firefox
 ```
 Omit the `--cookies-from-browser firefox` if you do not need authentication (auth is required for age-restricted content, for example).
 ## 3. EDITING METADATA
 The specific meta tags you may need to set will vary depending on the music software you use. We have confirmed that `TIT2` is read as the title and `TPE1` is read as the artist when using Amberol on Linux and Musicolet on Android. Using `-t` and `-a` might work.
 ```bash
 id3v2 "/path/to/song" --TIT2 "Song Title" --TPE1 "Song Artist" 
 ```
 ## 4. ADDING COVER IMAGES
 Download the image (we have confirmed JPEGs work) that you want to apply to the song, then run:
 ```bash
 eyeD3 --add-image="/path/to/img":FRONT_COVER "/path/to/mp3"
 ```
 ## 5. COPYING TO ANDROID DEVICES
 You'll need to replace your paths and your device ID to match your local setup, but:
 ```bash
 adb -s 192.168.12.105:5555 push music/* /storage/self/primary/Music
 ```
 ## 6. LIMITATION OF LIABILITY AND DISCLAIMERS
 ### 6.1. Reference to Comprehensive Liability Framework
 **IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
 ### 6.2. Legal Compliance Disclaimer
 This Documentation provides technical procedures only. Our organisation:
 - Does not provide legal advice regarding music acquisition or copyright compliance
 - Does not endorse or support any illegal activities, including copyright infringement
 - Assumes no responsibility for users' compliance with copyright laws or licensing agreements
 - Recommends that users consult qualified legal counsel for questions about copyright compliance
 ### 6.3. Technical Accuracy Disclaimer
 While we strive to maintain accurate and current information in this Documentation, software tools, commands, and procedures may change over time. Users are responsible for:
 - Verifying current software versions and compatibility
 - Adapting procedures to their specific system configurations
 - Ensuring their technical setup meets the requirements for these procedures
 - Consulting additional resources for the most current technical information
 ## 7. CONCLUSION
 This Music Management Documentation provides technical procedures for managing local music libraries on Linux systems. All users must ensure that their use of these procedures complies with applicable copyright laws, licensing agreements, and legal requirements.
 ---
 *For questions about music management procedures or legal compliance, please consult qualified legal counsel.*
@@ -1,151 +0,0 @@
 ---
 title: AI Prompts
 ---
 **DOCUMENTING STANDARD AI PROMPTS AND WORKFLOW TEMPLATES**
 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
 ### 1.1. Policy Overview
 This AI Prompts Documentation (hereinafter referred to as "the Documentation") provides standard prompts, templates, and workflow instructions for using artificial intelligence tools in our organisational workflows. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
 ### 1.2. Purpose and Scope
 This Documentation serves as a reference for standardised AI prompts used in various organisational contexts. These prompts are provided for convenience and consistency but may require customisation for specific use cases.
 **IMPORTANT: These prompts are provided as starting points and may require modification to meet specific requirements. Users are responsible for ensuring that any use of AI tools complies with applicable laws, regulations, and organisational policies.**
 ### 1.3. AI Tool Usage Disclaimer
 Our organisation does not guarantee the accuracy, reliability, or appropriateness of outputs generated using these prompts. Users are responsible for:
 - Reviewing and validating all AI-generated content
 - Ensuring compliance with applicable laws and regulations
 - Maintaining appropriate oversight of AI tool usage
 - Protecting sensitive or confidential information when using AI tools
 ## 2. AI PROMPTS
 ### 2.1. Documentation Generation Prompt
 Open Claude Code in your project directory, then provide this prompt:
 ```md
 Please go through the entire `src` directory and use the codebase to generate documentation for me, given the following template:
 ---
 title: <app name>
 ---
 <app name> (hereinafter the "Application") is <description>
 ## 1. User Documentation
 This section is for those interacting with a live instance of the Application.
 ## 2. Technical Documentation
 This section is for those interested in running their own instance of the Application.
 ## 3. Legal Documentation
 This section is for expansions to our legal policies specific to the Application.
 ## 4. Contributing Documentation
 This section is for documentation related to contributing to the Application's codebase.
 ```
 ### 2.2. Comprehension Question Generation Prompt
 We use this for some of our client work, but this is great for creating questions to quiz yourself on any document you've read.
 ````md
 You must create three comprehension check questions for the lecture script the user provides. Do not include any other information. Format the response as a code block so the user can easily copy the syntax.
 Here is the format:
 ```
 ### Question 1:
 Which of the following is a key characteristic of relational databases?
 **A.** Flexible schema
 **B.** Document-based structure
 **C.** Key-value pairs
 **D.** Structured data in tables
 Hint: Think about how data is organised in relational databases.
 Answer: **D.** Structured data in tables
 ### Question 2:
 Which of the following is a key characteristic of relational databases?
 **A.** Flexible schema
 **B.** Document-based structure
 **C.** Key-value pairs
 **D.** Structured data in tables
 Hint: Think about how data is organised in relational databases.
 Answer: **D.** Structured data in tables
 ### Question 3:
 Which of the following is a key characteristic of relational databases?
 **A.** Flexible schema
 **B.** Document-based structure
 **C.** Key-value pairs
 **D.** Structured data in tables
 Hint: Think about how data is organised in relational databases.
 Answer: **D.** Structured data in tables
 ```
 ````
 ## 3. LIMITATION OF LIABILITY AND DISCLAIMERS
 ### 3.1. Reference to Comprehensive Liability Framework
 **IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
 ### 3.2. AI Tool Usage Disclaimer
 These prompts are provided for informational purposes only. Our organisation:
 - Does not guarantee the accuracy, reliability, or appropriateness of outputs generated using these prompts
 - Does not warrant that these prompts will produce desired results in all contexts
 - Assumes no responsibility for outcomes resulting from the use of these prompts with AI tools
 - Recommends that users review and validate all AI-generated content
 ### 3.3. User Responsibilities
 Users are responsible for:
 - Reviewing and validating all AI-generated content before use
 - Ensuring compliance with applicable laws, regulations, and organisational policies
 - Protecting sensitive or confidential information when using AI tools
 - Maintaining appropriate oversight and quality control of AI tool usage
 - Adapting prompts to meet specific requirements and contexts
 ## 4. CONCLUSION
 This AI Prompts Documentation provides standardised prompts and workflow templates for using artificial intelligence tools in our organisational workflows. All users are responsible for ensuring that their use of these prompts complies with applicable laws, regulations, and organisational policies, and for maintaining appropriate oversight of AI tool usage.
 ---
 *For questions about AI prompt usage or to suggest improvements, please contact appropriate organisational leadership through designated communication channels.*
@@ -1,852 +0,0 @@
 ---
 title: Templates
 ---
 **PROVIDING STANDARD TEMPLATES AND DOCUMENTATION FORMS**
 ## 1. INTRODUCTION AND LEGAL FRAMEWORK
 ### 1.1. Policy Overview
 This Templates Documentation (hereinafter referred to as "the Documentation") provides standard templates, forms, and documentation formats used throughout our organisation. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
 ### 1.2. Purpose and Scope
 This Documentation serves as a reference for standardised templates used in various organisational contexts. These templates are provided for convenience and consistency but may require customisation for specific use cases.
 **IMPORTANT: These templates are provided as starting points and may require modification to meet specific legal, regulatory, or contextual requirements. Users are responsible for ensuring that any use of these templates complies with applicable laws and regulations.**
 ### 1.3. Disclaimer
 Our organisation does not provide legal advice. These templates are provided for informational purposes only. Users should consult with qualified legal counsel when using these templates for legal matters or when compliance with specific regulations is required.
 ## 2. TEMPLATES
 ### 2.1. Legal Templates
 #### 2.1.1. DMCA Takedown Template
 ```md
 To whom it may concern:
 We are writing to notify you of the copyright infringement and unlawful use of our copyrighted material that appear on the service for which you are the designated agent.
 The infringing material, which we contend belong to us, includes our original visual assets.
 The infringing material appears at the following location(s):
 <url>
 The original material is available at the following location(s):
 <url>
 This letter is the official notification under Section 512(c) of the Digital Millennium Copyright Act of 1998 ("DMCA") and we request the immediate removal of the aforementioned infringing materials from your servers.
 We also request that you immediately notify the infringer of this notice and inform them to cease any further posting of the infringing material to your server in the future.
 We are providing this notice in good faith and with the reasonable belief that we are the copyright holder of the material, and that the use of the described material in the manner complained is not authorised by us, our agents, or the law.
 We swear, under penalty of perjury, that the information in this notification is accurate and that we are the owner of the copyrighted material involved.
 If you have any questions, please feel free to reach out to us.
 ```
 ### 2.2. LinkedIn Templates
 #### 2.2.1. LinkedIn Cold Outreach Response Template
 ```md
 I would be more than happy to chat! You can schedule time directly on my calendar:
 https://zcal.co/nhcarrigan/meet
 ```
 #### 2.2.2. LinkedIn Post-Event Recommendation Template
 ```md
 I had the absolute pleasure of working with [Participant's Name] during our [event name], where [they] consistently impressed me with [their] dedication, technical growth, and collaborative spirit.
 From the start, [Participant's Name] dove into the challenge with enthusiasm, applying [their] skills in [tech stack] to build real, impactful solutions. Whether working independently or as part of a team, [they] brought thoughtful ideas, clear communication, and a passion for learning that elevated everyone around [them].
 The value of [Participant's Name]'s contributions are immeasurable. Throughout the event, they [explain loads of goals here].
 By the end of the [event name], [Participant's Name] had delivered an outstanding project: [project name or brief description]. More than the final product, what stood out was [their] journey—embracing feedback, overcoming obstacles, and supporting others along the way.
 I wholeheartedly recommend [Participant's Name] for any opportunity in tech. [They] bring not just technical ability, but the kind of energy and curiosity that makes any team stronger.
 ```
 #### 2.2.3. LinkedIn Mentorship Recommendation Template
 ```md
 I had the privilege of mentoring [Mentee's Name] through my 1:1 mentorship programme, and from our very first session, it was clear that [they] approached learning with curiosity, determination, and an eagerness to grow.
 Over the course of the programme, [Mentee's Name] set clear goals and worked diligently towards them—building both technical skills in [specific tech stack, tools, or concepts] and the professional confidence to apply those skills in real-world scenarios. [They] embraced feedback, sought out challenges, and consistently demonstrated the resilience needed to push past obstacles.
 What impressed me most was [their] commitment to personal and professional growth—not just in terms of technical ability, but also in communication, collaboration, and problem-solving. By the end of the mentorship, [Mentee's Name] had successfully delivered [describe final project or achievement], showing not only technical proficiency but also the ability to think critically and adapt to new situations.
 I am confident that [Mentee's Name] will continue to excel in their career. They bring the kind of focus, curiosity, and dedication that make them a valuable asset to any team, and I am proud to have played a part in their journey.
 ```
 ### 2.3. Form Response Email Templates
 #### 2.3.1. Appeals Form - Approval Email Template
 Subject Line: `Appeal Decision - [Sanction Type] Appeal Upheld`
 ```md
 Dear [Appellant's Name],
 Thank you for submitting your appeal regarding the disciplinary sanction imposed on [date of original sanction]. We acknowledge receipt of your appeal and have conducted a thorough review in accordance with our Community Disciplinary Appeals Policy.
 After careful consideration by the Appeals Panel, which included examination of all evidence and documentation, review of the original decision and its rationale, and assessment of your submissions and arguments, we have determined that your appeal has merit and meets the grounds for appeal as established in our policy.
 **Decision**: Your appeal has been upheld. The original disciplinary sanction has been [overturned/modified/reduced] as follows: [Insert specific details about the new decision].
 **Reasoning**: [Insert detailed reasoning here, addressing the specific grounds raised in the appeal and explaining why the appeal was successful. This should reference procedural compliance, proportionality of the sanction, factual accuracy, evidence considered, and correct application of community policies.]
 As outlined in Section 8.1 of our Community Disciplinary Appeals Policy, decisions of the Appeals Panel are final and binding. The decision outlined above is effective immediately.
 We appreciate your engagement with our appeals process and your respect for our community standards. We look forward to your continued positive participation in our community.
 Regards,
 ```
 #### 2.3.2. Appeals Form - Rejection Email Template
 Subject Line: `Appeal Decision - [Sanction Type] Appeal Dismissed`
 ```md
 Dear [Appellant's Name],
 Thank you for submitting your appeal regarding the disciplinary sanction imposed on [date of original sanction]. We acknowledge receipt of your appeal and have conducted a thorough review in accordance with our Community Disciplinary Appeals Policy.
 After careful consideration by the Appeals Panel, which included examination of all evidence and documentation, review of the original decision and its rationale, and assessment of your submissions and arguments, we have determined that your appeal does not meet the grounds for appeal as established in our policy.
 **Decision**: Your appeal has been dismissed. The original disciplinary sanction remains in full effect.
 **Reasoning**: [Insert detailed reasoning here, addressing the specific grounds raised in the appeal and explaining why the original decision was appropriate. This should reference procedural compliance, proportionality of the sanction, factual accuracy, evidence considered, and correct application of community policies.]
 As outlined in Section 8.1 of our Community Disciplinary Appeals Policy, decisions of the Appeals Panel are final and binding. No further appeals or reviews are available through our internal processes.
 We understand that this decision may be disappointing. Our appeals process is designed to ensure fairness and transparency, and we have given your submission careful consideration. The original sanction was imposed in accordance with our community standards and policies, which are designed to maintain a safe and welcoming environment for all members.
 If you have any questions about this decision, please note that our Appeals Panel's determination is final. We appreciate your understanding and respect for our community standards and processes.
 Regards,
 ```
 #### 2.3.3. Commissions Form - Approval Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your commission request! We are excited to work with you on [brief description of commission].
 We have reviewed your request and are pleased to accept it. We will begin working on your commission and will keep you updated on our progress.
 **Next Steps:**
 - [Insert specific next steps, timeline, or requirements here]
 - You will receive updates via [preferred contact method]
 - Expected completion date: [date if applicable]
 If you have any questions or need to make changes to your request, please don't hesitate to reach out to us.
 We look forward to creating something amazing for you!
 Best regards,
 ```
 #### 2.3.4. Commissions Form - Rejection Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your interest in commissioning work from us. We appreciate you taking the time to submit your request.
 After careful review, we have decided not to proceed with your commission request at this time. This decision may be based on factors such as current workload, project scope, timeline constraints, or alignment with our services.
 Please note that due to the volume of requests we receive, we are unable to provide detailed feedback on every declined request.
 We encourage you to stay engaged with our community and projects. If your needs change or you have a different project in mind, we would welcome a new request in the future.
 If you have any questions, please reach out in our Discord community: https://chat.nhcarrigan.com
 Best regards,
 ```
 #### 2.3.5. Community Recognition Form - Approval Email Template
 ```md
 Hello [Nominator's Name],
 Thank you for taking the time to nominate [Nominee's Name] for community recognition! We truly appreciate you highlighting the positive contributions of community members.
 We are pleased to inform you that your nomination has been accepted and will be considered in our next recognition cycle. The recognition process involves review by our leadership team, and selected nominees will be celebrated through our community recognition programmes.
 **What Happens Next:**
 - Your nomination will be reviewed by our recognition committee
 - Selected nominees will be notified and celebrated publicly
 - Recognition may include awards, spotlights, or other forms of appreciation
 - All nominations help us build a more appreciative and inclusive community
 Thank you for helping us celebrate the amazing contributions of our community members. Your nomination makes a difference!
 If you have any questions, please reach out in our Discord community: https://chat.nhcarrigan.com
 Warm regards,
 ```
 #### 2.3.6. Community Recognition Form - Rejection Email Template
 ```md
 Hello [Nominator's Name],
 Thank you for taking the time to submit a nomination for community recognition. We truly appreciate your effort to highlight positive contributions in our community.
 After careful review, we have decided not to proceed with this nomination at this time. This decision may be based on factors such as eligibility criteria, timing, or alignment with our recognition programmes.
 Please note that due to the volume of nominations we receive, we are unable to provide detailed feedback on every declined nomination.
 We encourage you to continue recognising positive contributions in our community. There are many ways to show appreciation, including direct recognition, peer appreciation, and future nominations.
 If you have any questions about our recognition programmes, please reach out in our Discord community: https://chat.nhcarrigan.com
 Thank you again for your engagement with our community.
 Warm regards,
 ```
 #### 2.3.7. Contact Form - Approval Email Template
 ```md
 Hello [Contact's Name],
 Thank you for reaching out to us through our contact form. We have received your message regarding [brief topic summary].
 We appreciate you taking the time to contact us and are pleased to confirm that we have received your inquiry. [Insert specific response or next steps here, such as:]
 - We will review your request and respond within [timeframe]
 - A team member will be in touch shortly
 - We have scheduled a follow-up [meeting/call/response] for [date/time]
 If you have any urgent questions or need immediate assistance, please don't hesitate to reach out in our Discord community: https://chat.nhcarrigan.com
 We look forward to connecting with you!
 Best regards,
 ```
 #### 2.3.8. Contact Form - Rejection Email Template
 ```md
 Hello [Contact's Name],
 Thank you for reaching out to us through our contact form. We have received your message regarding [brief topic summary].
 After reviewing your inquiry, we are unable to assist with your request at this time. This may be due to factors such as scope of services, current capacity, or alignment with our mission and values.
 Please note that due to the volume of inquiries we receive, we are unable to provide detailed feedback on every declined request.
 If you have questions about our services or policies, we encourage you to review our documentation at https://docs.nhcarrigan.com or join our Discord community: https://chat.nhcarrigan.com
 Thank you for your understanding.
 Best regards,
 ```
 #### 2.3.9. Development Review Requests Form - Approval Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your development review request! We have reviewed your submission and are pleased to accept your request for review of [project/repository name or description].
 **Review Details:**
 - Review Type: [Code Review/Project Review/Architecture Review/etc.]
 - Materials to be Reviewed: [list of materials]
 - Expected Timeline: [timeline for review completion]
 **Next Steps:**
 - Our team will begin reviewing your materials
 - You will receive detailed feedback via [communication method]
 - We will provide constructive suggestions for improvement
 Please note that development reviews are provided as free services to active community members, and feedback is provided in good faith based on our expertise and best practices.
 If you have any questions or need to provide additional materials, please don't hesitate to reach out.
 We look forward to reviewing your work!
 Best regards,
 ```
 #### 2.3.10. Development Review Requests Form - Rejection Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your interest in receiving a development review. We appreciate you taking the time to submit your request.
 After careful review, we have decided not to proceed with your development review request at this time. This decision may be based on factors such as:
 - Current review capacity and workload
 - Alignment with our review services and expertise
 - Community membership and engagement requirements
 - Project scope or complexity
 Please note that development reviews are provided as free services exclusively to active members of our community. If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant.
 If you have questions about our development review services or would like to resubmit in the future, please reach out in our Discord community: https://chat.nhcarrigan.com
 Thank you for your understanding.
 Best regards,
 ```
 #### 2.3.11. Events Form - Approval Email Template
 ```md
 Hello [Event Organiser's Name],
 Thank you for your event request! We are excited about your proposed event: [Event Name].
 We have reviewed your submission and are pleased to approve your event request. We look forward to supporting and promoting this event within our community.
 **Event Details:**
 - Event Name: [Event Name]
 - Proposed Date: [Date]
 - Event Type: [Type of event]
 **Next Steps:**
 - [Insert specific next steps, such as scheduling, promotion, or coordination details]
 - We will work with you to finalise event details
 - Event promotion will begin [timeline]
 If you have any questions or need to make changes to your event details, please don't hesitate to reach out to us.
 Thank you for contributing to our community through this event!
 Best regards,
 ```
 #### 2.3.12. Events Form - Rejection Email Template
 ```md
 Hello [Event Organiser's Name],
 Thank you for your interest in organising an event with our community. We appreciate you taking the time to submit your event request: [Event Name].
 After careful review, we have decided not to proceed with your event request at this time. This decision may be based on factors such as:
 - Current event calendar and capacity
 - Alignment with our community values and mission
 - Resource availability and support requirements
 - Event scope or logistics
 Please note that due to the volume of event requests we receive, we are unable to provide detailed feedback on every declined request.
 We encourage you to stay engaged with our community and consider submitting future event proposals. If you have questions about our event policies or would like to discuss alternative event formats, please reach out in our Discord community: https://chat.nhcarrigan.com
 Thank you for your understanding and continued engagement with our community.
 Best regards,
 ```
 #### 2.3.13. Mock Interview Requests Form - Approval Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your mock interview request! We have reviewed your submission and are pleased to accept your request for a [technical/behavioural/combined] mock interview.
 **Interview Details:**
 - Interview Type: [Type]
 - Target Role: [Role if provided]
 - Interview Format: [Format]
 **Next Steps:**
 - We will coordinate with you to schedule your mock interview session
 - Mock interviews are typically conducted via [video call/voice call]
 - Sessions typically last between 30-60 minutes
 - You will receive preparation materials and session details via [communication method]
 Please note that mock interviews are provided as free services exclusively to active members of our community. We look forward to helping you prepare for your upcoming interview!
 If you have any questions or need to reschedule, please don't hesitate to reach out to us.
 Best regards,
 ```
 #### 2.3.14. Mock Interview Requests Form - Rejection Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your interest in receiving a mock interview. We appreciate you taking the time to submit your request.
 After careful review, we have decided not to proceed with your mock interview request at this time. This decision may be based on factors such as:
 - Current interview capacity and availability
 - Community membership and engagement requirements
 - Interview type or scope alignment with our services
 - Scheduling constraints
 **IMPORTANT**: Mock interviews are provided as free services EXCLUSIVELY to active members of our community. These services are NOT available to the general public. To be eligible, you MUST be an active, engaged member of our community with demonstrated participation and engagement.
 If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant. Once you have established active community membership through regular participation and engagement, you will be eligible to request mock interview services.
 If you have questions about our mock interview services or community membership, please reach out in our Discord community: https://chat.nhcarrigan.com
 Thank you for your understanding.
 Best regards,
 ```
 #### 2.3.15. Portfolio Review Requests Form - Approval Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your portfolio review request! We have reviewed your submission and are pleased to accept your request for review of your [resume/LinkedIn profile/GitHub profile/portfolio website].
 **Review Details:**
 - Review Type: [Resume/LinkedIn/GitHub/Portfolio Review]
 - Materials to be Reviewed: [list of materials or links]
 **Next Steps:**
 - Our team will begin reviewing your materials
 - You will receive detailed feedback via [communication method]
 - We will provide constructive suggestions for improvement based on industry best practices
 Please note that portfolio reviews are provided as free services to active community members, and feedback is provided in good faith based on our expertise and professional standards.
 If you have any questions or need to provide additional materials, please don't hesitate to reach out.
 We look forward to reviewing your materials and helping you improve your professional presentation!
 Best regards,
 ```
 #### 2.3.16. Portfolio Review Requests Form - Rejection Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your interest in receiving a portfolio review. We appreciate you taking the time to submit your request.
 After careful review, we have decided not to proceed with your portfolio review request at this time. This decision may be based on factors such as:
 - Current review capacity and workload
 - Community membership and engagement requirements
 - Material accessibility or completeness
 - Review type alignment with our services
 **IMPORTANT**: Portfolio reviews are provided as free services EXCLUSIVELY to active members of our community. These services are NOT available to the general public. To be eligible, you MUST be an active, engaged member of our community with demonstrated participation and engagement.
 If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant. Once you have established active community membership through regular participation and engagement, you will be eligible to request portfolio review services.
 If you have questions about our portfolio review services or community membership, please reach out in our Discord community: https://chat.nhcarrigan.com
 Thank you for your understanding.
 Best regards,
 ```
 #### 2.3.17. Recommendations Form - Approval Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your recommendation request! We have reviewed your submission and are pleased to accept your request for a recommendation.
 **Recommendation Details:**
 - Recommendation Type: [LinkedIn Recommendation/General Recommendation/etc.]
 - Context: [Brief context if provided]
 **Next Steps:**
 - We will prepare your recommendation based on our relationship and your contributions
 - Recommendations are typically provided via [LinkedIn/email/etc.]
 - You will receive a copy of the recommendation once it is completed
 - Expected completion: [timeline]
 Please note that recommendations are provided as free services in good faith, based on our relationship and knowledge of your work. We provide honest, accurate recommendations based on our direct experience with you.
 If you have any questions or need to provide additional context, please don't hesitate to reach out.
 We are happy to support you in your professional journey!
 Best regards,
 ```
 #### 2.3.18. Recommendations Form - Rejection Email Template
 ```md
 Hello [Requester's Name],
 Thank you for your interest in receiving a recommendation. We appreciate you taking the time to submit your request.
 After careful review, we have decided not to proceed with your recommendation request at this time. This decision may be based on factors such as:
 - Insufficient direct working relationship or interaction
 - Lack of sufficient context or experience to provide an accurate recommendation
 - Timeline constraints or capacity limitations
 - Alignment with our recommendation policy and standards
 Please note that we can only provide recommendations when we have sufficient direct experience and relationship with the requester to provide an honest, accurate, and meaningful recommendation.
 If you believe there has been an error or would like to discuss your request further, please reach out in our Discord community: https://chat.nhcarrigan.com
 Thank you for your understanding.
 Best regards,
 ```
 #### 2.3.19. Staff Applications Form - Approval Email Template
 ```md
 Dear [Applicant's Name],
 Thank you so much for taking the time to apply for a volunteer role with NHCarrigan. We truly appreciate your interest in contributing your time and energy to our community.
 After carefully reviewing your application, we are excited to inform you that we would like to move forward with your candidacy! We were impressed by [specific aspects of their application] and believe you would be a valuable addition to our team.
 **Next Steps:**
 - You will receive a separate email with your contract and onboarding materials
 - Please review the contract carefully and reach out with any questions or concerns
 - You can reach out to us on Discord (https://chat.nhcarrigan.com) or reply to this email if you have any questions or concerns
 We are thrilled about the possibility of working with you and look forward to welcoming you to our team. Thank you again for your interest and enthusiasm!
 Warm regards,
 ```
 #### 2.3.20. Staff Applications Form - Onboarding Email Template
 ```md
 Dear [New Staff Member's Name],
 Welcome to the NHCarrigan team! We are thrilled to have you join us and are excited to begin working together.
 **Getting Started:**
 1. **Join Our Discord Server:**
   - Please join our Discord community at: https://chat.nhcarrigan.com
   - This is where most of our team communication and collaboration happens
 2. **Access Credentials:**
   - **Email:**
     - Address: 
     - Password:
     - Can access email via web at https://mail.nhcarrigan.com/mail or through any email client/app. A reminder that this is only for work-related use. Please do not spam people and get our mail server blocked (I do have logs).
   - **Gitea:** https://git.nhcarrigan.com
     - Username:
     - Password: 
 3. **Complete Your Training:**
   - Please complete the policy assessment form for training: https://forms.nhcarrigan.com/o/docs/forms/nxaJyKBuKH9nrt3m5VC98w/4
   - This is an important step to ensure you are familiar with our policies and procedures
 **Next Steps:**
 - Our team will be in touch shortly to discuss your role-specific responsibilities
 - Feel free to explore our documentation at https://docs.nhcarrigan.com
 If you have any questions or need assistance getting set up, please don't hesitate to reach out to us on Discord or reply to this email.
 We are excited to have you on board and look forward to working with you!
 Warm regards,
 ```
 #### 2.3.21. Staff Applications Form - Rejection Email Template
 ```md
 Dear [Applicant's Name],
 Thank you so much for taking the time to apply for a volunteer role with NHCarrigan. We truly appreciate your interest in contributing your time and energy to our community.
 After carefully reviewing your application, we've decided not to move forward with your candidacy for this volunteer position at this time. Please don't take this as a reflection of your value or potential—our selection process is highly competitive, and we often have to make very difficult decisions.
 Please note that due to the large volume of applications we receive, we are unable to provide personalised feedback. Here are some common application issues we see:
 1. Low-effort Application: Please ensure you are taking the time to provide detailed, well-thought responses. The more effort you put in, the more likely we will be able to accept your application.
 2. Invalid Discord ID: Applications require you to provide your unique Discord ID - this is a 16 to 19 digit number that uniquely identifies your Discord account. If this is incorrect, we are unable to accept an application. If you need help finding yours, please refer to https://dis.gd/findid
 3. Concerning Responses: If your responses to any of the application questions raise red flags, we decline your application. Remember that you want to paint yourself in the best light here.
 We still encourage you to stay engaged with our community spaces, events, and projects. There are always opportunities to connect, learn, and grow together, and we would love to see you continue to participate.
 We encourage you to take the time to consider these common points of failure, and would welcome a resubmission from you in the future.
 Thank you again for your interest and enthusiasm. We wish you the very best in all your endeavors and hope our paths cross again in the future.
 Warm regards,
 ```
 #### 2.3.22. Testimonials Form - Approval Email Template
 ```md
 Hello [Contributor's Name],
 Thank you for sharing your testimonial with us! We have reviewed your submission and are pleased to accept it for publication.
 **Testimonial Details:**
 - Your testimonial will be reviewed and may be featured on our website, social media, or other promotional materials
 - We may edit your testimonial for length, clarity, or formatting whilst preserving your message and intent
 - You will be credited as [name/handle as provided]
 **Next Steps:**
 - Your testimonial will be added to our review queue
 - We will notify you when it is published (if applicable)
 - Thank you for helping others learn about our community and services!
 Your words help us build trust and connect with others who might benefit from our community. We truly appreciate you taking the time to share your experience.
 If you have any questions or would like to make changes to your testimonial, please don't hesitate to reach out.
 Best regards,
 ```
 #### 2.3.23. Testimonials Form - Rejection Email Template
 ```md
 Hello [Contributor's Name],
 Thank you for taking the time to submit a testimonial. We appreciate your interest in sharing your experience with our community.
 After careful review, we have decided not to publish your testimonial at this time. This decision may be based on factors such as:
 - Content alignment with our community values and standards
 - Formatting or clarity requirements
 - Current testimonial collection needs
 - Verification or authenticity concerns
 Please note that due to the volume of testimonials we receive, we are unable to provide detailed feedback on every declined submission.
 We encourage you to stay engaged with our community and consider submitting a testimonial in the future if your experience changes or if you have additional feedback to share.
 If you have questions about our testimonial process, please reach out in our Discord community: https://chat.nhcarrigan.com
 Thank you for your understanding and continued engagement with our community.
 Best regards,
 ```
 ### 2.4. Form Components
 #### 2.4.1. Form Consent for Email Communications
 Description:
 ```
 At NHCarrigan, we are fully committed to respecting and protecting your privacy. We strictly adhere to a policy of non-disclosure regarding your personal data; we do not sell, trade, or transfer your information to outside parties. The contact details you provide will be used exclusively for the purpose of responding to your inquiry or addressing the subject of this form. For a complete overview of our data practices, please review our [Privacy Policy](https://docs.nhcarrigan.com/legal/privacy/).
 ```
 Question: 
 ```
 I agree to be contacted via email, solely for the purpose of addressing this submission.
 ```
 #### 2.4.2. Form Image Header
 ```html
 <div style="width: 100%; text-align: center"><img src="https://cdn.nhcarrigan.com/logo.png" style="width: 250px; height: 250px"></div>
 ```
 #### 2.4.3. Form Confirmation
 Add this at the end of any form specific text.
 ```
 If you'd like to stay up to date on everything we do, come hang out in our server! https://chat.nhcarrigan.com
 ```
 ### 2.5. Community & Communication Templates
 #### 2.5.1. Discord Server Introduction Template
 ```md
 Hello~! I'm Naomi, a 34 year old transfem software engineer and community manager based in Washington. All of my work (and therefore most of my life) is spent online, so I'm always looking for new spaces and people to vibe with. Remote work can feel dreadfully isolating, and this is my attempt to combat that feeling.
 <insert bit about community here>
 ``` 
 #### 2.5.2. freeCodeCamp Contributor Sprint Template
 ```md
 ## This issue is part of Naomi's sprint initiatives.
 If you are interested in working on this issue, [join our Discord](https://chat.freecodecamp.org) and ping Naomi!
 ### Action Items
 - [ ] Prototype created and PRed to https://github.com/freeCodeCamp/curriculumexpansion
 - [ ] Prototype reviewed + approved + merged by staff
 - [ ] Break prototype down into steps (if workshop) or individual "step" (if lab) - write description, hint text **only** (no tests yet), and seed code. Refer to https://contribute.freecodecamp.org/how-to-work-on-coding-challenges
 - [ ] DRAFT PR opened on https://github.com/freeCodeCamp/freeCodeCamp
 - [ ] Team + Naomi review your steps, confirm the breakdown + user stories look good
 - [ ] Begin writing the actual test logic, refer to https://contribute.freecodecamp.org/curriculum-help/#basic-usage-pattern for how to write tests for Python challenges
 - [ ] Mark PR as not a draft, team reviews + approves + merges
 - [ ] YOU DID IT GO CELEBRATE!
 ### Other Details
 - Remember to keep an eye on your PRs and respond to review comments and suggestions
 - For workshops, refer to: https://contribute.freecodecamp.org/how-to-work-on-coding-challenges/
 - For labs, refer to: https://contribute.freecodecamp.org/how-to-work-on-labs/
 ### Questions
 Ping Naomi in the sprint channel on Discord
 ```
 ### 2.6. Gaming Templates
 #### 2.6.1. Guild Wars 2 Recruitment Advertisement Template
 This has to be sent in two chat messages because of the length.
 ```
 Hiya friends~! Naomi's Newbies is a new guild that is really focused on helping newer players come to love the game, and supporting casual players who have busy schedules.
 ```
 ```
 We have no activity requirement, no rep requirement, a Discord community, and more! If you are interested, please whisper me and I will gladly invite you!
 ```
 ### 2.7. Donation Templates
 #### 2.7.1. Discord Bot Donation Copy Template
 These go in the bot SKUs:
 ##### 2.7.1.1. Subscription Name
 ```
 Sponsor Naomi
 ```
 ##### 2.7.1.2. Subscription Description
 ```
 **How Your Support Makes a Difference**
 1. Creating Free Software
  - Develop open-source tools accessible to everyone
  - Design Discord bots for community management and safe spaces
  - Create learning resources and accessibility-focused web applications
 2. Building Inclusive Communities
  - Manage welcoming online spaces where diverse voices are celebrated
  - Organise virtual events, workshops, and mentorship programmes
  - Implement inclusive community guidelines
 3. Guiding Others in Tech
  - Provide mentorship to aspiring technologists from underrepresented groups
  - Create educational content (tutorials, blog posts, videos)
  - Offer career advice and emotional support
 4. Your Contribution's Ripple Effect:
  - Challenges the status quo of the tech industry
  - Creates opportunities for underrepresented individuals in STEM
  - Fosters innovation through diverse perspectives
  - Builds a tech community that reflects and serves all of society
 Every donation, regardless of size, contributes to this mission. Together, we're creating a more inclusive, accessible, and diverse future for technology.
 Thank you for considering a donation and being part of this important journey.
 ```
 ##### 2.7.1.3. Benefit Name
 ```
 Your donation:
 ```
 ##### 2.7.1.4. Benefit Description
 ```
 Helps a transfemme technology witch create free software, build inclusive communities, and guide others on their journey in tech.
 ```
 ##### 2.7.1.5. Notes
 - Use my avatar for subscription
 - Use pentatrans for benefit
 ### 2.8. freeCodeCamp Templates
 #### 2.8.1. freeCodeCamp Sprint Issue Template
 ```md
 **Type:** Workshop/Lab/????  
 **Summary:**
 **User Stories**
 1. 
 2.
 3.
 **Technical Notes**
 - 
 -
 -
 ## This issue is part of Naomi's sprint initiatives.
 If you are interested in working on this issue, [join our Discord](https://chat.freecodecamp.org) and ping Naomi!
 ### Action Items
 - [ ] Prototype created and PRed to https://github.com/freeCodeCamp/curriculumexpansion
 - [ ] Prototype reviewed + approved + merged by staff
 - [ ] Break prototype down into steps (if workshop) or individual "step" (if lab) - write description, hint text **only** (no tests yet), and seed code.
 - [ ] DRAFT PR opened on https://github.com/freeCodeCamp/freeCodeCamp
 - [ ] Team + Naomi review your steps, confirm the breakdown + user stories look good
 - [ ] Begin writing the actual test logic, refer to https://contribute.freecodecamp.org/curriculum-help/#js-helper for how to write tests for JS challenges
 - [ ] Mark PR as not a draft, team reviews + approves + merges
 - [ ] YOU DID IT GO CELEBRATE!
 ### Other Details
 - Remember to keep an eye on your PRs and respond to review comments and suggestions
 - For workshops, refer to: https://contribute.freecodecamp.org/how-to-work-on-coding-challenges/
 - For labs, refer to: https://contribute.freecodecamp.org/how-to-work-on-labs/
 ### Questions
 Ping Naomi in the sprint channel on Discord
 ```
 #### 2.8.2. freeCodeCamp Sprint Progress Update
 ```md
 **Progress Update - <date>**
 <summarise what contributor said>
 ```
 ## 3. DISCLAIMERS AND USAGE REQUIREMENTS
 ### 3.1. Reference to Comprehensive Liability Framework
 **IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
 ### 3.2. Template Usage Disclaimer
 These templates are provided for informational purposes only. Our organisation:
 - Does not provide legal advice or guarantee the legal effectiveness of these templates
 - Does not warrant that these templates will meet specific legal, regulatory, or contextual requirements
 - Recommends that users consult with qualified legal counsel when using these templates for legal matters
 - Assumes no responsibility for outcomes resulting from the use of these templates
 ### 3.3. Customisation Requirements
 Users are responsible for:
 - Customising templates to meet their specific needs and requirements
 - Ensuring compliance with applicable laws, regulations, and organisational policies
 - Verifying the accuracy and appropriateness of template content for their specific use case
 - Obtaining appropriate legal review when necessary
 ## 4. CONCLUSION
 This Templates Documentation provides standardised templates and forms for use throughout our organisation. All users are responsible for ensuring that their use of these templates complies with applicable laws, regulations, and organisational requirements.
 ---
 *For questions about template usage or to suggest improvements, please contact appropriate organisational leadership through designated communication channels.*