Merge branch 'main' into content-restructure

# Conflicts:
#	astro.config.ts
#	content/crutchcorn/posts/object-mutation/index.md
#	content/crutchcorn/posts/what-is-ssr-and-ssg/index.md
#	content/data/unicorns.json
#	src/pages/collections/framework-field-guide/index.astro
#	src/utils/achievements/github.ts
#	src/utils/markdown/iframes/rehype-transform.ts
#	src/utils/markdown/index.ts
#	src/utils/markdown/rehype-astro-image-md.ts
#	src/utils/markdown/rehype-header-text.ts

Author: crutchcorn

.eslintignore

@@ -2,4 +2,7 @@ dist
 node_modules
 package-lock.json
 *.md
-*.min.js
+*.min.js
+
+content/**/*
+public/content/**/*

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Community Chat
+    url: https://discord.com/invite/FMcvc6T
+    about: Our dedicated community is here to help.

.github/ISSUE_TEMPLATE/content-suggestion.yml

@@ -0,0 +1,47 @@
+name: Content Suggestion
+description: A suggestion for a new article/post about a technical topic
+title: "[Proposed Post]: "
+labels:
+  - blog post
+body:
+  - type: markdown
+    attributes:
+      value: >-
+        > This is a proposed article to be written (by anyone) for Unicorn
+        Utterances. If this topic seems interesting to you and you'd like to
+        write it, just leave a comment saying so and let us know what we can do
+        to help.
+  - type: input
+    attributes:
+      label: "Proposed topic title:"
+      description: What is the proposed title of the article?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: "Topic description:"
+      description: A description of the content you'd like to see written
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: "Link to existing draft:"
+      description: >-
+        This is an optional link to an existing draft if work on this content
+        has already begun,
+  - type: input
+    attributes:
+      label: "Part of series:"
+      description: >-
+        If this article is proposed to be part of a article series, what should
+        said series be called?
+  - type: textarea
+    attributes:
+      label: Resources
+      description: >-
+        Resources used to research this topic for those that might not know
+        already
+  - type: textarea
+    attributes:
+      label: Other Notes
+      description: Anything else you'd like to add about this potential article

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,18 @@
+name: Feature Request
+description: template for missing feature
+title: "[Feature Request]: "
+body:
+  - type: textarea
+    attributes:
+      label: Description
+      description: A clear and concise description of the problem or missing capability
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: If you have a solution in mind, please describe it.
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      description: Have you considered any alternative solutions or workarounds?

.github/ISSUE_TEMPLATE/website-bug.yml

@@ -0,0 +1,18 @@
+name: Website bug report
+description: Template for bug reports about the website
+title: "[Website Bug]: "
+body:
+  - type: textarea
+    attributes:
+      label: Description
+      description: A clear and concise description of the problem
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Minimal Reproduction
+      description: provide steps to reproduce the problem
+  - type: textarea
+    attributes:
+      label: Exception or Error
+      description: provide error logs

.github/workflows/test.yml

@@ -1,18 +1,31 @@
 name: test
 
-on: push
+on:
+  pull_request:
+    branches:
+      - main
+  push:
+    branches:
+      - main
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.number || github.ref }}
+  cancel-in-progress: true
 
 jobs:
   test:
     env:
       CI: true
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
-      - name: Use Node.js 16.x
-        uses: actions/setup-node@v2
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Setup Node
+        uses: actions/setup-node@v4
         with:
-          node-version: 16.x
+          node-version-file: .nvmrc
           cache: npm
 
       - name: Install Dependencies
@@ -25,11 +38,14 @@ jobs:
       CI: true
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
-      - name: Use Node.js 16.x
-        uses: actions/setup-node@v2
+      - name: Checkout
+        uses: actions/checkout@v4
         with:
-          node-version: 16.x
+          fetch-depth: 0
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: .nvmrc
           cache: npm
 
       - name: Install Dependencies
@@ -42,11 +58,14 @@ jobs:
       CI: true
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
-      - name: Use Node.js 16.x
-        uses: actions/setup-node@v2
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Setup Node
+        uses: actions/setup-node@v4
         with:
-          node-version: 16.x
+          node-version-file: .nvmrc
           cache: npm
 
       - name: Install Dependencies

.prettierignore

@@ -2,4 +2,4 @@ dist
 node_modules
 package-lock.json
 *.md
-*.min.js
+*.min.js

astro.config.ts

@@ -20,6 +20,7 @@ import * as path from "path";
 import svgr from "vite-plugin-svgr";
 import { languages } from "./src/constants/index";
 import { fileToOpenGraphConverter } from "./src/utils/translations";
+import { posts } from "./src/utils/data";
 
 await symlink(path.resolve("content"), path.resolve("public/content"));
 
