Give your Laravel Knowledge Base a visual editor backed by Git. Writers draft in a beautiful UI — developers keep full control over rendering.
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.
Run `composer require metakit/laravel` to add Metakit to your project. The SDK auto-detects your configuration and sets up content schemas.
Link your GitHub repo to Metakit. We detect your Laravel project structure and configure content paths automatically.
Open the Metakit editor and start creating Knowledge Base content. Rich text, images, frontmatter — all managed through a beautiful interface with live preview.
Every save creates a Git commit. Push triggers your existing CI/CD pipeline. Content goes live through the same deployment process your team already uses.
Install with a single command, then start using Metakit in your existing Laravel codebase.
composer require metakit/laravelimport { metakit } from '@metakit/react';
const content = metakit({ contentType: 'knowledge-base' });
export default async function Page({ params }) {
const item = await content.get(params.slug);
return (
<article>
<h1>{item.title}</h1>
<content.Render content={item} />
</article>
);
}More with Laravel
Blog · Documentation · Changelog · API Reference · Marketing Pages · Help Center · Product Updates
Deploy to Laravel Forge. Content managed visually. Git history preserved.
Start for free →