Blog for SvelteKit with Metakit

Managing Blog in SvelteKit shouldn't be this hard

Your content files live as .mdx files in a directory. Every edit requires opening a code editor, understanding frontmatter schemas, and creating a pull request. Your marketing writer wants to fix a typo? They need to learn Git. You could adopt a headless CMS, but then you lose the colocated content model, your build gets slower with API calls, and you introduce a dependency on a third-party service for what should be simple markdown files.

Getting started

What you get

• ⚡Framework compatible — Works with your existing SvelteKit setup. No client-side SDK required.
• 🚀Fast builds — Content is statically generated at build time with on-demand revalidation.
• 👁Live preview — Changes in the visual editor hot-reload in your dev server. Writers see exactly what ships.
• 💻Type-safe content — Auto-generated types from your content schema. Catch broken references at build time.
• 🌍Automatic sitemap & RSS — Metakit generates sitemap.xml and RSS feeds from your Blog content.
• 🔒Git-backed history — Every edit is a Git commit. Full history, branch-based previews, and PR reviews.

Integration

Install with a single command, then start using Metakit in your existing SvelteKit codebase.

npm install @metakit/svelte

import { metakit } from '@metakit/react';

const content = metakit({ contentType: 'blog' });

export default async function Page({ params }) {
  const item = await content.get(params.slug);

  return (
    <article>
      <h1>{item.title}</h1>
      <content.Render content={item} />
    </article>
  );
}

Related guides