Blog VitePress plugin markdown-it

Reading Time

Reading time for this document is 9 minutes for 2445 words.

@binarynoir/vitepress-blog turns pages into a blog with frontmatter alone. Any page, in any folder, can be a post. A main blog lists posts from the whole site, and section blogs list the posts of one folder, the same way section glossaries and tagged pages work. Every blog gets its own RSS feed.

See it live

The BinaryNoir blog is this site's real blog, built with this plugin. Its feed is the one the navbar's RSS icon links to.
The Scopes Demo is a small main blog with a section blog inside it, and example posts that show which blog lists which post. It is limited to its own folder, so the examples stay off the real blog.
The Browse Demo is a section blog of example posts in three categories over two years, for trying the browse panel: filter by category, keyword, year and month, combine them, and open a long row with "+N more".

Open any post to see its byline under the title, and links to the newer and older posts in its blog at the end, in place of VitePress's previous / next links.

Why this plugin

VitePress has no blog of its own. The usual approach is a data loader that collects your posts, and a Vue component you write to list them. Or you switch to a blog theme, and your docs take on that theme. This plugin is built for the other case: a documentation site that also needs to publish news, without leaving the default theme or writing components.

Posts live where their subject lives. A release note can sit next to the API page it changes, and a team's update in the team's folder. The frontmatter decides which blog lists it, not a posts/ folder.
One site, many blogs. Each part of the site can have its own section blog, and the main blog still gathers what everyone should see. Other approaches give you one list, and filtering it is up to you.
A feed for each blog. Readers subscribe to only the part of the site they care about: one product's releases, one team's updates. Every blog page and block has its own "Subscribe" link.
Plain pages, built ahead of time. Lists are Markdown written at build time, so they are in the static HTML and in local search, and they work without JavaScript. Pagination and filters by category, keyword and date are an enhancement on top.
It fits with the other plugins. Posts sort into the sidebar with Auto Sidebar's .sort and .limit, titles lose their Markdown Tags badges in lists and feeds, and pages that Exclude leaves out are never listed.

Install

npm install --save-dev @binarynoir/vitepress-blog

Needs Node 22 or later and VitePress 2.

Use

Wrap your config with withBlog. In your theme, import the stylesheet and call useBlog():

// .vitepress/config.mts
import { defineConfig } from 'vitepress';
import { withBlog } from '@binarynoir/vitepress-blog/vitepress';

export default withBlog(
  defineConfig({
    sitemap: { hostname: 'https://example.com' },
    // ...your config
  }),
  {
    authors: { jane: { name: 'Jane Doe', url: 'https://example.com/jane' } },
  },
);

// .vitepress/theme/index.ts
import DefaultTheme from 'vitepress/theme';
import { useBlog } from '@binarynoir/vitepress-blog/client';
import '@binarynoir/vitepress-blog/style.css';

export default {
  extends: DefaultTheme,
  setup() {
    // Pages (?page=2) and filters (?category=, ?tag=, ?year=, ?month=) on blog pages.
    useBlog();
  },
};

withBlog keeps any markdown.config, transformHead, transformPageData and buildEnd you already have, so it composes with other withX() wrappers in any order.

Wiring it by hand

This site wires the five pieces one by one, so each is visible in its config. Pass the same options to all five:

import { blogMarkdown } from '@binarynoir/vitepress-blog';
import {
  blogHead,
  blogPageData,
  blogVitePlugin,
  writeBlogFeeds,
} from '@binarynoir/vitepress-blog/vitepress';

const blogOptions = { siteUrl: 'https://example.com' };

export default defineConfig({
  markdown: {
    config(md) {
      md.use(blogMarkdown, blogOptions); // lists, bylines, newer / older links
    },
  },
  transformHead: (context) => blogHead(context, blogOptions), // social tags, feed links
  transformPageData: (pageData, context) => blogPageData(pageData, context, blogOptions), // descriptions
  buildEnd: (siteConfig) => writeBlogFeeds(siteConfig, blogOptions), // RSS feeds, images
  vite: { plugins: [blogVitePlugin(blogOptions)] }, // fresh lists and feeds in `vitepress dev`
});

Writing a post

A page is a post when its frontmatter has a blog key. blog: true is a post with every default; an object sets its details:

