Skip to content

Open-source status page, incident response and uptime monitoring

chore: structured json ld (#1812)

Maximilian Kaske2509c9b0cca2
diff --git a/apps/web/package.json b/apps/web/package.json
index fced35666..621795832 100644
--- a/apps/web/package.json
+++ b/apps/web/package.json
@@ -63,6 +63,7 @@
"date-fns": "2.30.0",
"date-fns-tz": "2.0.0",
"feed": "4.2.2",
+ "gray-matter": "4.0.3",
"lucide-react": "0.525.0",
"nanoid": "5.0.7",
"next": "16.0.10",
diff --git a/apps/web/src/app/(landing)/[slug]/page.tsx b/apps/web/src/app/(landing)/[slug]/page.tsx
index da65c6680..59c6b8d9f 100644
--- a/apps/web/src/app/(landing)/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/[slug]/page.tsx
@@ -1,14 +1,17 @@
-import {
- BASE_URL,
- getJsonLDBreadcrumbList,
- getJsonLDWebPage,
- getPageMetadata,
-} from "@/app/shared-metadata";
import { CustomMDX } from "@/content/mdx";
import { getMainPages } from "@/content/utils";
+import { getPageMetadata } from "@/lib/metadata/shared-metadata";
+import {
+ createJsonLDGraph,
+ getJsonLDFAQPage,
+ getJsonLDHowTo,
+ getJsonLDOrganization,
+ getJsonLDProduct,
+ getJsonLDSoftwareApplication,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
import { notFound } from "next/navigation";
-import type { BreadcrumbList, WebPage, WithContext } from "schema-dts";
export const dynamicParams = false;
@@ -48,30 +51,23 @@ export default async function Page({
notFound();
}
- const jsonLDWebPage: WithContext<WebPage> = getJsonLDWebPage(page);
-
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
- { name: "Home", url: BASE_URL },
- { name: page.metadata.title, url: `${BASE_URL}/${slug}` },
- ],
- );
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDOrganization(),
+ getJsonLDSoftwareApplication(),
+ getJsonLDProduct(),
+ getJsonLDWebPage(page),
+ getJsonLDHowTo(page),
+ getJsonLDFAQPage(page),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none">
- <script
- type="application/ld+json"
- // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
- dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDWebPage).replace(/</g, "\\u003c"),
- }}
- />
<script
type="application/ld+json"
suppressHydrationWarning
// biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{page.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/blog/[slug]/page.tsx b/apps/web/src/app/(landing)/blog/[slug]/page.tsx
index 6a2cdf184..21b5363bf 100644
--- a/apps/web/src/app/(landing)/blog/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/blog/[slug]/page.tsx
@@ -1,16 +1,19 @@
-import {
- BASE_URL,
- getJsonLDBlogPosting,
- getJsonLDBreadcrumbList,
- getPageMetadata,
-} from "@/app/shared-metadata";
import { CustomMDX } from "@/content/mdx";
import { formatDate, getBlogPosts } from "@/content/utils";
import { getAuthor } from "@/data/author";
+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";
+import {
+ createJsonLDGraph,
+ getJsonLDBlogPosting,
+ getJsonLDBreadcrumbList,
+ getJsonLDFAQPage,
+ getJsonLDHowTo,
+ getJsonLDOrganization,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
import Image from "next/image";
import { notFound } from "next/navigation";
-import type { BlogPosting, BreadcrumbList, WithContext } from "schema-dts";
import { ContentPagination } from "../../content-pagination";
export const dynamicParams = false;
@@ -58,35 +61,27 @@ export default async function Blog({
notFound();
}
- const jsonLDBlog: WithContext<BlogPosting> = getJsonLDBlogPosting(
- post,
- "blog",
- );
-
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDOrganization(),
+ getJsonLDWebPage(post),
+ getJsonLDBlogPosting(post, "blog"),
+ getJsonLDBreadcrumbList([
{ name: "Home", url: BASE_URL },
{ name: "Blog", url: `${BASE_URL}/blog` },
{ name: post.metadata.title, url: `${BASE_URL}/blog/${slug}` },
- ],
- );
+ ]),
+ getJsonLDHowTo(post),
+ getJsonLDFAQPage(post),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none">
<script
type="application/ld+json"
suppressHydrationWarning
- // biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
- dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBlog).replace(/</g, "\\u003c"),
- }}
- />
- <script
- type="application/ld+json"
- suppressHydrationWarning
- // biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
+ // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{post.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/blog/category/[slug]/page.tsx b/apps/web/src/app/(landing)/blog/category/[slug]/page.tsx
index 21304524b..13d540112 100644
--- a/apps/web/src/app/(landing)/blog/category/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/blog/category/[slug]/page.tsx
@@ -1,11 +1,11 @@
import { ContentCategory } from "@/app/(landing)/content-category";
import { ContentList } from "@/app/(landing)/content-list";
+import { getBlogPosts } from "@/content/utils";
import {
defaultMetadata,
ogMetadata,
twitterMetadata,
-} from "@/app/shared-metadata";
-import { getBlogPosts } from "@/content/utils";
+} from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
const TITLE = "Blog Category";
diff --git a/apps/web/src/app/(landing)/blog/page.tsx b/apps/web/src/app/(landing)/blog/page.tsx
index 8bfff9243..b2b9893d9 100644
--- a/apps/web/src/app/(landing)/blog/page.tsx
+++ b/apps/web/src/app/(landing)/blog/page.tsx
@@ -1,6 +1,6 @@
-import { defaultMetadata, ogMetadata } from "@/app/shared-metadata";
-import { twitterMetadata } from "@/app/shared-metadata";
import { getBlogPosts } from "@/content/utils";
+import { defaultMetadata, ogMetadata } from "@/lib/metadata/shared-metadata";
+import { twitterMetadata } from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
import Link from "next/link";
import { ContentCategory } from "../content-category";
diff --git a/apps/web/src/app/(landing)/changelog/[slug]/page.tsx b/apps/web/src/app/(landing)/changelog/[slug]/page.tsx
index cbefb2b1c..01b27925a 100644
--- a/apps/web/src/app/(landing)/changelog/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/changelog/[slug]/page.tsx
@@ -1,15 +1,18 @@
+import { CustomMDX } from "@/content/mdx";
+import { formatDate, getChangelogPosts } from "@/content/utils";
+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";
import {
- BASE_URL,
+ createJsonLDGraph,
getJsonLDBlogPosting,
getJsonLDBreadcrumbList,
- getPageMetadata,
-} from "@/app/shared-metadata";
-import { CustomMDX } from "@/content/mdx";
-import { formatDate, getChangelogPosts } from "@/content/utils";
+ getJsonLDFAQPage,
+ getJsonLDHowTo,
+ getJsonLDOrganization,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
import Image from "next/image";
import { notFound } from "next/navigation";
-import type { BlogPosting, BreadcrumbList, WithContext } from "schema-dts";
import { ContentPagination } from "../../content-pagination";
export const dynamicParams = false;
@@ -57,35 +60,27 @@ export default async function Changelog({
notFound();
}
- const jsonLDBlog: WithContext<BlogPosting> = getJsonLDBlogPosting(
- post,
- "changelog",
- );
-
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDOrganization(),
+ getJsonLDWebPage(post),
+ getJsonLDBlogPosting(post, "changelog"),
+ getJsonLDBreadcrumbList([
{ name: "Home", url: BASE_URL },
{ name: "Changelog", url: `${BASE_URL}/changelog` },
{ name: post.metadata.title, url: `${BASE_URL}/changelog/${slug}` },
- ],
- );
+ ]),
+ getJsonLDHowTo(post),
+ getJsonLDFAQPage(post),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none">
<script
type="application/ld+json"
suppressHydrationWarning
- // biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
- dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBlog).replace(/</g, "\\u003c"),
- }}
- />
- <script
- type="application/ld+json"
- suppressHydrationWarning
- // biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
+ // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{post.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/changelog/category/[slug]/page.tsx b/apps/web/src/app/(landing)/changelog/category/[slug]/page.tsx
index 60843fc4e..7ec556d69 100644
--- a/apps/web/src/app/(landing)/changelog/category/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/changelog/category/[slug]/page.tsx
@@ -1,11 +1,11 @@
import { ContentCategory } from "@/app/(landing)/content-category";
import { ContentList } from "@/app/(landing)/content-list";
+import { getChangelogPosts } from "@/content/utils";
import {
defaultMetadata,
ogMetadata,
twitterMetadata,
-} from "@/app/shared-metadata";
-import { getChangelogPosts } from "@/content/utils";
+} from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
const TITLE = "Changelog Category";
diff --git a/apps/web/src/app/(landing)/changelog/page.tsx b/apps/web/src/app/(landing)/changelog/page.tsx
index 705f6052e..ecc0cf8b2 100644
--- a/apps/web/src/app/(landing)/changelog/page.tsx
+++ b/apps/web/src/app/(landing)/changelog/page.tsx
@@ -1,6 +1,6 @@
-import { defaultMetadata, ogMetadata } from "@/app/shared-metadata";
-import { twitterMetadata } from "@/app/shared-metadata";
import { getChangelogPosts } from "@/content/utils";
+import { defaultMetadata, ogMetadata } from "@/lib/metadata/shared-metadata";
+import { twitterMetadata } from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
import Link from "next/link";
import { ContentCategory } from "../content-category";
diff --git a/apps/web/src/app/(landing)/compare/[slug]/page.tsx b/apps/web/src/app/(landing)/compare/[slug]/page.tsx
index a2ad0d24e..57a5593eb 100644
--- a/apps/web/src/app/(landing)/compare/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/compare/[slug]/page.tsx
@@ -1,13 +1,17 @@
-import {
- BASE_URL,
- getJsonLDBreadcrumbList,
- getPageMetadata,
-} from "@/app/shared-metadata";
import { CustomMDX } from "@/content/mdx";
import { getComparePages } from "@/content/utils";
+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";
+import {
+ createJsonLDGraph,
+ getJsonLDBlogPosting,
+ getJsonLDBreadcrumbList,
+ getJsonLDFAQPage,
+ getJsonLDHowTo,
+ getJsonLDOrganization,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
import { notFound } from "next/navigation";
-import type { BreadcrumbList, WithContext } from "schema-dts";
export const dynamicParams = false;
@@ -48,22 +52,27 @@ export default async function Blog({
notFound();
}
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDOrganization(),
+ getJsonLDWebPage(post),
+ getJsonLDBlogPosting(post, "compare"),
+ getJsonLDBreadcrumbList([
{ name: "Home", url: BASE_URL },
{ name: "Compare", url: `${BASE_URL}/compare` },
{ name: post.metadata.title, url: `${BASE_URL}/compare/${slug}` },
- ],
- );
+ ]),
+ getJsonLDHowTo(post),
+ getJsonLDFAQPage(post),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none">
<script
type="application/ld+json"
suppressHydrationWarning
- // biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
+ // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{post.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/compare/page.tsx b/apps/web/src/app/(landing)/compare/page.tsx
index 0719e8cb4..8099a97db 100644
--- a/apps/web/src/app/(landing)/compare/page.tsx
+++ b/apps/web/src/app/(landing)/compare/page.tsx
@@ -1,10 +1,10 @@
+import { components } from "@/content/mdx";
+import { getComparePages } from "@/content/utils";
import {
defaultMetadata,
ogMetadata,
twitterMetadata,
-} from "@/app/shared-metadata";
-import { components } from "@/content/mdx";
-import { getComparePages } from "@/content/utils";
+} from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
import {
ContentBoxDescription,
diff --git a/apps/web/src/app/(landing)/guides/[slug]/page.tsx b/apps/web/src/app/(landing)/guides/[slug]/page.tsx
index 6934ad1f0..25966dade 100644
--- a/apps/web/src/app/(landing)/guides/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/guides/[slug]/page.tsx
@@ -1,16 +1,19 @@
-import {
- BASE_URL,
- getJsonLDBlogPosting,
- getJsonLDBreadcrumbList,
- getPageMetadata,
-} from "@/app/shared-metadata";
import { CustomMDX } from "@/content/mdx";
import { formatDate, getGuides } from "@/content/utils";
import { getAuthor } from "@/data/author";
+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";
+import {
+ createJsonLDGraph,
+ getJsonLDBlogPosting,
+ getJsonLDBreadcrumbList,
+ getJsonLDFAQPage,
+ getJsonLDHowTo,
+ getJsonLDOrganization,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
import Image from "next/image";
import { notFound } from "next/navigation";
-import type { BlogPosting, BreadcrumbList, WithContext } from "schema-dts";
import { ContentPagination } from "../../content-pagination";
export const dynamicParams = false;
@@ -58,35 +61,27 @@ export default async function Guide({
notFound();
}
- const jsonLDBlog: WithContext<BlogPosting> = getJsonLDBlogPosting(
- post,
- "guides",
- );
-
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDOrganization(),
+ getJsonLDWebPage(post),
+ getJsonLDBlogPosting(post, "guides"),
+ getJsonLDBreadcrumbList([
{ name: "Home", url: BASE_URL },
{ name: "Guides", url: `${BASE_URL}/guides` },
{ name: post.metadata.title, url: `${BASE_URL}/guides/${slug}` },
- ],
- );
+ ]),
+ getJsonLDHowTo(post),
+ getJsonLDFAQPage(post),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none">
<script
type="application/ld+json"
suppressHydrationWarning
- // biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
- dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBlog).replace(/</g, "\\u003c"),
- }}
- />
- <script
- type="application/ld+json"
- suppressHydrationWarning
- // biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
+ // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{post.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/guides/category/[slug]/page.tsx b/apps/web/src/app/(landing)/guides/category/[slug]/page.tsx
index f9e336a45..17053b225 100644
--- a/apps/web/src/app/(landing)/guides/category/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/guides/category/[slug]/page.tsx
@@ -1,11 +1,11 @@
import { ContentCategory } from "@/app/(landing)/content-category";
import { ContentList } from "@/app/(landing)/content-list";
+import { getGuides } from "@/content/utils";
import {
defaultMetadata,
ogMetadata,
twitterMetadata,
-} from "@/app/shared-metadata";
-import { getGuides } from "@/content/utils";
+} from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
const TITLE = "Guide Category";
diff --git a/apps/web/src/app/(landing)/guides/page.tsx b/apps/web/src/app/(landing)/guides/page.tsx
index 7ebfff73f..bbf5212d0 100644
--- a/apps/web/src/app/(landing)/guides/page.tsx
+++ b/apps/web/src/app/(landing)/guides/page.tsx
@@ -1,6 +1,6 @@
-import { defaultMetadata, ogMetadata } from "@/app/shared-metadata";
-import { twitterMetadata } from "@/app/shared-metadata";
import { getGuides } from "@/content/utils";
+import { defaultMetadata, ogMetadata } from "@/lib/metadata/shared-metadata";
+import { twitterMetadata } from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
import { ContentCategory } from "../content-category";
import { ContentList } from "../content-list";
diff --git a/apps/web/src/app/(landing)/oss-friends/page.tsx b/apps/web/src/app/(landing)/oss-friends/page.tsx
index 6ad5b2aa4..d45f8845f 100644
--- a/apps/web/src/app/(landing)/oss-friends/page.tsx
+++ b/apps/web/src/app/(landing)/oss-friends/page.tsx
@@ -1,9 +1,9 @@
+import { components } from "@/content/mdx";
import {
defaultMetadata,
ogMetadata,
twitterMetadata,
-} from "@/app/shared-metadata";
-import { components } from "@/content/mdx";
+} from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
import { z } from "zod";
import {
diff --git a/apps/web/src/app/(landing)/page.tsx b/apps/web/src/app/(landing)/page.tsx
index 857239426..5344d6783 100644
--- a/apps/web/src/app/(landing)/page.tsx
+++ b/apps/web/src/app/(landing)/page.tsx
@@ -1,68 +1,36 @@
import { CustomMDX } from "@/content/mdx";
import { getHomePage } from "@/content/utils";
-import type { Metadata } from "next";
-import type {
- FAQPage,
- Organization,
- Product,
- WebPage,
- WithContext,
-} from "schema-dts";
+import { defaultMetadata } from "@/lib/metadata/shared-metadata";
import {
- defaultMetadata,
+ createJsonLDGraph,
getJsonLDFAQPage,
getJsonLDOrganization,
getJsonLDProduct,
-} from "../shared-metadata";
-
-const jsonLdProduct: WithContext<Product> = getJsonLDProduct();
-
-const jsonLdOrganization: WithContext<Organization> = getJsonLDOrganization();
-
-const jsonLDWebpage: WithContext<WebPage> = {
- "@context": "https://schema.org",
- "@type": "WebPage",
- name: "openstatus",
- description: "Open-source uptime and synthetic monitoring with status pages.",
- url: "https://openstatus.dev",
- image: "https://openstatus.dev/assets/logos/OpenStatus-Logo.svg",
- headline: "Showcase your uptime with a status page",
-};
-
-const jsonLDFAQPage: WithContext<FAQPage> = getJsonLDFAQPage();
+ getJsonLDSoftwareApplication,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
+import type { Metadata } from "next";
export const metadata: Metadata = defaultMetadata;
export default function Page() {
const homePage = getHomePage();
+
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDOrganization(),
+ getJsonLDProduct(),
+ getJsonLDSoftwareApplication(),
+ getJsonLDWebPage(homePage),
+ getJsonLDFAQPage(homePage),
+ ]);
+
return (
<div className="prose dark:prose-invert max-w-none">
<script
type="application/ld+json"
// biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLdProduct).replace(/</g, "\\u003c"),
- }}
- />
- <script
- type="application/ld+json"
- // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
- dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLdOrganization).replace(/</g, "\\u003c"),
- }}
- />
- <script
- type="application/ld+json"
- // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
- dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDWebpage).replace(/</g, "\\u003c"),
- }}
- />
- <script
- type="application/ld+json"
- // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd
- dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDFAQPage).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{homePage.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/play/checker/[slug]/page.tsx b/apps/web/src/app/(landing)/play/checker/[slug]/page.tsx
index ea2c6cf41..5212e4ba3 100644
--- a/apps/web/src/app/(landing)/play/checker/[slug]/page.tsx
+++ b/apps/web/src/app/(landing)/play/checker/[slug]/page.tsx
@@ -1,8 +1,3 @@
-import {
- BASE_URL,
- getJsonLDBreadcrumbList,
- getPageMetadata,
-} from "@/app/shared-metadata";
import {
getCheckerDataById,
latencyFormatter,
@@ -10,9 +5,14 @@ import {
} from "@/components/ping-response-analysis/utils";
import { CustomMDX } from "@/content/mdx";
import { getToolsPage } from "@/content/utils";
+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";
+import {
+ createJsonLDGraph,
+ getJsonLDBreadcrumbList,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
import { redirect } from "next/navigation";
-import type { BreadcrumbList, WithContext } from "schema-dts";
import { mockCheckAllRegions } from "../api/mock";
import { Table } from "./client";
@@ -93,14 +93,15 @@ export default async function Page({
if (!data) redirect("/play/checker");
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDWebPage(page),
+ getJsonLDBreadcrumbList([
{ name: "Home", url: BASE_URL },
{ name: "Playground", url: `${BASE_URL}/play` },
{ name: "Speed Checker", url: `${BASE_URL}/play/checker` },
{ name: data.url, url: `${BASE_URL}/play/checker/${slug}` },
- ],
- );
+ ]),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none">
@@ -109,7 +110,7 @@ export default async function Page({
suppressHydrationWarning
// biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{data.url}</h1>
diff --git a/apps/web/src/app/(landing)/play/checker/page.tsx b/apps/web/src/app/(landing)/play/checker/page.tsx
index f054c4e30..ef303b8a4 100644
--- a/apps/web/src/app/(landing)/play/checker/page.tsx
+++ b/apps/web/src/app/(landing)/play/checker/page.tsx
@@ -1,13 +1,13 @@
-import {
- BASE_URL,
- getJsonLDBreadcrumbList,
- getPageMetadata,
-} from "@/app/shared-metadata";
import { getCheckerDataById } from "@/components/ping-response-analysis/utils";
import { CustomMDX } from "@/content/mdx";
import { getToolsPage } from "@/content/utils";
+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";
+import {
+ createJsonLDGraph,
+ getJsonLDBreadcrumbList,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
-import type { BreadcrumbList, WithContext } from "schema-dts";
import { mockCheckAllRegions } from "./api/mock";
import {
CheckerProvider,
@@ -38,13 +38,14 @@ export default async function Page(props: {
: await getCheckerDataById(id)
: null;
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDWebPage(page),
+ getJsonLDBreadcrumbList([
{ name: "Home", url: BASE_URL },
{ name: "Playground", url: `${BASE_URL}/play` },
{ name: page.metadata.title, url: `${BASE_URL}/play/checker` },
- ],
- );
+ ]),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none">
@@ -53,7 +54,7 @@ export default async function Page(props: {
suppressHydrationWarning
// biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{page.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/play/curl/page.tsx b/apps/web/src/app/(landing)/play/curl/page.tsx
index 73f89e918..7fab0b100 100644
--- a/apps/web/src/app/(landing)/play/curl/page.tsx
+++ b/apps/web/src/app/(landing)/play/curl/page.tsx
@@ -1,12 +1,12 @@
-import {
- BASE_URL,
- getJsonLDBreadcrumbList,
- getPageMetadata,
-} from "@/app/shared-metadata";
import { CustomMDX } from "@/content/mdx";
import { getToolsPage } from "@/content/utils";
+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";
+import {
+ createJsonLDGraph,
+ getJsonLDBreadcrumbList,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
-import type { BreadcrumbList, WithContext } from "schema-dts";
import { Form } from "./client";
export function generateMetadata(): Metadata {
@@ -17,13 +17,14 @@ export function generateMetadata(): Metadata {
export default function Page() {
const page = getToolsPage("curl");
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDWebPage(page),
+ getJsonLDBreadcrumbList([
{ name: "Home", url: BASE_URL },
{ name: "Playground", url: `${BASE_URL}/play` },
{ name: page.metadata.title, url: `${BASE_URL}/play/curl` },
- ],
- );
+ ]),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none">
@@ -32,7 +33,7 @@ export default function Page() {
suppressHydrationWarning
// biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{page.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/play/page.tsx b/apps/web/src/app/(landing)/play/page.tsx
index eaab7486a..179f210c9 100644
--- a/apps/web/src/app/(landing)/play/page.tsx
+++ b/apps/web/src/app/(landing)/play/page.tsx
@@ -1,9 +1,9 @@
+import { components } from "@/content/mdx";
import {
defaultMetadata,
ogMetadata,
twitterMetadata,
-} from "@/app/shared-metadata";
-import { components } from "@/content/mdx";
+} from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
import {
ContentBoxDescription,
diff --git a/apps/web/src/app/(landing)/play/uptime-sla/page.tsx b/apps/web/src/app/(landing)/play/uptime-sla/page.tsx
index 0da6a011e..560f03f32 100644
--- a/apps/web/src/app/(landing)/play/uptime-sla/page.tsx
+++ b/apps/web/src/app/(landing)/play/uptime-sla/page.tsx
@@ -1,12 +1,12 @@
-import {
- BASE_URL,
- getJsonLDBreadcrumbList,
- getPageMetadata,
-} from "@/app/shared-metadata";
import { CustomMDX } from "@/content/mdx";
import { getToolsPage } from "@/content/utils";
+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";
+import {
+ createJsonLDGraph,
+ getJsonLDBreadcrumbList,
+ getJsonLDWebPage,
+} from "@/lib/metadata/structured-data";
import type { Metadata } from "next";
-import type { BreadcrumbList, WithContext } from "schema-dts";
import { Calculation } from "./client";
export function generateMetadata(): Metadata {
@@ -17,13 +17,14 @@ export function generateMetadata(): Metadata {
export default function Page() {
const page = getToolsPage("uptime-sla");
- const jsonLDBreadcrumb: WithContext<BreadcrumbList> = getJsonLDBreadcrumbList(
- [
+ const jsonLDGraph = createJsonLDGraph([
+ getJsonLDWebPage(page),
+ getJsonLDBreadcrumbList([
{ name: "Home", url: BASE_URL },
{ name: "Playground", url: `${BASE_URL}/play` },
{ name: page.metadata.title, url: `${BASE_URL}/play/uptime-sla` },
- ],
- );
+ ]),
+ ]);
return (
<section className="prose dark:prose-invert max-w-none space-y-4">
@@ -32,7 +33,7 @@ export default function Page() {
suppressHydrationWarning
// biome-ignore lint/security/noDangerouslySetInnerHtml: <explanation>
dangerouslySetInnerHTML={{
- __html: JSON.stringify(jsonLDBreadcrumb).replace(/</g, "\\u003c"),
+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),
}}
/>
<h1>{page.metadata.title}</h1>
diff --git a/apps/web/src/app/(landing)/status/page.tsx b/apps/web/src/app/(landing)/status/page.tsx
index cb5cae075..16fdf3212 100644
--- a/apps/web/src/app/(landing)/status/page.tsx
+++ b/apps/web/src/app/(landing)/status/page.tsx
@@ -1,10 +1,10 @@
+import { components } from "@/content/mdx";
+import { env } from "@/env";
import {
defaultMetadata,
ogMetadata,
twitterMetadata,
-} from "@/app/shared-metadata";
-import { components } from "@/content/mdx";
-import { env } from "@/env";
+} from "@/lib/metadata/shared-metadata";
import type { Metadata } from "next";
import {
ContentBoxDescription,
diff --git a/apps/web/src/app/api/og/monitor/route.tsx b/apps/web/src/app/api/og/monitor/route.tsx
index 96c0f0820..c316ae4f0 100644
--- a/apps/web/src/app/api/og/monitor/route.tsx
+++ b/apps/web/src/app/api/og/monitor/route.tsx
@@ -2,8 +2,8 @@ import { ImageResponse } from "next/og";
import { OSTinybird } from "@openstatus/tinybird";
-import { DESCRIPTION, TITLE } from "@/app/shared-metadata";
import { env } from "@/env";
+import { DESCRIPTION, TITLE } from "@/lib/metadata/shared-metadata";
import { BasicLayout } from "../_components/basic-layout";
import { Tracker } from "../_components/tracker";
import { SIZE, calSemiBold, interLight, interRegular } from "../utils";
diff --git a/apps/web/src/app/api/og/page/route.tsx b/apps/web/src/app/api/og/page/route.tsx
index 2e1b98b78..629cdfd57 100644
--- a/apps/web/src/app/api/og/page/route.tsx
+++ b/apps/web/src/app/api/og/page/route.tsx
@@ -2,7 +2,7 @@ import { ImageResponse } from "next/og";
import { Tracker } from "@openstatus/tracker";
-import { DESCRIPTION, TITLE } from "@/app/shared-metadata";
+import { DESCRIPTION, TITLE } from "@/lib/metadata/shared-metadata";
import { api } from "@/trpc/server";
import { BasicLayout } from "../_components/basic-layout";
import { StatusCheck } from "../_components/status-check";
diff --git a/apps/web/src/app/api/og/post/route.tsx b/apps/web/src/app/api/og/post/route.tsx
index 2f0bfe0d8..11e0ba3b3 100644
--- a/apps/web/src/app/api/og/post/route.tsx
+++ b/apps/web/src/app/api/og/post/route.tsx
@@ -1,7 +1,7 @@
/* eslint-disable @next/next/no-img-element */
import { ImageResponse } from "next/og";
-import { TITLE } from "@/app/shared-metadata";
+import { TITLE } from "@/lib/metadata/shared-metadata";
import { BasicLayout } from "../_components/basic-layout";
import {
DEFAULT_URL,
diff --git a/apps/web/src/app/api/og/route.tsx b/apps/web/src/app/api/og/route.tsx
index 759e122b2..64beb7f8b 100644
--- a/apps/web/src/app/api/og/route.tsx
+++ b/apps/web/src/app/api/og/route.tsx
@@ -1,7 +1,7 @@
/* eslint-disable @next/next/no-img-element */
import { ImageResponse } from "next/og";
-import { OG_DESCRIPTION, TITLE } from "@/app/shared-metadata";
+import { OG_DESCRIPTION, TITLE } from "@/lib/metadata/shared-metadata";
import { SIZE } from "./utils";
export const runtime = "edge";
diff --git a/apps/web/src/app/api/og/status/route.tsx b/apps/web/src/app/api/og/status/route.tsx
index 2cbe1dc5e..eb4d0f204 100644
--- a/apps/web/src/app/api/og/status/route.tsx
+++ b/apps/web/src/app/api/og/status/route.tsx
@@ -1,6 +1,6 @@
import { ImageResponse } from "next/og";
-import { DESCRIPTION, TITLE } from "@/app/shared-metadata";
+import { DESCRIPTION, TITLE } from "@/lib/metadata/shared-metadata";
import { cn } from "@/lib/utils";
import { api } from "@/trpc/server";
import type { RouterOutputs } from "@openstatus/api";
diff --git a/apps/web/src/app/layout.tsx b/apps/web/src/app/layout.tsx
index 68a5617ea..ce116ee7d 100644
--- a/apps/web/src/app/layout.tsx
+++ b/apps/web/src/app/layout.tsx
@@ -5,14 +5,14 @@ import type { Metadata } from "next";
import { Inter } from "next/font/google";
import LocalFont from "next/font/local";
+import { ThemeProvider } from "@/components/theme-provider";
+import { Toaster } from "@/components/ui/sonner";
+import { env } from "@/env";
import {
defaultMetadata,
ogMetadata,
twitterMetadata,
-} from "@/app/shared-metadata";
-import { ThemeProvider } from "@/components/theme-provider";
-import { Toaster } from "@/components/ui/sonner";
-import { env } from "@/env";
+} from "@/lib/metadata/shared-metadata";
import { TRPCReactQueryProvider } from "@/trpc/rq-client";
import PlausibleProvider from "next-plausible";
import { NuqsAdapter } from "nuqs/adapters/next/app";
diff --git a/apps/web/src/app/shared-metadata.ts b/apps/web/src/app/shared-metadata.ts
deleted file mode 100644
index deac2c822..000000000
--- a/apps/web/src/app/shared-metadata.ts
+++ /dev/null
@@ -1,243 +0,0 @@
-import type { MDXData } from "@/content/utils";
-import { allPlans } from "@openstatus/db/src/schema/plan/config";
-import type { Metadata } from "next";
-import type {
- BlogPosting,
- BreadcrumbList,
- FAQPage,
- Organization,
- Product,
- WebPage,
- WithContext,
-} from "schema-dts";
-
-export const TITLE = "openstatus";
-export const HOMEPAGE_TITLE =
- "OpenStatus - Open-Source Status Page & Uptime Monitoring";
-export const DESCRIPTION =
- "Monitor your services globally and showcase your uptime with a status page. Get started for free with our open-source status page with uptime monitoring solution.";
-
-export const OG_DESCRIPTION =
- "Open-source status page and uptime monitoring system";
-
-export const BASE_URL =
- process.env.NODE_ENV === "production"
- ? "https://www.openstatus.dev"
- : "http://localhost:3000";
-
-export const twitterMetadata: Metadata["twitter"] = {
- title: TITLE,
- description: DESCRIPTION,
- card: "summary_large_image",
- images: ["/api/og"],
-};
-
-export const ogMetadata: Metadata["openGraph"] = {
- title: TITLE,
- description: DESCRIPTION,
- type: "website",
- images: ["/api/og"],
-};
-
-export const defaultMetadata: Metadata = {
- title: {
- template: `%s | ${TITLE}`,
- default: HOMEPAGE_TITLE,
- },
- description: DESCRIPTION,
- metadataBase: new URL(BASE_URL),
- alternates: {
- canonical: "/",
- },
- twitter: twitterMetadata,
- openGraph: ogMetadata,
-};
-
-export const getPageMetadata = (page: MDXData, basePath?: string): Metadata => {
- const { slug, metadata } = page;
- const { title, description, category, publishedAt } = metadata;
-
- const ogImage = `${BASE_URL}/api/og?title=${encodeURIComponent(
- title,
- )}&description=${encodeURIComponent(
- description,
- )}&category=${encodeURIComponent(category)}`;
-
- const url = basePath
- ? `${BASE_URL}/${basePath}/${slug}`
- : `${BASE_URL}/${slug}`;
-
- return {
- title,
- description,
- alternates: {
- canonical: url,
- },
- openGraph: {
- title,
- description,
- type: "article",
- publishedTime: publishedAt.toISOString(),
- url,
- images: [
- {
- url: ogImage,
- },
- ],
- },
- twitter: {
- card: "summary_large_image",
- title,
- description,
- images: [ogImage],
- },
- };
-};
-
-export const getJsonLDWebPage = (page: MDXData): WithContext<WebPage> => {
- return {
- "@context": "https://schema.org",
- "@type": "WebPage",
- name: `${page.metadata.title} | openstatus`,
- headline: page.metadata.description,
- mainEntityOfPage: {
- "@type": "WebPage",
- "@id": "https://www.openstatus.dev",
- },
- };
-};
-
-export const getJsonLDBlogPosting = (
- post: MDXData,
- basePath: string,
-): WithContext<BlogPosting> => {
- return {
- "@context": "https://schema.org",
- "@type": "BlogPosting",
- headline: post.metadata.title,
- datePublished: post.metadata.publishedAt.toISOString(),
- dateModified: post.metadata.publishedAt.toISOString(),
- description: post.metadata.description,
- image: post.metadata.image
- ? `${BASE_URL}${post.metadata.image}`
- : `/api/og?title=${encodeURIComponent(
- post.metadata.title,
- )}&description=${encodeURIComponent(
- post.metadata.description,
- )}&category=${encodeURIComponent(post.metadata.category)}`,
- url: `${BASE_URL}/${basePath}/${post.slug}`,
- author: {
- "@type": "Person",
- name: post.metadata.author,
- },
- };
-};
-
-export const getJsonLDOrganization = (): WithContext<Organization> => {
- return {
- "@context": "https://schema.org",
- "@type": "Organization",
- name: "openstatus",
- url: "https://openstatus.dev",
- logo: "https://openstatus.dev/assets/logos/OpenStatus-Logo.svg",
- sameAs: [
- "https://github.com/openstatushq",
- "https://linkedin.com/company/openstatus",
- "https://bsky.app/profile/openstatus.dev",
- "https://x.com/openstatushq",
- ],
- contactPoint: [
- {
- "@type": "ContactPoint",
- contactType: "Support",
- email: "[email protected]",
- },
- ],
- };
-};
-
-export const getJsonLDProduct = (): WithContext<Product> => {
- return {
- "@context": "https://schema.org",
- "@type": "Product",
- name: "openstatus",
- description:
- "Open-source uptime and synthetic monitoring with status pages.",
- brand: {
- "@type": "Brand",
- name: "openstatus",
- logo: "https://openstatus.dev/assets/logos/OpenStatus-Logo.svg",
- },
- offers: Object.entries(allPlans).map(([_, value]) => ({
- "@type": "Offer",
- price: value.price.USD,
- name: value.title,
- priceCurrency: "USD",
- availability: "https://schema.org/InStock",
- })),
- };
-};
-
-export const getJsonLDBreadcrumbList = (
- items: { name: string; url: string }[],
-): WithContext<BreadcrumbList> => {
- return {
- "@context": "https://schema.org",
- "@type": "BreadcrumbList",
- itemListElement: items.map((item, index) => ({
- "@type": "ListItem",
- position: index + 1,
- name: item.name,
- item: item.url,
- })),
- };
-};
-
-export const getJsonLDFAQPage = (): WithContext<FAQPage> => {
- return {
- "@context": "https://schema.org",
- "@type": "FAQPage",
- mainEntity: [
- {
- "@type": "Question",
- name: "What are the free limits?",
- acceptedAnswer: {
- "@type": "Answer",
- text: "As free user you will start with a total of one monitor and one status page (incl. three page components) as well as cron jobs of min. 10m. You can upgrade to a paid plan at any time. No credit card is required to sign up and you can cancel at any time.",
- },
- },
- {
- "@type": "Question",
- name: "Who are we?",
- acceptedAnswer: {
- "@type": "Answer",
- text: "We are Thibault and Max and we take you with us on our journey. Read more on our about page at https://www.openstatus.dev/about.",
- },
- },
- {
- "@type": "Question",
- name: "How does it work?",
- acceptedAnswer: {
- "@type": "Answer",
- text: "We ping your endpoints from multiple regions to calculate uptime and display the current status on your status page. We also collect response time data like headers and timing phases and display it on your dashboard.",
- },
- },
- {
- "@type": "Question",
- name: "What regions do we support?",
- acceptedAnswer: {
- "@type": "Answer",
- text: "We support monitoring from 28 regions worldwide across all continents: Europe (Amsterdam, Stockholm, Paris, Frankfurt, London), North America (Dallas, New Jersey, Los Angeles, San Jose, Chicago, Toronto), South America (São Paulo), Asia (Mumbai, Tokyo, Singapore), Africa (Johannesburg), and Oceania (Sydney).",
- },
- },
- {
- "@type": "Question",
- name: "How can I help?",
- acceptedAnswer: {
- "@type": "Answer",
- text: "There are many ways you can help us: Spread the word by telling your friends and colleagues about OpenStatus, report bugs if you find them, suggest new features, contribute to the project if you are a developer, become a paid user if you are a business, or star our project on GitHub.",
- },
- },
- ],
- };
-};
diff --git a/apps/web/src/content/pages/changelog/sms-notification.mdx b/apps/web/src/content/pages/changelog/sms-notification.mdx
index 78fc63e75..16fe627b1 100644
--- a/apps/web/src/content/pages/changelog/sms-notification.mdx
+++ b/apps/web/src/content/pages/changelog/sms-notification.mdx
@@ -1,7 +1,6 @@
---
title: "Get alerted on your cell phone"
-description: ""
- Receive alerts on your cell phone via SMS when your monitor is down.
+description: "Receive alerts on your cell phone via SMS when your monitor is down."
publishedAt: "2023-11-13"
image: "/assets/changelog/sms-notification.png"
author: "openstatus"
diff --git a/apps/web/src/content/pages/guides/api-service-disruption.mdx b/apps/web/src/content/pages/guides/api-service-disruption.mdx
index 363434523..24a0c0e27 100644
--- a/apps/web/src/content/pages/guides/api-service-disruption.mdx
+++ b/apps/web/src/content/pages/guides/api-service-disruption.mdx
@@ -4,6 +4,15 @@ description: "Professional template for communicating API outages and third-part
author: "openstatus"
publishedAt: "2026-01-19"
category: "template"
+faq:
+ - question: "How often should I update users during an API disruption?"
+ answer: "Provide updates every 30-60 minutes during active incidents, even if there's no significant change. Users appreciate knowing you're still working on the issue. Once resolved, a final summary is essential."
+ - question: "Should I name the third-party provider causing the issue?"
+ answer: "Yes, if you can. Being specific helps users understand the scope and that you're transparent about dependencies. Companies like Vercel, Stripe, and GitHub regularly name their providers during incidents. Just remain professional and factual."
+ - question: "What metrics should I include in API disruption updates?"
+ answer: "Include error rates (e.g., '5% of requests failing'), affected endpoints, and timeframes when you have them. Avoid oversharing internal metrics that might confuse users. Focus on impact-oriented data that helps them assess how they're affected."
+ - question: "When should I use this template instead of other incident templates?"
+ answer: "Use this template specifically for API-related issues, third-party provider failures, or integration connectivity problems. Use Database Performance for database-specific issues, Deployment Rollback for deployment failures, or Network Connectivity for regional/CDN issues."
---
Use this template when your API or third-party service provider is experiencing issues. Based on real-world examples from companies like Vercel, Stripe, and GitHub.
diff --git a/apps/web/src/content/pages/guides/database-performance-degradation.mdx b/apps/web/src/content/pages/guides/database-performance-degradation.mdx
index fbe4166a6..d1d956864 100644
--- a/apps/web/src/content/pages/guides/database-performance-degradation.mdx
+++ b/apps/web/src/content/pages/guides/database-performance-degradation.mdx
@@ -4,6 +4,13 @@ description: "Technical template for communicating database latency and performa
author: "openstatus"
publishedAt: "2026-01-19"
category: "template"
+faq:
+ - question: "How do I decide between technical and user-friendly messaging?"
+ answer: "Match your communication to your audience. For developer-focused products, include technical details like p95 latency, query times, and specific database components. For general users, focus on impact: 'slower response times' instead of 'elevated connection pool exhaustion.'"
+ - question: "Should I share the root cause of database performance issues?"
+ answer: "Yes, once resolved. Technical audiences appreciate transparency and can learn from your incidents. Share root cause, mitigation steps taken, and preventative measures. This builds trust and demonstrates engineering maturity."
+ - question: "When should I trigger a database performance incident notification?"
+ answer: "Trigger notifications when p95 latency exceeds 2x normal, error rates exceed 1%, connection timeouts occur, or when user reports indicate widespread slowness. Set up automated monitoring alerts to catch these thresholds early."
---
Use this template when experiencing database performance issues, elevated latency, or query slowdowns. Ideal for engineering teams and technical stakeholders.
diff --git a/apps/web/src/content/pages/guides/deployment-rollback.mdx b/apps/web/src/content/pages/guides/deployment-rollback.mdx
index 415f1eef1..77ce868a8 100644
--- a/apps/web/src/content/pages/guides/deployment-rollback.mdx
+++ b/apps/web/src/content/pages/guides/deployment-rollback.mdx
@@ -4,6 +4,30 @@ description: "Template for communicating deployment failures and rollback proced
author: "openstatus"
publishedAt: "2026-01-19"
category: "template"
+howto:
+ totalTime: "PT1H"
+ steps:
+ - name: "Detect and acknowledge the deployment issue"
+ text: "Identify that a recent deployment is causing problems through monitoring alerts or user reports. Immediately acknowledge the issue and announce rollback decision to users."
+ url: "#investigating"
+ - name: "Execute the rollback"
+ text: "Roll back to the previous stable version while providing status updates. Monitor error rates and system health during the rollback process."
+ url: "#identified"
+ - name: "Monitor post-rollback stability"
+ text: "Verify that the rollback completed successfully and all services have returned to normal operation. Continue monitoring for any lingering issues."
+ url: "#monitoring"
+ - name: "Confirm resolution and communicate lessons"
+ text: "Send final confirmation that services are restored. Schedule post-mortem to identify root cause and document preventative measures for future deployments."
+ url: "#resolved"
+faq:
+ - question: "How quickly should I decide to roll back a deployment?"
+ answer: "If error rates exceed 5% or critical functionality is broken, initiate rollback immediately. Don't wait to debug in production. Roll back first, then investigate the issue in a safe environment. Time is critical - every minute of impact affects user trust."
+ - question: "Should I complete the rollback before communicating, or communicate during?"
+ answer: "Communicate the rollback decision immediately, then provide updates during the process. Users appreciate knowing you're taking action. Example: 'We've initiated a rollback and expect completion in 10 minutes' is better than waiting until it's done."
+ - question: "What if the rollback doesn't fix the issue?"
+ answer: "This suggests the problem isn't with the recent deployment. Pivot your communication to general incident response, investigate the root cause, and consider whether you need to roll back further or take other remediation steps. Update users with revised information."
+ - question: "Do I need a post-mortem after every rollback?"
+ answer: "Yes. Even quick rollbacks deserve analysis. Document what went wrong, why it wasn't caught in testing, and what process changes will prevent recurrence. Share key findings with users if appropriate to show continuous improvement."
---
Use this template when a deployment causes issues and requires rolling back to a previous version. Communicates the issue, mitigation, and resolution clearly.
diff --git a/apps/web/src/content/pages/guides/feature-degradation.mdx b/apps/web/src/content/pages/guides/feature-degradation.mdx
index f7af13fdd..df2c58b09 100644
--- a/apps/web/src/content/pages/guides/feature-degradation.mdx
+++ b/apps/web/src/content/pages/guides/feature-degradation.mdx
@@ -4,6 +4,15 @@ description: "Template for communicating partial service degradation where some
author: "openstatus"
publishedAt: "2026-01-19"
category: "template"
+faq:
+ - question: "When is something 'degraded' vs a full outage?"
+ answer: "Use degraded when the feature still works partially (e.g., 50% success rate, slower than normal, or intermittent failures). Use outage when the feature is completely unavailable (100% failure rate). Clear distinction helps users set expectations."
+ - question: "Should I list all working features or just the broken ones?"
+ answer: "For major features, list both. Users need to know what still works so they can continue their workflow. For minor features, focus on what's broken and state 'all other features operating normally.' The feature impact matrix format works well for complex degradations."
+ - question: "How do I communicate partial degradation percentages to users?"
+ answer: "Be specific: '50% success rate - retry usually works' or '10% error rate - most requests succeeding.' Avoid vague terms like 'some' or 'many.' Percentages help users assess their likelihood of being affected and whether retrying makes sense."
+ - question: "What if I don't know which feature is causing issues?"
+ answer: "Start with what you know: 'We're investigating reports of errors. Some users may be affected.' Then update as you learn more: 'We've confirmed the issue is with [specific feature].' Narrow the scope as quickly as possible to reduce user uncertainty."
---
Use this template when specific features are degraded or unavailable, but the core service remains operational. Helps users understand what's working and what isn't.
diff --git a/apps/web/src/content/pages/guides/network-connectivity-issues.mdx b/apps/web/src/content/pages/guides/network-connectivity-issues.mdx
index 0c7354ddd..2e4d73f1d 100644
--- a/apps/web/src/content/pages/guides/network-connectivity-issues.mdx
+++ b/apps/web/src/content/pages/guides/network-connectivity-issues.mdx
@@ -4,6 +4,13 @@ description: "Template for communicating network outages, CDN problems, and regi
author: "openstatus"
publishedAt: "2026-01-19"
category: "template"
+faq:
+ - question: "How do I identify which region or users are affected?"
+ answer: "Use monitoring data from multiple geographic locations, check CDN provider dashboards, and review user reports by location. Tools like uptime monitors with multi-region checks can quickly identify geographic patterns in outages."
+ - question: "Should I provide a workaround like a direct IP address?"
+ answer: "Yes, if safe and practical. Direct IPs, alternate endpoints, or backup URLs can help users during CDN or DNS issues. Just ensure the workaround is secure and won't create additional problems once the primary issue is resolved."
+ - question: "What if my CDN provider is having issues but hasn't acknowledged it?"
+ answer: "You can still communicate transparently without waiting for your provider. Say 'We're experiencing connectivity issues that appear related to our CDN provider. We're investigating with them and will update you shortly.' Users care about your transparency, not your provider's timeline."
---
Use this template when experiencing network-related issues affecting user connectivity, including CDN problems, regional outages, or ISP issues.
diff --git a/apps/web/src/content/pages/guides/scheduled-maintenance.mdx b/apps/web/src/content/pages/guides/scheduled-maintenance.mdx
index 3f049fb81..d16034ad9 100644
--- a/apps/web/src/content/pages/guides/scheduled-maintenance.mdx
+++ b/apps/web/src/content/pages/guides/scheduled-maintenance.mdx
@@ -4,6 +4,30 @@ description: "Proactive template for communicating planned maintenance windows,
author: "openstatus"
publishedAt: "2026-01-19"
category: "template"
+howto:
+ totalTime: "PT2H"
+ steps:
+ - name: "Plan and schedule maintenance"
+ text: "Choose a low-traffic time window and schedule maintenance at least 1 week in advance. Consider timezone differences for global audiences."
+ url: "#advance-notice-best-practices"
+ - name: "Send advance notifications"
+ text: "Notify users 1 week before, 24 hours before, and 1 hour before maintenance begins. Include exact times, duration, and expected impact."
+ url: "#1-week-before"
+ - name: "Execute maintenance with updates"
+ text: "Begin maintenance at scheduled time, provide status updates every hour, and extend timeline if needed with clear communication."
+ url: "#at-start"
+ - name: "Complete and verify"
+ text: "Test all systems after completion, send completion notice to all users, and communicate any improvements or benefits delivered."
+ url: "#at-completion"
+faq:
+ - question: "How much advance notice should I give for maintenance?"
+ answer: "Minimum 48 hours for minor maintenance under 30 minutes with no downtime. 1 week notice for standard maintenance 1-4 hours with read-only mode. 2+ weeks notice for major maintenance over 4 hours with full downtime."
+ - question: "What if maintenance takes longer than expected?"
+ answer: "Provide updates every hour and notify users immediately of any time extensions. Include the new estimated completion time and reason for the extension."
+ - question: "Should I include timezone information?"
+ answer: "Yes, always include multiple timezones for global audiences or use UTC time with a timezone converter link. This prevents confusion about when maintenance will occur."
+ - question: "What information must be included in maintenance notices?"
+ answer: "Always include exact date and time with timezone, expected duration, impact description, what users can and cannot do during maintenance, and who to contact with questions."
---
Use this template for planned maintenance, infrastructure upgrades, or scheduled downtime. Proactive communication builds trust and reduces support burden.
diff --git a/apps/web/src/content/pages/guides/security-incident-response.mdx b/apps/web/src/content/pages/guides/security-incident-response.mdx
index caf5f8da4..833a271d0 100644
--- a/apps/web/src/content/pages/guides/security-incident-response.mdx
+++ b/apps/web/src/content/pages/guides/security-incident-response.mdx
@@ -4,6 +4,15 @@ description: "Formal template for communicating security issues with professiona
author: "openstatus"
publishedAt: "2026-01-19"
category: "template"
+faq:
+ - question: "Do I need to notify users immediately for every security concern?"
+ answer: "No. Only communicate publicly when there's a confirmed incident with user impact or when you're taking visible security measures (like requiring password resets). Internal security reviews and patched vulnerabilities without exploitation typically don't require public disclosure."
+ - question: "What legal obligations do I have for security incident disclosure?"
+ answer: "This varies by jurisdiction and industry. GDPR requires notification within 72 hours for personal data breaches. CCPA has requirements for California residents. Healthcare (HIPAA) and payment systems (PCI DSS) have specific rules. Always consult with legal counsel before publishing security incident communications."
+ - question: "How much technical detail should I share about a security vulnerability?"
+ answer: "Share enough to demonstrate competence and transparency, but avoid tactical details that could help attackers. Good: 'unauthorized access attempts to our admin panel.' Bad: 'SQL injection on /admin/login using parameter X.' Wait until the vulnerability is fully patched and no longer exploitable before sharing technical details."
+ - question: "Should I tell users to change their passwords?"
+ answer: "Only if there's evidence of credential compromise or unauthorized access to authentication systems. Don't create alarm fatigue by requesting password changes for unrelated security work. Be specific about why you're asking and which accounts are affected."
---
Use this template when investigating or responding to security-related incidents. Maintains professional tone while reassuring users about security measures.
diff --git a/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx b/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx
index 0868e0b3c..478877ec2 100644
--- a/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx
+++ b/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx
@@ -5,6 +5,15 @@ description: "Explore the best alternatives to Atlassian Statuspage including Op
author: "Thibault Le Ouay Ducasse"
publishedAt: "2025-11-05"
category: "alternative"
+faq:
+ - question: "How do I migrate from Atlassian Statuspage to an alternative?"
+ answer: "Most alternatives offer import tools or APIs. Start by exporting your component list, subscriber data, and historical incidents. Set up your new status page in parallel, then coordinate a cutover date. Update all integrations and notify subscribers of the new status page URL before making the switch."
+ - question: "Which alternative is most cost-effective for small teams?"
+ answer: "OpenStatus and Betterstack offer the most generous free tiers. OpenStatus provides unlimited team members at $30/month with monitoring included, while Betterstack has a powerful free tier for solo developers. Both are significantly more affordable than Atlassian Statuspage for small teams."
+ - question: "Can I use these alternatives without built-in monitoring?"
+ answer: "Yes. Status.io focuses purely on status communication without monitoring. Other platforms like OpenStatus, Instatus, and Betterstack include monitoring but also allow manual incident updates, so you can use your existing monitoring tools if preferred."
+ - question: "Do any alternatives support self-hosting?"
+ answer: "OpenStatus is the only open-source option on this list that supports self-hosting, giving you complete control over your data and infrastructure. The other alternatives are cloud-hosted SaaS solutions only."
---
Atlassian Statuspage has long been a go-to choice for organizations needing to communicate their service status. It's a robust, mature platform. However, the service reliability and incident communication landscape is evolving rapidly.
diff --git a/apps/web/src/content/pages/home.mdx b/apps/web/src/content/pages/home.mdx
index ff458472e..bb9787869 100644
--- a/apps/web/src/content/pages/home.mdx
+++ b/apps/web/src/content/pages/home.mdx
@@ -4,6 +4,17 @@ publishedAt: "2025-11-10"
author: "openstatus"
description: "Openstatus helps you communicate openly during incidents. Share what's happening, keep users updated, and let your status page automatically populate real-time data from our uptime monitoring solution."
category: "Product"
+faq:
+ - question: "What are the free limits?"
+ answer: "As free user you will start with a total of one monitor and one status page (incl. three page components) as well as cron jobs of min. 10m. You can upgrade to a paid plan at any time. No credit card is required to sign up and you can cancel at any time."
+ - question: "Who are we?"
+ answer: "We are Thibault and Max and we take you with us on our journey. Read more on our about page at https://www.openstatus.dev/about."
+ - question: "How does it work?"
+ answer: "We ping your endpoints from multiple regions to calculate uptime and display the current status on your status page. We also collect response time data like headers and timing phases and display it on your dashboard."
+ - question: "What regions do we support?"
+ answer: "We support monitoring from 28 regions worldwide across all continents: Europe (Amsterdam, Stockholm, Paris, Frankfurt, London), North America (Dallas, New Jersey, Los Angeles, San Jose, Chicago, Toronto), South America (São Paulo), Asia (Mumbai, Tokyo, Singapore), Africa (Johannesburg), and Oceania (Sydney)."
+ - question: "How can I help?"
+ answer: "There are many ways you can help us: Spread the word by telling your friends and colleagues about OpenStatus, report bugs if you find them, suggest new features, contribute to the project if you are a developer, become a paid user if you are a business, or star our project on GitHub."
---
<div className="space-x-2">
diff --git a/apps/web/src/content/pages/product/api-monitoring.mdx b/apps/web/src/content/pages/product/api-monitoring.mdx
index fda83ad13..85cf45191 100644
--- a/apps/web/src/content/pages/product/api-monitoring.mdx
+++ b/apps/web/src/content/pages/product/api-monitoring.mdx
@@ -4,6 +4,15 @@ publishedAt: "2025-11-10"
author: "openstatus"
description: "Openstatus allows your to monitor your API from multiple regions around the world. "
category: "Product"
+faq:
+ - question: "What types of API endpoints can I monitor?"
+ answer: "You can monitor any HTTP/HTTPS endpoint including REST APIs, GraphQL APIs, webhooks, and third-party service endpoints. OpenStatus supports all HTTP methods (GET, POST, PUT, DELETE, etc.) and custom headers for authentication."
+ - question: "How do assertions work in API monitoring?"
+ answer: "Assertions let you validate API responses beyond just checking if the endpoint is reachable. You can validate status codes (e.g., expect 200), check for specific text in response bodies, or verify header values. This ensures your API returns correct data, not just any response."
+ - question: "What's the difference between internal monitoring tools and OpenStatus?"
+ answer: "Internal tools like Grafana or Signoz monitor from inside your infrastructure and see your services as your servers see them. OpenStatus monitors from external locations worldwide, showing you what your customers actually experience including network issues, CDN problems, and geographic latency."
+ - question: "Can I export monitoring data to my existing observability stack?"
+ answer: "Yes, OpenStatus supports OpenTelemetry (OTLP) export. You can send monitoring metrics to your existing tools like Grafana, Honeycomb, or Datadog, allowing you to combine external monitoring data with your internal metrics and set custom alerts."
---
## Why monitor your API from an external providers?
diff --git a/apps/web/src/content/pages/product/monitoring-as-code.mdx b/apps/web/src/content/pages/product/monitoring-as-code.mdx
index 5a014ae20..372c1be3f 100644
--- a/apps/web/src/content/pages/product/monitoring-as-code.mdx
+++ b/apps/web/src/content/pages/product/monitoring-as-code.mdx
@@ -4,6 +4,30 @@ publishedAt: "2025-11-10"
author: "Maximilian Kaske"
description: "Openstatus gives you the possibility to store your monitoring as code."
category: "Product"
+howto:
+ totalTime: "PT15M"
+ steps:
+ - name: "Create a YAML configuration file"
+ text: "Create a monitoring configuration file (e.g., openstatus.yaml) in your repository. Define your monitors with regions, frequency, and request details using our YAML schema."
+ url: "#yaml--cli"
+ - name: "Install the OpenStatus CLI"
+ text: "Install the OpenStatus CLI tool to your local environment or CI/CD pipeline. Authenticate with your API key to connect to your workspace."
+ url: "https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/"
+ - name: "Apply your configuration"
+ text: "Run 'openstatus monitors apply' to sync your YAML configuration with OpenStatus. The CLI will create or update monitors based on your config file."
+ url: "#yaml--cli"
+ - name: "Commit and version control"
+ text: "Commit your monitoring configuration to git. All changes to your monitors are now tracked, reviewable, and can be rolled back just like your application code."
+ url: "#what-are-the-benefits-of-monitoring-as-code"
+faq:
+ - question: "Should I use YAML with CLI or Terraform for monitoring as code?"
+ answer: "Use YAML + CLI for simplicity and if you're not already using Terraform. It's lightweight and easy to get started. Choose Terraform if you're managing infrastructure as code and want to integrate monitoring into your existing Terraform workflows for unified state management."
+ - question: "Can I manage monitors both via UI and via code?"
+ answer: "Yes, but we recommend choosing one primary method to avoid conflicts. If you apply a YAML config, it will sync the monitors defined in that file. Monitors created only in the UI won't be affected unless you add them to your YAML config."
+ - question: "How do I handle sensitive data like API tokens in my YAML config?"
+ answer: "Never commit tokens directly to git. Use environment variables or secret management tools. In CI/CD, store tokens as encrypted secrets. For local development, use .env files (and add them to .gitignore) or reference secrets from your secret manager."
+ - question: "What happens when I apply changes to an existing monitor?"
+ answer: "The CLI updates the existing monitor with your new configuration. Historical monitoring data is preserved. If you change the monitor name, it will create a new monitor instead of updating, so use unique identifiers consistently."
---
## What are the benefits of monitoring as code?
diff --git a/apps/web/src/content/pages/product/private-locations.mdx b/apps/web/src/content/pages/product/private-locations.mdx
index e337b8500..d044cc98e 100644
--- a/apps/web/src/content/pages/product/private-locations.mdx
+++ b/apps/web/src/content/pages/product/private-locations.mdx
@@ -4,6 +4,30 @@ publishedAt: "2025-11-10"
author: "Thibault Le Ouay Ducasse"
description: "Openstatus allows your to monitor your service from your own network."
category: "Product"
+howto:
+ totalTime: "PT10M"
+ steps:
+ - name: "Create a private location in OpenStatus"
+ text: "In your OpenStatus dashboard, create a new private location and generate an API key. This key will authenticate your probe with the OpenStatus platform."
+ url: "https://docs.openstatus.dev/tutorial/how-to-create-private-location/"
+ - name: "Deploy the Docker container"
+ text: "Pull the private location Docker image (ghcr.io/openstatushq/private-location:latest) and run it with your API key in your infrastructure, VPC, or cloud provider."
+ url: "#docker-container"
+ - name: "Verify the connection"
+ text: "Check your OpenStatus dashboard to confirm the private location is connected and receiving updates. The probe will automatically sync with your monitors every few minutes."
+ url: "https://docs.openstatus.dev/tutorial/how-to-create-private-location/"
+ - name: "Assign monitors to the private location"
+ text: "Update your monitors to use the private location region. The probe will now run checks from inside your network on the defined schedule."
+ url: "https://docs.openstatus.dev/tutorial/how-to-create-private-location/"
+faq:
+ - question: "Why is the Docker image only 8.5MB?"
+ answer: "We keep it minimal by excluding browser-based checks and bundling only the HTTP monitoring engine. This allows deployment on resource-constrained devices like Raspberry Pis while maintaining full API monitoring capabilities."
+ - question: "Can I run multiple private locations in different networks?"
+ answer: "Yes, you can deploy as many private location probes as needed across different networks, VPCs, or regions. Each gets its own API key and appears as a separate monitoring region in your dashboard."
+ - question: "What platforms support the private location Docker image?"
+ answer: "The image supports both ARM64 and AMD64 architectures, running on any Docker-compatible platform including cloud providers (AWS, GCP, Azure), Cloudflare Containers, Kubernetes, Raspberry Pi, and standard Linux servers."
+ - question: "How does the probe communicate with OpenStatus?"
+ answer: "The probe makes outbound connections to OpenStatus to fetch monitor configurations and send results. It doesn't require inbound connections or firewall changes, making it safe to run in restricted networks."
---
Sometimes the services you want to monitor are not accessible from the outside, you want to be able to monitor from your own network.
diff --git a/apps/web/src/content/pages/product/status-page.mdx b/apps/web/src/content/pages/product/status-page.mdx
index 89c92dfd6..795dfe89b 100644
--- a/apps/web/src/content/pages/product/status-page.mdx
+++ b/apps/web/src/content/pages/product/status-page.mdx
@@ -4,6 +4,17 @@ publishedAt: "2025-11-10"
author: "Maximilian Kaske"
description: "Turn transparency into trust with a dedicated status page. Keep users informed during downtime, so you can focus on the fix."
category: "Product"
+faq:
+ - question: "When should I use a public vs private status page?"
+ answer: "Use public status pages for customer-facing services where transparency builds trust. Use private status pages (password-protected or magic link) for internal tools, client-specific deployments, or when you need to control who receives status updates."
+ - question: "What's the difference between monitors and external services in page components?"
+ answer: "Monitors are automatically synced with your OpenStatus uptime monitoring data and update in real-time. External services are manually managed components for third-party dependencies or systems you don't directly monitor but want to report status for."
+ - question: "Can I use my own domain for the status page?"
+ answer: "Yes, you can configure custom domains to host your status page on your own domain (e.g., status.yourcompany.com) instead of the default OpenStatus subdomain. This keeps the experience consistent with your brand."
+ - question: "How do status page subscriptions work?"
+ answer: "Users can subscribe to receive updates when you post status reports or maintenance notices. We support email notifications, RSS/Atom feeds for feed readers, and JSON feeds for programmatic consumption. Subscribers are automatically notified when you publish updates."
+ - question: "Can I customize the appearance of my status page?"
+ answer: "Yes, use the Theme Store to apply community themes or create your own. Themes control colors, fonts, and layout. For private custom themes, contact us. You can also define which data to share (uptime percentages, response times, or manual reports only)."
---
## Why do you need a status page?
diff --git a/apps/web/src/content/pages/product/uptime-monitoring.mdx b/apps/web/src/content/pages/product/uptime-monitoring.mdx
index ad232c6a5..3b73f10fb 100644
--- a/apps/web/src/content/pages/product/uptime-monitoring.mdx
+++ b/apps/web/src/content/pages/product/uptime-monitoring.mdx
@@ -4,6 +4,17 @@ publishedAt: "2025-11-10"
author: "Thibault Le Ouay Ducasse"
description: "Openstatus provides a global multi-cloud uptime monitoring solution."
category: "Product"
+faq:
+ - question: "How many regions should I monitor from?"
+ answer: "Start with 3-5 regions covering your main user geographies. More regions provide better global coverage but use more check quota. For critical services, monitor from all major regions (North America, Europe, Asia) to catch regional issues quickly."
+ - question: "Why monitor from multiple cloud providers instead of just one?"
+ answer: "If your service runs on AWS and your monitoring also runs on AWS, you won't detect AWS-wide outages or network issues affecting AWS connectivity. Using Fly.io, Koyeb, and Railway ensures monitoring independence from your infrastructure provider."
+ - question: "What's the difference between frequency settings?"
+ answer: "Frequency determines how often we check your service (e.g., every 30 seconds, 1 minute, 5 minutes, 10 minutes). Higher frequency (30s) catches issues faster but uses more checks. Lower frequency (10m) is sufficient for non-critical services and conserves quota."
+ - question: "Can uptime monitoring trigger my status page automatically?"
+ answer: "Yes, you can configure monitors to automatically update your status page based on monitoring results. When assertions fail or thresholds are exceeded, the status page can reflect degraded or down status without manual intervention."
+ - question: "How do thresholds and assertions work together?"
+ answer: "Assertions validate response correctness (status code, headers, body content) while thresholds define performance boundaries (degraded latency, timeout). Both can trigger alerts - assertions catch functional failures, thresholds catch performance degradation."
---
```
diff --git a/apps/web/src/content/utils.ts b/apps/web/src/content/utils.ts
index 8cc2e63c8..346f0f3e8 100644
--- a/apps/web/src/content/utils.ts
+++ b/apps/web/src/content/utils.ts
@@ -1,8 +1,27 @@
import fs from "node:fs";
import path from "node:path";
+import matter from "gray-matter";
import slugify from "slugify";
import { z } from "zod";
+// Structured data schemas
+const howtoStepSchema = z.object({
+ name: z.string(),
+ text: z.string(),
+ image: z.string().optional(),
+ url: z.string().optional(),
+});
+
+const howtoSchema = z.object({
+ totalTime: z.string().optional(), // ISO 8601 duration format (e.g., "PT2H")
+ steps: z.array(howtoStepSchema),
+});
+
+const faqItemSchema = z.object({
+ question: z.string(),
+ answer: z.string(),
+});
+
const metadataSchema = z.object({
title: z.string(),
publishedAt: z.coerce.date(),
@@ -10,30 +29,24 @@ const metadataSchema = z.object({
category: z.string(),
author: z.string(),
image: z.string().optional(),
+ // Structured data fields
+ howto: howtoSchema.optional(),
+ faq: z.array(faqItemSchema).optional(),
});
export type Metadata = z.infer<typeof metadataSchema>;
+export type HowToStep = z.infer<typeof howtoStepSchema>;
+export type HowToData = z.infer<typeof howtoSchema>;
+export type FAQItem = z.infer<typeof faqItemSchema>;
function parseFrontmatter(fileContent: string) {
- const frontmatterRegex = /---\s*([\s\S]*?)\s*---/;
- const match = frontmatterRegex.exec(fileContent);
- const frontMatterBlock = match?.[1];
- const content = fileContent.replace(frontmatterRegex, "").trim();
- const frontMatterLines = frontMatterBlock?.trim().split("\n");
- const metadata: Record<string, string> = {};
-
- frontMatterLines?.forEach((line) => {
- const [key, ...valueArr] = line.split(": ");
- let value = valueArr.join(": ").trim();
- value = value.replace(/^['"](.*)['"]$/, "$1"); // Remove quotes
- metadata[key.trim()] = value;
- });
+ const { data, content } = matter(fileContent);
- const validatedMetadata = metadataSchema.safeParse(metadata);
+ const validatedMetadata = metadataSchema.safeParse(data);
if (!validatedMetadata.success) {
console.error(validatedMetadata.error);
- throw new Error(`Invalid metadata ${fileContent}`);
+ throw new Error(`Invalid metadata: ${validatedMetadata.error.message}`);
}
return { metadata: validatedMetadata.data, content };
diff --git a/apps/web/src/lib/metadata/shared-metadata.ts b/apps/web/src/lib/metadata/shared-metadata.ts
new file mode 100644
index 000000000..f7cfc9cdf
--- /dev/null
+++ b/apps/web/src/lib/metadata/shared-metadata.ts
@@ -0,0 +1,85 @@
+import type { MDXData } from "@/content/utils";
+import type { Metadata } from "next";
+
+export const TITLE = "openstatus";
+export const HOMEPAGE_TITLE =
+ "OpenStatus - Open-Source Status Page & Uptime Monitoring";
+export const DESCRIPTION =
+ "Monitor your services globally and showcase your uptime with a status page. Get started for free with our open-source status page with uptime monitoring solution.";
+
+export const OG_DESCRIPTION =
+ "Open-source status page and uptime monitoring system";
+
+export const BASE_URL =
+ process.env.NODE_ENV === "production"
+ ? "https://www.openstatus.dev"
+ : "http://localhost:3000";
+
+export const twitterMetadata: Metadata["twitter"] = {
+ title: TITLE,
+ description: DESCRIPTION,
+ card: "summary_large_image",
+ images: ["/api/og"],
+};
+
+export const ogMetadata: Metadata["openGraph"] = {
+ title: TITLE,
+ description: DESCRIPTION,
+ type: "website",
+ images: ["/api/og"],
+};
+
+export const defaultMetadata: Metadata = {
+ title: {
+ template: `%s | ${TITLE}`,
+ default: HOMEPAGE_TITLE,
+ },
+ description: DESCRIPTION,
+ metadataBase: new URL(BASE_URL),
+ alternates: {
+ canonical: "/",
+ },
+ twitter: twitterMetadata,
+ openGraph: ogMetadata,
+};
+
+export const getPageMetadata = (page: MDXData, basePath?: string): Metadata => {
+ const { slug, metadata } = page;
+ const { title, description, category, publishedAt } = metadata;
+
+ const ogImage = `${BASE_URL}/api/og?title=${encodeURIComponent(
+ title,
+ )}&description=${encodeURIComponent(
+ description,
+ )}&category=${encodeURIComponent(category)}`;
+
+ const url = basePath
+ ? `${BASE_URL}/${basePath}/${slug}`
+ : `${BASE_URL}/${slug}`;
+
+ return {
+ title,
+ description,
+ alternates: {
+ canonical: url,
+ },
+ openGraph: {
+ title,
+ description,
+ type: "article",
+ publishedTime: publishedAt.toISOString(),
+ url,
+ images: [
+ {
+ url: ogImage,
+ },
+ ],
+ },
+ twitter: {
+ card: "summary_large_image",
+ title,
+ description,
+ images: [ogImage],
+ },
+ };
+};
diff --git a/apps/web/src/lib/metadata/structured-data.ts b/apps/web/src/lib/metadata/structured-data.ts
new file mode 100644
index 000000000..69f64aa0f
--- /dev/null
+++ b/apps/web/src/lib/metadata/structured-data.ts
@@ -0,0 +1,233 @@
+import type { MDXData } from "@/content/utils";
+import { allPlans } from "@openstatus/db/src/schema/plan/config";
+import type {
+ BlogPosting,
+ BreadcrumbList,
+ FAQPage,
+ Graph,
+ HowTo,
+ Organization,
+ Person,
+ Product,
+ SoftwareApplication,
+ Thing,
+ WebPage,
+ WithContext,
+} from "schema-dts";
+import { BASE_URL } from "./shared-metadata";
+
+export const getJsonLDWebPage = (page: MDXData): WithContext<WebPage> => {
+ return {
+ "@context": "https://schema.org",
+ "@type": "WebPage",
+ name: `${page.metadata.title} | openstatus`,
+ headline: page.metadata.description,
+ mainEntityOfPage: {
+ "@type": "WebPage",
+ "@id": BASE_URL,
+ },
+ };
+};
+
+export const getJsonLDBlogPosting = (
+ post: MDXData,
+ basePath: string,
+): WithContext<BlogPosting> => {
+ return {
+ "@context": "https://schema.org",
+ "@type": "BlogPosting",
+ headline: post.metadata.title,
+ datePublished: post.metadata.publishedAt.toISOString(),
+ dateModified: post.metadata.publishedAt.toISOString(),
+ description: post.metadata.description,
+ image: post.metadata.image
+ ? `${BASE_URL}${post.metadata.image}`
+ : `/api/og?title=${encodeURIComponent(
+ post.metadata.title,
+ )}&description=${encodeURIComponent(
+ post.metadata.description,
+ )}&category=${encodeURIComponent(post.metadata.category)}`,
+ url: `${BASE_URL}/${basePath}/${post.slug}`,
+ author: {
+ "@type": "Person",
+ name: post.metadata.author,
+ },
+ };
+};
+
+export const getJsonLDOrganization = (): WithContext<Organization> => {
+ return {
+ "@context": "https://schema.org",
+ "@type": "Organization",
+ name: "openstatus",
+ url: BASE_URL,
+ logo: `${BASE_URL}/assets/logos/OpenStatus-Logo.svg`,
+ sameAs: [
+ "https://github.com/openstatushq",
+ "https://linkedin.com/company/openstatus",
+ "https://bsky.app/profile/openstatus.dev",
+ "https://x.com/openstatushq",
+ ],
+ contactPoint: [
+ {
+ "@type": "ContactPoint",
+ contactType: "Support",
+ email: "[email protected]",
+ },
+ ],
+ };
+};
+
+export const getJsonLDProduct = (): WithContext<Product> => {
+ return {
+ "@context": "https://schema.org",
+ "@type": "Product",
+ name: "openstatus",
+ description:
+ "Open-source uptime and synthetic monitoring with status pages.",
+ url: BASE_URL,
+ brand: {
+ "@type": "Brand",
+ name: "openstatus",
+ logo: `${BASE_URL}/assets/logos/OpenStatus-Logo.svg`,
+ },
+ offers: Object.entries(allPlans).map(([_, value]) => ({
+ "@type": "Offer",
+ price: value.price.USD,
+ name: value.title,
+ priceCurrency: "USD",
+ availability: "https://schema.org/InStock",
+ })),
+ };
+};
+
+export const getJsonLDSoftwareApplication =
+ (): WithContext<SoftwareApplication> => {
+ return {
+ "@context": "https://schema.org",
+ "@type": "SoftwareApplication",
+ name: "openstatus",
+ url: BASE_URL,
+ description:
+ "Open-source uptime and synthetic monitoring with status pages.",
+ applicationCategory: "BusinessApplication",
+ applicationSubCategory: "Monitoring & Observability",
+ operatingSystem: "Web, Self-hosted",
+ offers: Object.entries(allPlans).map(([_, value]) => ({
+ "@type": "Offer",
+ price: value.price.USD,
+ name: value.title,
+ priceCurrency: "USD",
+ availability: "https://schema.org/InStock",
+ })),
+ featureList: [
+ "Multi-region uptime monitoring",
+ "API monitoring (REST, GraphQL)",
+ "Branded status pages",
+ "Incident notifications (Slack, PagerDuty, email)",
+ "Monitoring as code",
+ "Self-hosting option",
+ "Open-source",
+ ],
+ screenshot: `${BASE_URL}/assets/landing/dashboard.png`,
+ };
+ };
+
+export const getJsonLDPerson = (item: {
+ name: string;
+ url?: string;
+}): WithContext<Person> => {
+ return {
+ "@context": "https://schema.org",
+ "@type": "Person",
+ name: item.name,
+ url: item.url,
+ };
+};
+
+export const getJsonLDBreadcrumbList = (
+ items: { name: string; url: string }[],
+): WithContext<BreadcrumbList> => {
+ return {
+ "@context": "https://schema.org",
+ "@type": "BreadcrumbList",
+ itemListElement: items.map((item, index) => ({
+ "@type": "ListItem",
+ position: index + 1,
+ name: item.name,
+ item: item.url,
+ })),
+ };
+};
+
+export function getJsonLDFAQPage(input: MDXData): WithContext<FAQPage> | null {
+ if (!input.metadata.faq) {
+ return null;
+ }
+ return {
+ "@context": "https://schema.org",
+ "@type": "FAQPage",
+ mainEntity: input.metadata.faq.map((faq) => ({
+ "@type": "Question",
+ name: faq.question,
+ acceptedAnswer: {
+ "@type": "Answer",
+ text: faq.answer,
+ },
+ })),
+ };
+}
+
+export const getJsonLDHowTo = (post: MDXData): WithContext<HowTo> | null => {
+ if (!post.metadata.howto) {
+ return null;
+ }
+
+ return {
+ "@context": "https://schema.org",
+ "@type": "HowTo",
+ name: post.metadata.title,
+ description: post.metadata.description,
+ totalTime: post.metadata.howto.totalTime,
+ step: post.metadata.howto.steps.map((step, index) => ({
+ "@type": "HowToStep",
+ position: index + 1,
+ name: step.name,
+ text: step.text,
+ image: step.image ?? undefined,
+ url: step.url ?? undefined,
+ })),
+ };
+};
+
+/**
+ * Creates a unified JSON-LD graph from multiple schema objects
+ * Combines multiple schemas into a single @graph structure
+ *
+ * @param items - Array of schema objects with @context
+ * @returns A single schema object with @graph containing all items
+ *
+ * @example
+ * const graph = createJsonLDGraph([
+ * getJsonLDWebPage(data),
+ * getJsonLDBlogPosting(data),
+ * getJsonLDFAQPage(faqs),
+ * ]);
+ */
+export const createJsonLDGraph = (
+ items: (WithContext<Thing> | null)[],
+): Graph => {
+ const graphItems = items
+ .filter((item): item is WithContext<Thing> => item !== null)
+ .map(
+ (item) =>
+ Object.fromEntries(
+ Object.entries(item).filter(([key]) => key !== "@context"),
+ ) as Thing,
+ );
+
+ return {
+ "@context": "https://schema.org",
+ "@graph": graphItems,
+ };
+};
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 88ecfef16..20a0a84ff 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -979,6 +979,9 @@ importers:
feed:
specifier: 4.2.2
version: 4.2.2
+ gray-matter:
+ specifier: 4.0.3
+ version: 4.0.3
lucide-react:
specifier: 0.525.0
version: 0.525.0([email protected])
@@ -1186,7 +1189,7 @@ importers:
version: 2.6.2
drizzle-orm:
specifier: 0.44.4
- version: 0.44.4(@libsql/[email protected])(@opentelemetry/[email protected])(@types/[email protected])([email protected])
+ version: 0.44.4(@libsql/[email protected])(@opentelemetry/[email protected])(@types/[email protected])([email protected])
effect:
specifier: 3.19.12
version: 3.19.12
@@ -1205,7 +1208,7 @@ importers:
version: link:../../packages/tsconfig
'@types/bun':
specifier: latest
- version: 1.3.6
+ version: 1.3.8
typescript:
specifier: 5.9.3
version: 5.9.3
@@ -1367,10 +1370,10 @@ importers:
version: 3.0.3
drizzle-orm:
specifier: 0.44.4
- version: 0.44.4(@libsql/[email protected])(@opentelemetry/[email protected])(@types/[email protected])([email protected])
+ version: 0.44.4(@libsql/[email protected])(@opentelemetry/[email protected])(@types/[email protected])([email protected])
drizzle-zod:
specifier: 0.8.3
zod:
specifier: 4.1.13
version: 4.1.13
@@ -6611,8 +6614,8 @@ packages:
resolution: {integrity: sha512-SQFof9H+LXeWNz8wDe7oN5zu7ket0qwMu5vZubW4GCJ8Kkeh6nBWUz87+KTz/G3Kqsrp0j/W253XJb3KMEeg3w==}
- '@types/[email protected]':
- resolution: {integrity: sha512-uWCv6FO/8LcpREhenN1d1b6fcspAB+cefwD7uti8C8VffIv0Um08TKMn98FynpTiU38+y2dUO55T11NgDt8VAA==}
+ '@types/[email protected]':
+ resolution: {integrity: sha512-3LvWJ2q5GerAXYxO2mffLTqOzEu5qnhEAlh48Vnu8WQfnmSwbgagjGZV6BoHKJztENYEDn6QmVd949W4uESRJA==}
resolution: {integrity: sha512-hWtVTC2q7hc7xZ/RLbxapMvDMgUnDvKvMOpKal4DrMyfGBUfB1oKaZlIRr6mJL+If3bAP6sV/QneGzF6tJjZDg==}
@@ -7032,6 +7035,9 @@ packages:
resolution: {integrity: sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==}
+ resolution: {integrity: sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==}
+
resolution: {integrity: sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==}
@@ -7188,8 +7194,8 @@ packages:
peerDependencies:
'@types/react': ^19
- resolution: {integrity: sha512-OlFwHcnNV99r//9v5IIOgQ9Uk37gZqrNMCcqEaExdkVq3Avwqok1bJFmvGMCkCE0FqzdY8VMOZpfpR3lwI+CsQ==}
+ resolution: {integrity: sha512-fL99nxdOWvV4LqjmC+8Q9kW3M4QTtTR1eePs94v5ctGqU8OeceWrSUaRw3JYb7tU3FkMIAjkueehrHPPPGKi5Q==}
resolution: {integrity: sha512-7Q/6vkyYAwOmQNRw75x+4yRtZCZJXUDmHHlFdkiV0wgv/reNjtJwpu1jPJ0w2kbEpIM0uoKI3S4/f39dU7AjSA==}
@@ -8086,6 +8092,10 @@ packages:
resolution: {integrity: sha512-LmDxfWXwcTArk8fUEnOfSZpHOJ6zOMUJKOtFLFqJLoKJetuQG874Uc7/Kki7zFLzYybmZhp1M7+98pfMqeX8yA==}
+ resolution: {integrity: sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==}
+ engines: {node: '>=0.10.0'}
+
resolution: {integrity: sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==}
@@ -8331,6 +8341,10 @@ packages:
resolution: {integrity: sha512-DKKrynuQRne0PNpEbzuEdHlYOMksHSUI8Zc9Unei5gTsMNA2/vMpoMz/yKba50pejK56qj98qM0SjYxAKi13gQ==}
engines: {node: ^12.22.0 || ^14.16.0 || ^16.0.0 || >=17.0.0}
+ resolution: {integrity: sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==}
+ engines: {node: '>=6.0'}
+
resolution: {integrity: sha512-pCcEwRi+TKpMlxAQObHDQ56KawURgyAf6jtIY046fJ5tIv3zDe/LEIubckAO8fj6JnAxLdmWkUfNyulQ2iKdEw==}
engines: {node: '>=14.0.0'}
@@ -8620,6 +8634,10 @@ packages:
engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
hasBin: true
+ resolution: {integrity: sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==}
+ engines: {node: '>=0.10.0'}
+
resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==}
engines: {node: '>=0.10.0'}
@@ -8764,6 +8782,10 @@ packages:
resolution: {integrity: sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==}
+ resolution: {integrity: sha512-PMSmkqxr106Xa156c2M265Z+FTrPl+oxd/rgOQy2tijQeK5TxQ43psO1ZCwhVOSdnn+RzkzlRz/eY4BgJBYVpg==}
+ hasBin: true
+
resolution: {integrity: sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA==}
hasBin: true
@@ -8809,6 +8831,10 @@ packages:
resolution: {integrity: sha512-KDncfTmOZoOMTFG4mBlG0qUIOlc03fmzH+ru6RgYVZhPkyiy/92Owlt/8UEN+a4TXR1FQetfIpJE8ApdvdVxTg==}
+ resolution: {integrity: sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==}
+ engines: {node: '>=0.10.0'}
+
resolution: {integrity: sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==}
engines: {node: '>=6'}
@@ -10321,6 +10347,10 @@ packages:
resolution: {integrity: sha512-eflK8wEtyOE6+hsaRVPxvUKYCpRgzLqDTb8krvAsRIwOGlHoSgYLgBXoubGgLd2fT41/OUYdb48v4k4WWHQurA==}
engines: {node: '>= 10.13.0'}
+ resolution: {integrity: sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==}
+ engines: {node: '>=4'}
+
resolution: {integrity: sha512-5TF+l7p4+OsnP8BCCvSyZiSPc4x4//p5uPwK8TCnVPJYRmU2aYKMpOXvw8zM5a5JvuuCGN1jmsMwuU2W02ukfA==}
@@ -10491,6 +10521,9 @@ packages:
resolution: {integrity: sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q==}
+ resolution: {integrity: sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==}
+
resolution: {integrity: sha512-WjlahMgHmCJpqzU8bIBy4qtsZdU9lRlcZE3Lvyej6t4tuOuv1vk57OW3MBrj6hXBFx/nNoC9MPMTcr5YA7NQbg==}
engines: {node: '>=6'}
@@ -10581,6 +10614,10 @@ packages:
resolution: {integrity: sha512-gmBGslpoQJtgnMAvOVqGZpEz9dyoKTCzy2nfz/n8aIFhN/jCE/rCmcxabB6jOOHV+0WNnylOxaxBQPSvcWklhA==}
engines: {node: '>=12'}
+ resolution: {integrity: sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==}
+ engines: {node: '>=0.10.0'}
+
resolution: {integrity: sha512-vavAMRXOgBVNF6nyEEmL3DBK19iRpDcoIwW+swQ+CbGiu7lju6t+JklA1MHweoWtadgt4ISVUsXLyDq34ddcwA==}
engines: {node: '>=4'}
@@ -16474,9 +16511,9 @@ snapshots:
'@types/[email protected]': {}
- '@types/[email protected]':
+ '@types/[email protected]':
dependencies:
- bun-types: 1.3.6
+ bun-types: 1.3.8
'@types/[email protected]': {}
@@ -16961,6 +16998,10 @@ snapshots:
+ dependencies:
+ sprintf-js: 1.0.3
+
@@ -17224,7 +17265,7 @@ snapshots:
'@types/node': 24.0.8
'@types/react': 19.2.2
dependencies:
'@types/node': 24.0.8
@@ -17737,16 +17778,16 @@ snapshots:
transitivePeerDependencies:
- supports-color
optionalDependencies:
'@libsql/client': 0.15.15
'@opentelemetry/api': 1.9.0
'@types/pg': 8.15.6
- bun-types: 1.3.6
+ bun-types: 1.3.8
dependencies:
- drizzle-orm: 0.44.4(@libsql/[email protected])(@opentelemetry/[email protected])(@types/[email protected])([email protected])
+ drizzle-orm: 0.44.4(@libsql/[email protected])(@opentelemetry/[email protected])(@types/[email protected])([email protected])
zod: 4.1.13
@@ -18080,6 +18121,10 @@ snapshots:
+ dependencies:
+ is-extendable: 0.1.1
+
@@ -18390,6 +18435,13 @@ snapshots:
+ dependencies:
+ js-yaml: 3.14.2
+ kind-of: 6.0.3
+ section-matter: 1.0.0
+ strip-bom-string: 1.0.0
+
dependencies:
gaxios: 6.7.1
@@ -18864,6 +18916,8 @@ snapshots:
+
@@ -18969,6 +19023,11 @@ snapshots:
+ dependencies:
+ argparse: 1.0.10
+ esprima: 4.0.1
+
dependencies:
argparse: 2.0.1
@@ -19010,6 +19069,8 @@ snapshots:
jwa: 2.0.1
safe-buffer: 5.2.1
+
@@ -20982,6 +21043,11 @@ snapshots:
ajv-formats: 2.1.1([email protected])
ajv-keywords: 5.1.0([email protected])
+ dependencies:
+ extend-shallow: 2.0.1
+ kind-of: 6.0.3
+
dependencies:
parseley: 0.12.1
@@ -21272,6 +21338,8 @@ snapshots:
+
dependencies:
type-fest: 0.7.1
@@ -21396,6 +21464,8 @@ snapshots:
dependencies:
ansi-regex: 6.2.2
+