feat: prepare for release and add new blog post

Author: prplwtf

apps/frontend/content/blog/pterodactyl-v1_12_0.md

@@ -0,0 +1,33 @@
+---
+title: Pterodactyl v1.12.0 is now compatible
+description: We've released a new Blueprint update that makes us compatible with the latest version of Pterodactyl
+author: Emma
+thumbnail: pterodactyl-v1_12-compatibility.jpg
+date: 1/16/2026 18:00 (CEDST)
+num: 2
+---
+
+Pterodactyl recently released `v1.12.0`, which Blueprint was not compatible with.
+I'm happy to share that we've figured out a way to make the latest version compatible, without breaking existing extensions.
+
+### The issues we ran into
+
+We ran into a few issues trying to port Blueprint to the latest version of Pterodactyl.
+These have now been taken care of, but it caused a few delays in the process of making this release.
+
+- I (Emma) was on break while the Pterodactyl update got announced and released. The break lasted until January 12th, while `v1.12.0` released January 6th.
+- Certain dependency updates caused Blueprint themes to break. We've been able to take care of this issue by keeping specific dependencies on their old versions.
+- A newer version of Webpack stopped providing polyfills for functions like `path`. This was taken care of by Pterodactyl, but we had to add an alias for extensions still using the old library.
+
+### What changed?
+
+> Check out the [more detailed changelog](/releases/beta-2026-01) for more information about what changed this release.
+
+We've made Blueprint officially compatible with `v1.12.0`. The latest update may still work on `v1.11.11`, but that version is no longer officially supported and we recommend [updating your panel](/guides/admin/updatepanel).
+
+Besides making compatibility happen, we've added an onboarding modal visible for whenever you install Blueprint for the first time (or update to any version with the modal for the first time)!
+
+### Final words
+
+[Consider donating to Blueprint!](https://hcb.hackclub.com/donations/start/blueprint)
+Donations help us set a solid foundation for the future of Blueprint, and solidify it's place as the industry-leading platform for Pterodactyl panel modding.

apps/frontend/content/guides/admin/install.md

@@ -7,12 +7,6 @@ thumbnail: cli.jpeg
 order: -1
 ---
 
-::card
-Blueprint is currently not _officially_ compatible with the latest version of Pterodactyl. Compatibility is coming sometime this week. In the meantime, join our [Discord community](https://discord.com/servers/blueprint-1063548024825057451) to get pinged when we release the update.
-
-You can track our progress by checking out [this issue](https://github.com/BlueprintFramework/framework/issues/191) and [this pull request](https://github.com/BlueprintFramework/framework/pull/197). If you'd like to donate towards development, you may do so on [HCB](https://hcb.hackclub.com/donations/start/blueprint) or [GitHub Sponsors](https://github.com/sponsors/blueprintframework).
-::
-
 ## Define Pterodactyl directory
 
 Define your Pterodactyl directory, we'll use this later in the guide. If your Pterodactyl webserver **is not** located in this directory, change the path.

apps/frontend/content/releases/beta-2024-12.md

@@ -2,7 +2,6 @@
 version: beta-2024-12
 released: 2024-12-28T19:02:40Z
 summary: Quite a big release
-supported: false
 num: 12
 ---
 

apps/frontend/content/releases/beta-2025-09.md

@@ -2,7 +2,6 @@
 version: beta-2025-09
 released: 09/30/2025 16:06 (GMT+2)
 summary: More stable. Still beta though
-supported: true
 num: 13
 ---
 

apps/frontend/content/releases/beta-2025-10.md

@@ -2,7 +2,6 @@
 version: beta-2025-10
 released: 10/25/2025 22:22 (CET)
 summary: Bug squashed, release released
-supported: true
 num: 14
 ---
 

apps/frontend/content/releases/beta-2025-11.md

@@ -2,7 +2,6 @@
 version: beta-2025-11
 released: 11/28/2025 20:15 (CET)
 summary: better theme support?? in my blueprint??
-supported: false
 num: 15
 ---
 

apps/frontend/content/releases/beta-2025-12.md

@@ -3,14 +3,13 @@ version: beta-2025-12
 released: 12/21/2025 16:30 (CET)
 summary: should've listened to robert
 supported: true
-latest: true
 num: 16
 ---
 
-### Themes
+#### Themes
 
 This version rolls back the theming changes made in [beta-2025-11](/releases/beta-2025-11) ([blog post](/blog/update-on-themes)). The Tailwind color variable editing support has been removed.
 
-### New updater
+#### New updater
 
 We've implemented a new update tool for Blueprint. Updating to this version will require you to run the `blueprint -upgrade` command twice, instead of just once. This shouldn't be much of an issue, the CLI will guide you through the process.

apps/frontend/content/releases/beta-2026-01.md

@@ -0,0 +1,26 @@
+---
+version: beta-2026-01
+released: 1/16/2026 18:00 (CEDST)
+summary: Pterodactyl v1.12 compatibility!
+supported: true
+latest: true
+num: 17
+---
+
+#### Pterodactyl v1.12 compatibility
+
+Blueprint is now compatible with Pterodactyl `v1.12.0`. Read more in the [related blog post](/blog/pterodactyl-v1_12_0).
+
+#### Onboarding modal
+
+We've added an onboarding modal that provides you useful links to our Discord community and privacy policy. This onboarding modal will show up whenever you use Blueprint for the first time (or update to any release containing the onboarding modal for the first time). It can be manually triggered by setting the `introduction_dismissed` flag to `false`.
+
+#### Node.js version requirement
+
+**We've increased the Node.js version requirement from `v17.x` to `v20.x`.** While Pterodactyl updated their minimum version requirement to `v22.x`, we're giving you a bit more time to migrate over.
+
+#### Additional changes
+
+- Updated the general description of what Blueprint is on the extensions admin page.
+- The copyright footer in the admin panel now switches between Pterodactyl and Blueprint depending on the page you're visiting, instead of adding Blueprint to the copyright footer.
+- The `disable_attribution` flag is no longer visibly displayed in the Blueprint flags editor. If you previously had this flag disabled, it will stay disabled. You will have to use the API or interact with the database to update this flag from now on.

apps/frontend/public/img/blog/thumbnails/pterodactyl-v1_12-compatibility.jpg

@@ -12,7 +12,9 @@
       </p>
       <p>{{ post.description || 'No description provided' }}</p>
       <p class="text-default-font/60">
-        <NuxtTime :datetime="post?.date" :relative="true" />
+        <client-only>
+          <NuxtTime :datetime="post?.date" :relative="true" />
+        </client-only>
         (<NuxtTime :datetime="post?.date" />)
       </p>
     </div>