---
title: We launched
blog:
  date: 2026-10-01 09:00
  updated: 2026-10-05 16:30
  summary: Team A's first release is out.
  image: ./launch.png
  imageAlt: The release dashboard
  author: [jane, Sam Lee]
  tags: [team-a, dashboard]
  category: Releases
  scope: site
  pinned: true
---

Key	Default	What it does
`title`	the page's `title`, then its `#` heading	Title in lists, feeds and social cards.
`summary`	the page's `description`, then first prose	One or two sentences for cards, feeds and the page's description.
`date`	none	When the post was published: a date, or a date and time. See Dates and times. Newest first; undated posts go last.
`updated`	none	When the post was last changed, in the same forms. The byline shows both, and it is the feed's last-updated time.
`image`	none	Card, social and feed image: relative to the post, a public path (`/cover.png`) or a URL. `{ src, alt, fit, position }` works.
`imageAlt`	`''`	Alt text for the image.
`imageFit`	`cover`	How cards fit the image in their frame: `cover` crops it to fill the frame, `contain` shows all of it, letterboxed. Use `contain` for logos and diagrams.
`imagePosition`	the centre	Which part of a cropped image stays in view, as CSS `object-position`: `top`, `left`, `30% 20%`.
`author`	the `defaultAuthor` option	A name, a key from the `authors` option, `{ name, url, email }`, or a list of these.
`tags`	none	Any number of topics: a list or a comma-separated string. Shown as chips, each a filter, and written to the feed as categories. See Category or tags?.
`category`	none	The one kind of post this is, such as `Releases`. Shown above its title on cards and in its byline, each a filter. Written to the feed and `article:section`. See Category or tags?.
`scope`	`section`	`site` (or `global`) also lists the post on the main blog. See Scopes.
`pinned`	`false`	Kept at the top of its blog pages, above the paginated posts, with a Pinned badge. See Pinned posts.
`announcement`	`false`	`true`, or the banner's text, shows the post in the banner above the nav bar. See Announcements.
`draft`	`false`	Left out of lists and feeds. To leave drafts out of the build and the menus too, see Drafts.
`byline`	the `byline` option	`false` hides this post's byline.
`cover`	the `cover` option	`true` shows this post's image under its byline.
`postNav`	the `postNav` option	`false` hides this post's newer / older links, and VitePress's previous / next links come back. See Newer and older links.

Title, description, date, author, image and tags can also be written at the top level of the frontmatter, as other blog tools expect. A value under blog wins.

Category or tags?

Both sort posts, in different ways:

category is the one way you slice the blog. Each post has exactly one, from a short list that rarely changes. It is the label above the title on cards, and the first row of the browse panel. Pick the axis your readers browse by most: the kind of post (Releases, Guides, News), the team, or the product line.
tags are everything else a post is about. A post can have several, and new ones can appear at any time: the product it changes, the feature, the topic.
Don't say the same thing twice. If a post's category is Releases, a release tag adds nothing.
categories: on a blog page is a filter, not a label. blog-index: { categories: [Releases] } makes a page that lists only releases. tags: works the same way there, and both work in ::: blog-posts blocks.

This site's blog files posts by kind: every post so far is in Releases, and its tags name the plugin each one is about (blog, glossary). So all releases and everything about Glossary are two separate questions. The Browse Demo files posts by team instead (Engineering, Product, Design), with release as a tag: a different axis, the same idea.

Dates and times

date and updated take a date, or a date and a time, in any of these forms:

Written	Means
`2026-10-20`	A day. Shows "October 20, 2026".
`2026-10-20 14:30`	A day and a time, in the `timeZone` option.
`2026-10-20T14:30:00`	The same, with a `T` and seconds.
`2026-10-20T14:30:00-04:00`	An exact moment, with its offset from UTC.
`2026-10-20T18:30:00Z`	An exact moment, in UTC.

Every post on this site's blog gives its exact moment, with its offset from UTC. Introducing the Blog plugin was published, then edited later the same day, so its byline reads "Published October 20, 2026 at 2:34 PM EDT · Updated October 20, 2026 at 2:47 PM EDT":

yaml

blog:
  date: 2026-10-20T14:34:56-04:00
  updated: 2026-10-20T14:47:00-04:00

