Markdown plugins compatible with Vue:



Markdown plugins compatible with React:



There are several techniques for defining the metadata (title, publishing date, author, ...) of your markdown pages.

The preferred technique depends on whether the metadata is global or local.

Local metadata

What is local metadata? For example, if you want to show some detailed information below the blog post, such as the author's name and country. This metadata is only shown and only needed for that page.

For local metadata, we recommend:

Global metadata

What is global metadata? For example, if you want to show a list of all your blog posts, and you want to always show that list on the left side of your website.

2024-01-01 New Year 2024 Resolution
2023-12-20 Wrapping up 2023
2023-06-15 My summer 2023

Because this list is shown in the sidebar of every page, the publishing date and the title of all blog posts is always needed regardless of which page is rendered. This metadata is needed for every page.

For global metadata, we recommend:


You may be tempted to use import.meta.glob() to retrieve the metadata of all your pages, but we discourage this approach: loading all markdown files at once contradicts Vite's lazy-transpiling approach and it would, therefore, significantly slow down development speed.

With a metadata.js file

A simple way to define metadata is to define a metadata.js file that contains global metadata.

// /pages/metadata.js
// This metadata is always available for every page
export const metadata = [
    url: '/blog/introducing-vike',
    title: 'Introducing Vike',
    date: new Date('2024-01-01')
    url: '/blog/v1',
    title: 'v1.0.0 release',
    date: new Date('2024-06-01')
// /pages/+Layout.jsx
import { metadata } from './metadata'
export function Layout({ children }) {
  // Current URL
  const { urlPathname } = usePageContext()
  // The page's metadata
  const { title } = metadata.find(({ url }) => url === pageContext.urlPathname)
  return <>
    {/* Show the list of blog posts */}
      <p>Blog posts:</p>
      <ul>{{ title, url, date }) =>
            <a href={url}>{data + title}</a>
    {/* The page's content */}
      <h1>{ title }</h1>
      /* children is usually pageContext.Page which is the component defined by */
      { children }
// /pages/blog/introducing-vike/
We're thrilled to officially introduce Vike.

The <h1> of each pages is already defined by /pages/+Layout.jsx: you don't have to define it again in

// /pages/blog/v1/
The `v1.0.0` release signals that Vike is ready for prime time: it now includes
all essentials you'd expect from a frontend framework with a robust design.

With custom settings

You can use meta to create custom settings for defining local metadata.

// /pages/2024-new-year/+Page.mdx
export const metadata = {
  author: {
    firstName: 'John',
    lastName: 'Doe',
    country: 'England'
## Some Markdown
This page uses [markdown](

MDX allows you to export JavaScript values in .mdx files.

Usually, Vike forbids +Page.js files to have "side exports": the +Page.js should only export the value of the Page setting. But, for improved DX, Vike allows markdown files such as +Page.mdx to export the value of other settings.

// /pages/+config.js
// Define the custom settings `metadata`
export default {
  meta: {
    metadata: {
      env: { server: true, client: true }

See API > meta.

It's a common practice to use a metadata.js file for defining global metadata, as well as creating custom settings for defining local metadata.

With frontmatter

Some markdown processors have support for a so-called frontmatter to define the page's metadata.

title: A Markdown Page
description: Example of using markdown with some frontmatter data

## Some Markdown

This page uses [markdown](

The frontmatter data is usually exposed as an export, which you can access by making the export nameOfTheFrontmatterExport a custom setting, see API > meta.

See also