minor fixes

astro/.astro/types.d.ts

@@ -897,6 +897,13 @@ declare module 'astro:content' {
   collection: "blog",
   data: any
 } & { render(): Render[".mdx"] },
+"building-fusionauth-homebrew-formula.mdx": {
+  id: "building-fusionauth-homebrew-formula.mdx",
+  slug: "building-fusionauth-homebrew-formula",
+  body: string,
+  collection: "blog",
+  data: any
+} & { render(): Render[".mdx"] },
 "ciam-vs-iam.mdx": {
   id: "ciam-vs-iam.mdx",
   slug: "ciam-vs-iam",
@@ -1079,6 +1086,13 @@ declare module 'astro:content' {
   collection: "blog",
   data: any
 } & { render(): Render[".mdx"] },
+"fusionauth-recognized-industry-distinctions-comparecamp.mdx": {
+  id: "fusionauth-recognized-industry-distinctions-comparecamp.mdx",
+  slug: "fusionauth-recognized-industry-distinctions-comparecamp",
+  body: string,
+  collection: "blog",
+  data: any
+} & { render(): Render[".mdx"] },
 "fusionauth-reviews-around-world.mdx": {
   id: "fusionauth-reviews-around-world.mdx",
   slug: "fusionauth-reviews-around-world",
@@ -1107,6 +1121,13 @@ declare module 'astro:content' {
   collection: "blog",
   data: any
 } & { render(): Render[".mdx"] },
+"fusionauth-update-saml.mdx": {
+  id: "fusionauth-update-saml.mdx",
+  slug: "fusionauth-update-saml",
+  body: string,
+  collection: "blog",
+  data: any
+} & { render(): Render[".mdx"] },
 "fusionauth-website-how-we-do-it.mdx": {
   id: "fusionauth-website-how-we-do-it.mdx",
   slug: "fusionauth-website-how-we-do-it",
@@ -1219,6 +1240,13 @@ declare module 'astro:content' {
   collection: "blog",
   data: any
 } & { render(): Render[".mdx"] },
+"join-us-boulder-startup-week.mdx": {
+  id: "join-us-boulder-startup-week.mdx",
+  slug: "join-us-boulder-startup-week",
+  body: string,
+  collection: "blog",
+  data: any
+} & { render(): Render[".mdx"] },
 "jwt-authorization-microservices-gateway.mdx": {
   id: "jwt-authorization-microservices-gateway.mdx",
   slug: "jwt-authorization-microservices-gateway",
@@ -1464,6 +1492,13 @@ declare module 'astro:content' {
   collection: "blog",
   data: any
 } & { render(): Render[".mdx"] },
+"user-data-security-is-a-breach.mdx": {
+  id: "user-data-security-is-a-breach.mdx",
+  slug: "user-data-security-is-a-breach",
+  body: string,
+  collection: "blog",
+  data: any
+} & { render(): Render[".mdx"] },
 "using-oauth-and-pkce-to-add-authentication-to-your-gatsby-site.mdx": {
   id: "using-oauth-and-pkce-to-add-authentication-to-your-gatsby-site.mdx",
   slug: "using-oauth-and-pkce-to-add-authentication-to-your-gatsby-site",

astro/src/components/Search.astro

@@ -1,7 +1,7 @@
 ---
 ---
 <!-- Search modal -->
-<div class="backdrop-blur-sm bg-slate-500/10 fixed flex items-center justify-center hidden inset-0 overflow-auto z-20" data-widget="search">
+<div class="backdrop-blur-sm bg-slate-500/10 fixed flex items-center justify-center hidden inset-0 overflow-auto z-30" data-widget="search">
   <div class="bg-white border border-slate-900/10 flex flex-col h-4/5 max-w-4xl mx-auto rounded-md shadow-2xl text-slate-500 w-11/12 dark:bg-slate-800 dark:border-slate-100/10 dark:text-slate-400">
     <header class="border-b border-slate-900/10 flex flex-shrink items-center px-6 py-4 dark:border-slate-100/10">
       <i class="fa-regular fa-magnifying-glass mr-4"></i>

astro/src/components/blog/sso/starting.mdx

@@ -6,6 +6,6 @@ Once the FusionAuth service is started, open a browser and access [http://localh
 
 Fill in the admin user account details, read and accept the License Agreement. When you are ready, click **"Submit"**.
 
-<Aside type="tip">Learn more about the [Setup Wizard here](https://fusionauth.io/docs/v1/tech/tutorials/setup-wizard).</Aside>
+<Aside nodark="true" type="tip">Learn more about the [Setup Wizard here](https://fusionauth.io/docs/v1/tech/tutorials/setup-wizard).</Aside>
 
 After submitting, you'll be taken to a login screen where you need to fill in the credentials you specified during the setup wizard and sign in to the FusionAuth administrative user interface. Later, you'll use the same admin account for testing the SSO of the application.

astro/src/content/blog/announcing-fusionauth-1-43.mdx

@@ -62,7 +62,7 @@ However, the community has shared situations where a wildcard is helpful, such a
 
 Again, with great power comes great responsibility.
 
-<Aside type="caution">If you are allowing wildcards, ensure that the scope of the wildcard is as narrow as possible and that you entirely control all content and code running at the wildcarded URLs. Otherwise you could run into a situation where someone hijacks authorization codes and steals access tokens.</Aside>
+<Aside nodark="true" type="caution">If you are allowing wildcards, ensure that the scope of the wildcard is as narrow as possible and that you entirely control all content and code running at the wildcarded URLs. Otherwise you could run into a situation where someone hijacks authorization codes and steals access tokens.</Aside>
 
 ## The rest of it
 

astro/src/content/blog/consents-example.mdx

@@ -16,7 +16,7 @@ In this tutorial, we'll build a basic Node.js and [Express](http://expressjs.com
 
 The application itself is very simple: it will let users sign up via FusionAuth, allow them to set their permissions for marketing consent, and allow them to update their profile and consents at any time. With these basics in place, you'll see how FusionAuth works and how it can extend the application to do whatever you need. You can also [skip ahead and view the code](https://github.com/fusionauth/fusionauth-example-express-consents), although much of the application is defined in FusionAuth as detailed in this guide.
 
-<Aside type="note">The profile and custom registration forms described below are part of our paid plans. Please see the [pricing page](/pricing) for more information about paid plans. Consents, however, are community plan features.</Aside>
+<Aside nodark="true" type="note">The profile and custom registration forms described below are part of our paid plans. Please see the [pricing page](/pricing) for more information about paid plans. Consents, however, are community plan features.</Aside>
 
 ## Prerequisites
 

astro/src/content/blog/easy-integration-fusionauth-nodejs.mdx

@@ -16,7 +16,7 @@ There are a variety of strategies for authentication in Node.js apps, but none p
 
 We'll assume that you are using a unix command-line application like Power Shell on Windows, Terminal on macOS, or a standard terminal on Linux. You will also need **cURL** or some means of creating `GET` and `POST` requests to your localhost. I like REST clients such as [Insomnia](https://insomnia.rest/ "Get Insomnia") or [Postman](https://www.getpostman.com/ "Get Postman"). Let's get coding!
 
-<Aside type="note">
+<Aside nodark="true" type="note">
 The Node client is deprecated, however, this tutorial still works. We are currently working on an updated tutorial with our TypeScript library. You can track the progress of that [here](https://github.com/FusionAuth/fusionauth-site/issues/1097).
 </Aside>
 

astro/src/content/blog/easy-integration-of-fusionauth-and-spring.mdx

@@ -15,7 +15,7 @@ Making a Spring application with FusionAuth is easy. Follow the steps below and
 
 {/* more */}
 
-<Aside type="caution">
+<Aside nodark="true" type="caution">
 This post is old and no longer works. If you'd like to use Spring and FusionAuth, read [the Spring Boot FusionAuth quickstart](/docs/quickstarts/quickstart-springboot-web).
 </Aside>
 
@@ -406,7 +406,7 @@ http.addFilterAfter(new OAuth2ClientContextFilter(), AbstractPreAuthenticatedPro
 
 ## Conclusion
 
-<Aside type="caution">
+<Aside nodark="true" type="caution">
 This post is old and no longer works. If you'd like to use Spring and FusionAuth, read [the Spring Boot FusionAuth quickstart](/docs/quickstarts/quickstart-springboot-web).
 </Aside>
 

astro/src/content/blog/how-to-migrate-from-firebase.mdx

@@ -60,7 +60,7 @@ Another is to migrate it all to an environment where you have more control. What
 
 Such guidance is beyond the scope of this article, though there is plenty of discussion on the internet. Here's an [article about moving from Firebase to AWS](https://aws.amazon.com/blogs/startups/migrating-your-startup-from-firebase-to-aws/) and here's a [GitHub issue thread discussing alternatives](https://github.com/WelcometoMyGarden/welcometomygarden/issues/106).
 
-<Aside type="note">
+<Aside nodark="true" type="note">
 This blog post gives general guidance on migration off of Firebase to any other auth provider. If you are looking for step by step instructions on how to migrate from Firebase to FusionAuth, please review our [Firebase migration guide](/docs/v1/tech/migration-guide/firebase).
 </Aside>
 

astro/src/content/blog/nextjs-single-sign-on.mdx

@@ -55,15 +55,15 @@ This setup allows users in FusionAuth to sign in to the Next.js application auto
 
 <Setup />
 
-![The OAuth details tab.](/assets/img/blogs/nextjs-single-sign-on/fusionauth-callback.png)
+![The OAuth details tab.](/img/blogs/nextjs-single-sign-on/fusionauth-callback.png)
 
 * Record the generated "Client Id" and the "Client Secret" in a text file or to the clipboard. You'll use these below.
 * Add the value `http://localhost:3000/api/auth/callback/fusionauth` to the "Authorized redirect URLs" field. This will be used by FusionAuth to redirect the user to your application page once the user is successfully authenticated.
 * Scroll down and check the "Require registration" checkbox. This ensures that users who haven't been registered for this application in FusionAuth aren't able to access it when using the hosted login pages.
 
 After filling in the details, click the "Save" icon.
 
-<Aside type="note">You aren't limited to one application, by the way. If you have multiple applications, or even other applications like Zendesk or forum software, set them up here to enable SSO.</Aside>
+<Aside nodark="true" type="note">You aren't limited to one application, by the way. If you have multiple applications, or even other applications like Zendesk or forum software, set them up here to enable SSO.</Aside>
 
 
 ### Register the user
@@ -124,7 +124,7 @@ Now that you have the application running, let's implement the authentication pr
 
 ### Installing NextAuth.js
 
-<Aside type="tip">We recommend you look at the [NextAuth.js Getting Start guide](https://next-auth.js.org/getting-started/example) for the most up-to-date instructions.</Aside>
+<Aside nodark="true" type="tip">We recommend you look at the [NextAuth.js Getting Start guide](https://next-auth.js.org/getting-started/example) for the most up-to-date instructions.</Aside>
 
 First, install NextAuth.js.
 

astro/src/content/blog/single-sign-on-laravel-fusionauth.mdx

@@ -76,7 +76,7 @@ This setup allows users in FusionAuth to sign in to the Laravel application auto
 
 After filling in the details, click the "Save" icon.
 
-<Aside type="note">You aren't limited to one application, by the way. If you have multiple applications, or even other applications like Zendesk or forum software, set them up here to enable SSO.</Aside>
+<Aside nodark="true" type="note">You aren't limited to one application, by the way. If you have multiple applications, or even other applications like Zendesk or forum software, set them up here to enable SSO.</Aside>
 
 ### Register the user
 
@@ -90,7 +90,7 @@ Here's an example [Kickstart file](https://github.com/FusionAuth/fusionauth-exam
 
 ## Installing and configuring Laravel
 
-<Aside type="caution">If you already have a running Laravel application, please skip this step.</Aside>
+<Aside nodark="true" type="caution">If you already have a running Laravel application, please skip this step.</Aside>
 
 There are several ways of installing Laravel, but we recommend using it inside a Docker container via Laravel Sail. To do so, you can execute the command below to automatically download and install every package needed:
 
@@ -107,7 +107,7 @@ $ cd my-app
 $ ./vendor/bin/sail up -d
 ```
 
-<Aside type="tip">The command `./vendor/bin/sail` has a lot of built-in tools to handle the containerized application from your host machine and it forwards every unknown argument to `docker compose`. So, the command above would actually just call `docker compose up -d` with the necessary context and environment to run it successfully.</Aside>
+<Aside nodark="true" type="tip">The command `./vendor/bin/sail` has a lot of built-in tools to handle the containerized application from your host machine and it forwards every unknown argument to `docker compose`. So, the command above would actually just call `docker compose up -d` with the necessary context and environment to run it successfully.</Aside>
 
 To test whether the Laravel application is up and running as expected, open a browser and access [http://localhost](http://localhost).
 
@@ -128,7 +128,7 @@ The first thing you need to do is add the [FusionAuth provider](https://github.c
 ```shell
 $ ./vendor/bin/sail composer require socialiteproviders/fusionauth
 ```
-<Aside type="note">When running the command above, [composer](https://getcomposer.org) will automatically install the necessary `laravel/socialite` package</Aside>
+<Aside nodark="true" type="note">When running the command above, [composer](https://getcomposer.org) will automatically install the necessary `laravel/socialite` package</Aside>
 
 Alter the service provider responsible for listening to events at `app/Providers/EventServiceProvider.php` to tell Laravel that it should call `FusionAuthExtendSocialite` class when there is an event for Socialite. To do this, change its `$listen` property to add the following entry to the array:
 
@@ -140,7 +140,7 @@ protected $listen = [
 ];
 ```
 
-<Aside type="note">If you already have something in the `$listen` array (like `Registered::class => [...]`), please keep it and add a new entry to the array</Aside>
+<Aside nodark="true" type="note">If you already have something in the `$listen` array (like `Registered::class => [...]`), please keep it and add a new entry to the array</Aside>
 
 Now, configure your application with the necessary settings to interact with the FusionAuth service, by adding a new entry to the array located at `config/services.php`:
 
@@ -188,7 +188,7 @@ Then, go to your `database/migrations` folder, where you'll find a file there wi
 
 Edit that file to add three new columns to the `users` table: `fusionauth_id`, `fusionauth_access_token` and `fusionauth_refresh_token` and allow `NULL` values in the `password` column. You'd want to save the access token in your database to make requests to the FusionAuth API or other APIs that accept FusionAuth access tokens on behalf of the user. The refresh token is used to exchange an expired access token with a new one (but you'd still have to implement this yourself, as Socialite still doesn't do it). This way, users don't need to log in again to your FusionAuth instance as long as the refresh token is still valid.
 
-<Aside type="tip">If you cloned our [GitHub repository](https://github.com/FusionAuth/fusionauth-example-laravel-single-sign-on), you can just copy the contents from [laravel/migration.php](https://github.com/FusionAuth/fusionauth-example-laravel-single-sign-on/blob/main/laravel/migration.php).</Aside>
+<Aside nodark="true" type="tip">If you cloned our [GitHub repository](https://github.com/FusionAuth/fusionauth-example-laravel-single-sign-on), you can just copy the contents from [laravel/migration.php](https://github.com/FusionAuth/fusionauth-example-laravel-single-sign-on/blob/main/laravel/migration.php).</Aside>
 
 ```php
 <?php
@@ -282,7 +282,7 @@ protected $hidden = [
 
 Now that your `Users` model and table have more details about the integration, you should define the necessary routes to redirect the user to the FusionAuth login and the page that the user will be redirected to after completing the process and obtaining an access token there. Add them to the `routes/web.php` file:
 
-<Aside type="tip">If you cloned our [GitHub repository](https://github.com/FusionAuth/fusionauth-example-laravel-single-sign-on), you can just copy the contents from [laravel/routes.php](https://github.com/FusionAuth/fusionauth-example-laravel-single-sign-on/blob/main/laravel/routes.php).</Aside>
+<Aside nodark="true" type="tip">If you cloned our [GitHub repository](https://github.com/FusionAuth/fusionauth-example-laravel-single-sign-on), you can just copy the contents from [laravel/routes.php](https://github.com/FusionAuth/fusionauth-example-laravel-single-sign-on/blob/main/laravel/routes.php).</Aside>
 
 ```php
 <?php