A time shows only when you give one. A date alone is shown as a date, never as "12:00 AM".
Times without an offset are in the timeZone option, UTC unless you set one, so the same frontmatter means the same moment on every build machine. This site sets timeZone: 'America/New_York' and writes New York times; daylight saving is taken care of. Dates and times are shown in that time zone too.
Posts on the same day sort by their times, and a date alone counts as the start of its day. Feeds and social tags use the exact moment.
The sidebar and navbar sort the same way. Auto Sidebar and Auto Navbar read dates with times too, so .sort: date desc puts this afternoon's post above this morning's.

Drafts

draft: true keeps a post out of blog lists, ::: blog-posts blocks and feeds, but on its own the page is still built and can be opened by its URL. With the drafts option on, drafts are listed too, with a Draft badge.

This site goes further: Exclude's excludeFrontmatter option, with blog.draft in its list, leaves drafts out of the production build, and the same option in Auto Sidebar and Auto Navbar hides them from the menus. In vitepress dev, drafts are built and listed with their badge, for preview.

Making a blog page

A page with blog-index in its frontmatter lists posts. blog-index: true is a section blog of the page's own folder:

---
title: Team A blog
blog-index:
  layout: grid
  groupBy: year
---

# Team A blog

Notes from Team A.

<!-- blog-posts -->

The list goes where  is, or after the page's content if there is no marker.

Key	Default	What it does
`scope`	`section`	`site` makes this the main blog. See Scopes.
`folders`	the page's folder	Folders to list posts from, relative to the source directory; `./` and `../` are page-relative.
`tags`	all	Only list posts with at least one of these tags.
`categories`	all	Only list posts in one of these categories.
`limit`	all	Most posts to list. The feed has its own limit.
`layout`	`list`	`list` (image beside text), `grid` (cards) or `compact` (dates and titles).
`groupBy`	none	`year` or `month` puts a heading ("2026", "October 2026") above each year's or month's posts.
`showTags`	`true`	`false` hides tag chips on cards.
`showCategory`	`true`	`false` hides the category above each card's title.
`categoryList`	`true`	A row of categories in the browse panel, each with its count. `false` leaves it out.
`categoryLimit`	`8`	Categories shown before "+N more", most used first. `0` shows them all.
`tagList`	`true`	A row of keywords in the browse panel, each with its count. `false` leaves it out.
`tagLimit`	`12`	Keywords shown before "+N more", most used first. `0` shows them all.
`tagMinCount`	`1`	Leave keywords used by fewer posts out of the browse panel. They still show on cards.
`archive`	`true`	Rows of years, and each year's months, in the browse panel. `false` leaves them out.
`pageSize`	`10` (the `pageSize` option)	Posts per page. `0` shows them all on one page.
`pinLimit`	all (the `pinLimit` option)	Most pinned posts kept at the top. Extra ones take their place by date.
`rssLink`	`true` (the `rssLink` option)	A "Subscribe" link with the RSS icon to this blog's feed. `false` leaves it out.
`feed`	on	`false` turns the feed off, or `{ title, description, limit, path }` to set it up.

Pinned posts

pinned: true keeps a post at the top of every blog page that lists it, in its own section above the other posts, with a Pinned badge. The announcement of this plugin is pinned on the blog. Pinned posts show on the first page only and don't count toward pageSize. When more posts are pinned than a page's pinLimit, the newest ones stay on top and the others take their place by date. Feeds ignore pinning and stay in date order.

Before 0.4.0, these settings were called sticky and stickyLimit. The old names are still read, so older posts keep working.

To keep pinned posts on top of the sidebar too, sort the blog folder with Auto Sidebar's .sort setting, by pinning and then date. This site's blog does:

txt

# The overview stays first; pinned posts come next, then every other post, newest first.
index.md:All posts
.sort: blog.pinned desc, date desc
# Only the 10 newest posts are listed here; the blog page has them all.
.limit: 10
# In the navbar, Blog is one link to the blog page rather than a dropdown of every post.
.link

The sidebar pins every pinned post; pinLimit applies to blog pages.

Browsing: categories, keywords and dates

Every post is written into the blog page's HTML, so search engines, local search and readers without JavaScript see them all. With useBlog() in your theme, the browser then shows one page at a time and filters the posts, all from the URL:

URL	Shows
`?page=2`	The second page. Page links are added below the posts.
`?category=product`	Posts in the `Product` category, in any case.
`?tag=release`	Posts tagged `release`, in any case.
`?year=2026`	Posts published in 2026, in the `timeZone` option.
`?month=2026-10`	Posts published in October 2026. It wins over `?year=`.
`?announcements`	Announcements only. See Announcements.