@@ -45,15 +46,17 @@ export default defineConfig({
 				),
 			},
 			filter(page) {
-				// return true, unless lart part of the URL ends with "_noindex"
+				// return true, unless last part of the URL ends with "_noindex"
 				// in which case it should not be in the sitemap
-				return !(
-					page
-						.split("/")
-						.filter((part) => !!part.length)
-						.at(-1)
-						?.endsWith("_noindex") ?? false
-				);
+				const lastPartOfSlug = page
+					.split("/")
+					.filter((part) => !!part.length)
+					.at(-1);
+
+				if (lastPartOfSlug.endsWith("_noindex")) return false;
+				const relatedPost = posts.find((post) => post.slug === lastPartOfSlug);
+				if (relatedPost && relatedPost.originalLink) return false;
+				return true;
 			},
 			serialize({ url, ...rest }) {
 				return {

content/crutchcorn/collections/react-beyond-the-render/cover.png

@@ -0,0 +1,16 @@
+---
+{
+  title: "React Beyond the Render",
+  description: "React's capabilities are plentiful; there's a reason it's at the top of framework usage. But what can it REALLY do? Let's explore its potential; frontend and backend alike.",
+  tags: ["react", "webdev", "javascript"],
+  coverImg: "./cover.png",
+  published: "2023-12-15T13:45:00.284Z",
+  buttons: [{ text: "Read now", url: "/posts/what-is-reactivity" }],
+}
+---
+
+When React started its journey, it was only able to run on the user's machine. Today, it has immense capabilities on both the frontend and backend. 
+
+From static site generation to mobile apps to server actions, React can handle an application's needs from start-to-finish.
+
+Let's explore how React is able to do all of that; from the very beginning until its abilities today.

content/crutchcorn/collections/react-beyond-the-render/index.md

@@ -49,6 +49,8 @@ Enabling IOMMU on a Gigabyte AMD motherboard is much easier than enabling SVM mo
 
 Once changed, tab over to "Save & Exit" and select "Exit and save changes".
 
+<!-- in-content-ad title="Consider supporting" body="Donating any amount will help towards further development of articles like this." button-text="Visit our Open Collective" button-href="https://opencollective.com/unicorn-utterances" -->
+
 # Windows Features Setup {#windows-features}
 
 Now that we have our BIOS (UEFI, really) configured correctly, we can enable the Windows features we need for the Android Emulator.
@@ -99,7 +101,7 @@ SDK_INSTALL_LOCATION\extras\google\Android_Emulator_Hypervisor_Driver
 
 ![The location of the hypervisor visually using OneCommander app](./hypervisor_filesystem_path.png)
 
-> If you like having this macOS-like preview pane of files, you can find it in the OneCommander application. We covered this app in [our "Ultimate Windows Development Environment Guide" article](posts/ultimate-windows-development-environment-guide/#Paid)
+> If you like having this macOS-like preview pane of files, you can find it in the OneCommander application. We covered this app in [our "Ultimate Windows Development Environment Guide" article](/posts/ultimate-windows-development-environment-guide/#Paid)
 
 Once you have the path located, you'll want to run the `silent_installer.bat` inside of an elevated shell. I did this by pressing <kbd>Win</kbd> + <kbd>X</kbd> and pressing **"Windows PowerShell (Admin)"**. Once that was opened, I copied the path to the PowerShell window via `cd` and ran the installer.
 

content/crutchcorn/posts/android-studio-setup-for-ryzen-cpus/index.md

@@ -0,0 +1,100 @@
+{
+  "$schema": "./node_modules/@angular/cli/lib/config/schema.json",
+  "version": 1,
+  "newProjectRoot": "projects",
+  "projects": {
+    "demo": {
+      "root": "",
+      "sourceRoot": "src",
+      "projectType": "application",
+      "prefix": "app",
+      "schematics": {},
+      "architect": {
+        "build": {
+          "builder": "@angular-devkit/build-angular:browser",
+          "options": {
+            "outputPath": "dist/demo",
+            "index": "src/index.html",
+            "main": "src/main.ts",
+            "polyfills": "src/polyfills.ts",
+            "tsConfig": "src/tsconfig.app.json",
+            "assets": [
+              "src/favicon.ico",
+              "src/assets"
+            ],
+            "styles": [
+              "src/styles.css"
+            ],
+            "scripts": []
+          },
+          "configurations": {
+            "production": {
+              "fileReplacements": [
+                {
+                  "replace": "src/environments/environment.ts",
+                  "with": "src/environments/environment.prod.ts"
+                }
+              ],
+              "optimization": true,
+              "outputHashing": "all",
+              "sourceMap": false,
+              "extractCss": true,
+              "namedChunks": false,
+              "aot": true,
+              "extractLicenses": true,
+              "vendorChunk": false,
+              "buildOptimizer": true
+            }
+          }
+        },
+        "serve": {
+          "builder": "@angular-devkit/build-angular:dev-server",
+          "options": {
+            "browserTarget": "demo:build"
+          },
+          "configurations": {
+            "production": {
+              "browserTarget": "demo:build:production"
+            }
+          }
+        },
+        "extract-i18n": {
+          "builder": "@angular-devkit/build-angular:extract-i18n",
+          "options": {
+            "browserTarget": "demo:build"
+          }
+        },
+        "test": {
+          "builder": "@angular-devkit/build-angular:karma",
+          "options": {
+            "main": "src/test.ts",
+            "polyfills": "src/polyfills.ts",
+            "tsConfig": "src/tsconfig.spec.json",
+            "karmaConfig": "src/karma.conf.js",
+            "styles": [
+              "styles.css"
+            ],
+            "scripts": [],
+            "assets": [
+              "src/favicon.ico",
+              "src/assets"
+            ]
+          }
+        },
+        "lint": {
+          "builder": "@angular-devkit/build-angular:tslint",
+          "options": {
+            "tsConfig": [
+              "src/tsconfig.app.json",
+              "src/tsconfig.spec.json"
+            ],
+            "exclude": [
+              "**/node_modules/**"
+            ]
+          }
+        }
+      }
+    }
+  },
+  "defaultProject": "demo"
+}