Filters combine: ?category=engineering&tag=api&year=2026 shows the engineering posts tagged api from 2026, and pages count the matching posts only. The Browse Demo has posts in three categories over two years, so you can try every filter; its Design posts tagged ux is one combined view.

The browse panel above the posts has a row each for categories, keywords and the archive, each chip with its post count. It is a flat toolbar between two rules, with the blog's "Subscribe" link at the end of its first row:

Chips combine. A chip adds its filter to the ones in view. Another chip in the same row replaces it, and clicking the active chip takes it off again.
Counts follow the view. Each count says how many posts the chip would show with the other filters kept, so readers see where a click leads. Chips that would show nothing are dimmed.
Years open into months. Choosing a year shows a row of its months below the years; with only one year, its months always show. A month keeps its year active, and clicking it again steps back out to the whole year.
It stays short with many values. Categories and keywords are ranked by how many posts use them, and a row shows its first categoryLimit (8) or tagLimit (12), then "+N more". That opens the full list alphabetically, and a row of more than 30 values also gets a field to narrow it. An active chip always shows. tagMinCount: 2 leaves out keywords used only once.
One line per row on phones. On screens narrower than 640px, each row is a single line that scrolls sideways, its end fading while there is more. Chips are 32px high on touch screens.
Rows appear only when they can narrow the posts. No categories, or one category every post is in, means no category row. That is why this site's blog, where every post so far is a release, shows only its keywords. The archive needs posts from more than one month, and with only one year, it is that year's months alone.

The active filters show above the posts while any filter is on: how many posts match, a chip for each filter that removes just that one, and "Show all posts" to clear them all. Screen readers announce the new count.

Categories and keywords are links wherever they appear: in the browse panel, on each card, and in a post's byline, where they link to the post's own blog, filtered. They are ordinary links, so VitePress follows them without reloading the page, and each filtered view has its own URL to share.

Announcements

announcement: true puts a post in a banner across the top of every page, above the nav bar: one line, the full width of the window, linked to the post. A string sets the banner's text instead of the post's title. The post announcing this feature is one.

---
blog:
  date: 2026-10-20 09:00
  announcement: Scheduled maintenance on Friday, 18:00 UTC
---

Add the banner to your theme's layout-top slot:

// .vitepress/theme/index.ts
import { h } from 'vue';
import DefaultTheme from 'vitepress/theme';
import { BlogAnnouncementBanner } from '@binarynoir/vitepress-blog/client';

export default {
  extends: DefaultTheme,
  Layout: () => h(DefaultTheme.Layout, null, { 'layout-top': () => h(BlogAnnouncementBanner) }),
};

The newest one wins. With several, the banner shows the newest and a badge with how many there are. The badge opens the blog page filtered to announcements, as in /blog/?announcements.
Visitors can clear it. The close button dismisses every current announcement, remembered in the browser. A newer one brings the banner back, counting only the ones not yet dismissed. Changing a post's date announces it again.
No jump on load. The banner is in the static HTML, and a dismissed one is hidden before the page shows. While it shows, the nav bar, sidebar and content move down to make room.

The banner's posts come from VitePress's site data, which blogVitePlugin (or withBlog) fills in.

Latest posts on any page

A ::: blog-posts block shows a blog's latest posts anywhere, with its own settings. This site's home page uses one for "Latest from the blog":

::: blog-posts
limit: 3
pinLimit: 1
layout: grid
more: Read the blog →
:::

This one, written right here, shows the Scopes Demo's Team Blog, in its own compact layout:

::: blog-posts
blog: /plugins/blog/demo/team/
limit: 2
layout: compact
more: Open the Team Blog →
:::

Key	Default	What it does
`blog`	the page's own blog	The blog to show: its URL (`/blog/`) or file (`blog/index.md`); `./` and `../` are page-relative.
`limit`	`5`	Most posts shown, pinned ones included. `0` shows them all.
`pinLimit`	the blog page's	Most pinned posts kept at the top. `0` pins them all.
`layout`	the blog page's	`list`, `grid` or `compact`.
`showTags`	the blog page's	`false` hides keyword chips.
`showCategory`	the blog page's	`false` hides the category above each title.
`tags`	all	Only show posts with at least one of these keywords.
`categories`	all	Only show posts in one of these categories.
`more`	`All posts in {blog}`	Text of the link to the blog page below the posts. `false` leaves the link out.
`rssLink`	the blog page's	A "Subscribe" link with the RSS icon to the blog's feed, beside the link to the blog page. `false` leaves it out.

Without blog, a block shows the page's own blog: the deepest section blog covering its folder, else the main blog. So on the home page it is the main blog, and on a section's page, that section's blog.
It is written into the page at build time and refreshes in vitepress dev when a post changes. A page can hold several blocks, and a block inside a code fence is left as written, as in the examples above.
A blog it can't find, or settings that aren't valid YAML, log a warning naming the page and line.

Scopes

Scopes decide which blog lists a post.

A section blog lists every post in its folder and the folders below it, whatever the post's scope. Section blogs can be nested: a post in team-a/guides/ is listed by both team-a/ and team-a/guides/.
The main blog (blog-index: { scope: site }) lists two kinds of posts:
- posts from any folder that are marked scope: site
- posts in folders that don't have a section blog of their own

So a site with only a main blog needs no scope settings at all, and a post inside a section only reaches the main blog when it says scope: site. The Scopes Demo shows all three cases live.

txt

docs/
  blog/
    index.md          blog-index: { scope: site }   lists hello, launch, notes
    hello.md          blog: true
  team-a/
    index.md          blog-index: true              lists launch, internal
    launch.md         blog: { scope: site }
    internal.md       blog: true
  notes.md            blog: true                    no section blog covers it

Newer and older links

A post's newer and older links stay within its own blog: the deepest section blog that lists it, otherwise the main blog. They are in date order, the order readers see on the blog page.

They take the place of VitePress's previous / next links at the foot of the page, which follow the sidebar instead, so a post has one set of links, not two that disagree. To change that for one post:

prev or next in its frontmatter still sets VitePress's link, as on any page, and it shows beside the newer / older links.
postNav: false hides the newer / older links, and VitePress's previous / next come back.

A post that no blog lists keeps VitePress's links, since it has no blog to link within.

When a section blog helps

A section blog is worth it whenever one part of a site has its own audience. Some realistic cases:

Release notes per product. A docs site for several products gives each one a releases/ section blog. Users of one product subscribe to its feed alone. The major releases say scope: site and also reach the main blog.
Packages in a monorepo. Each package's docs folder holds its own changelog posts, so docs/packages/cli/ and docs/packages/sdk/ each get a blog and a feed, and the main blog has the releases that affect everyone. This site could do the same for each plugin.
Teams in a handbook. An internal handbook gives each team a section blog for its updates. Company-wide announcements are marked scope: site, so the main blog is what everyone reads, and each team's page shows only its own news in a ::: blog-posts block.
Incident reviews. A postmortems/ section blog keeps every review in date order for the people who need them, while only the ones customers should know about are marked scope: site.
Courses or cohorts. A learning site gives each course its announcements: due dates, new lessons, office hours. Students follow their own course's feed, and site-wide news stays on the main blog.

In each case the posts stay next to the docs they belong to, and a reader can follow all of it on the main blog or just one section.

Feeds

Each blog page's RSS 2.0 feed is written next to it at the end of the build: news/index.md gets news/feed.xml, and news/archive.md gets news/archive-feed.xml. Set feed.path to name it yourself. A feed holds the newest 20 posts (feedLimit, or the page's feed.limit), never drafts, and each item has its title, link, date, summary, authors, tags and image.

Feeds need absolute links, so they use the siteUrl option or VitePress's sitemap.hostname. Without either, no feeds are written and the build log says so.

Every blog page and ::: blog-posts block shows a "Subscribe" link with the RSS icon to its own blog's feed, so readers can follow the whole site or just one section (rssLink: false hides it). It only appears when feeds are written, that is, with a site URL. The blog page also links its feed with <link rel="alternate">, and so does every post in the feed, so a feed reader finds it from any of them. vitepress dev serves the feeds too.

A post image given as a relative path is also copied to blog-images/ under a name made from its content, because Vite's hashed name for it isn't known until the build is done. Feeds and social cards link that copy. Public paths and URLs are linked as they are.

Options

Option	Default	What it does
`siteUrl`	`sitemap.hostname`	Absolute URL of the published site, for feeds and social tags.
`authors`	`{}`	Authors posts can name by key: `{ jane: { name, url, email } }` or `{ jane: 'Jane Doe' }`.
`defaultAuthor`	none	Author for posts that don't name one.
`locale`	`'en-US'`	Locale for dates and author lists ("Jane and Sam").
`dateFormat`	`{ dateStyle: 'long' }`	`Intl.DateTimeFormat` options for dates.
`timeFormat`	`{ hour: 'numeric', minute: '2-digit', timeZoneName: 'short' }`	`Intl.DateTimeFormat` options for times, as in "2:30 PM EDT".
`timeZone`	`'UTC'`	The IANA time zone that times without an offset are in, and that dates and times are shown in. This site uses `'America/New_York'`.
`wordsPerMinute`	`200`	For "5 min read". `0` hides reading time.
`byline`	`true`	Author, date and tags under each post's title.
`cover`	`false`	Each post's image under its byline.
`postNav`	`true`	Newer and older post links at the end of each post, in place of VitePress's previous / next links.
`drafts`	`false`	List drafts, marked. This site passes `process.env.NODE_ENV !== 'production'`: dev only.
`stripTags`	`true`	Remove Markdown Tags syntax from titles and summaries.
`feedLimit`	`20`	Most posts in each feed.
`imagesDir`	`'blog-images'`	Output folder for copied post images.
`pageSize`	`10`	Posts per page on blog pages that don't set `pageSize`. `0` turns pages off.
`pinLimit`	`0` (all)	Most pinned posts on blog pages that don't set `pinLimit`.
`rssLink`	`true`	A "Subscribe" RSS link on blog pages and blocks that don't set `rssLink`.
`labels`	English	Every word the plugin writes (`by`, `readingTime: '{n} min read'`, `postCount: '{n} posts'`, …), for translating.

Styling

The stylesheet uses VitePress's theme variables, so it follows light and dark mode. Override --vp-blog-card-bg, --vp-blog-card-border, --vp-blog-card-radius, --vp-blog-meta-color, --vp-blog-tag-bg, --vp-blog-tag-color or --vp-blog-accent to restyle it, --vp-blog-browse-bg (transparent) and --vp-blog-facet-label-width for the browse panel, and --vp-blog-announcement-height, --vp-blog-announcement-bg or --vp-blog-announcement-color for the announcement banner. Every generated element has a vp-blog- class for anything more.

Notes

Built first, enhanced after. Lists, bylines and links are Markdown written at build time, so every post is in the static HTML and in search, and links get the site's base and VitePress's dead-link check. useBlog() only hides and shows what is already there, and keeps the browse panel's links and counts in step.
Lists stay fresh in vitepress dev. Add, edit or delete a post and every blog page and post that shows it reloads.
Pages kept out of the build aren't listed, including anything an .exclude file leaves out, so a list never links to a missing page.

Auto Sidebar

Sidebar Titles Demo

Markdown Tags

Glossary Tooltips

README Index

Blog

Scopes Demo

Team Blog

Browse Demo

HTML Escape

Blog VitePress plugin markdown-it

See it live

Why this plugin

Install

Use

Wiring it by hand

Writing a post

Category or tags?

Dates and times

Drafts

Making a blog page

Pinned posts

Browsing: categories, keywords and dates

Announcements

Latest posts on any page

Scopes

Newer and older links

When a section blog helps

Feeds

Options

Styling

Notes

Sidebar Titles Demo

Scopes Demo

Team Blog

Browse Demo

Blog VitePress plugin markdown-it ​

See it live ​

Why this plugin ​

Install ​

Use ​

Wiring it by hand ​

Writing a post ​

Category or tags? ​

Dates and times ​

Drafts ​

Making a blog page ​

Pinned posts ​

Browsing: categories, keywords and dates ​

Announcements ​

Latest posts on any page ​

Scopes ​

Newer and older links ​

When a section blog helps ​

Feeds ​

Options ​

Styling ​

Notes ​

Blog VitePress plugin markdown-it

See it live

Why this plugin

Install

Use

Wiring it by hand

Writing a post

Category or tags?

Dates and times

Drafts

Making a blog page

Pinned posts

Browsing: categories, keywords and dates

Announcements

Latest posts on any page

Scopes

Newer and older links

When a section blog helps

Feeds

Options

Styling

Notes