# Find a _plugin_
Find a plugin
17 first-party plugins, by what you want to do.
Try
lay out a page Steps, tabs, disclosures and figures around what you wrote.
Callouts @mdsvex/plugin-callouts Callouts: note, tip, important, warning and caution, with a default or custom title note directive :::notewarning directive :::warning[Title]
Elements @mdsvex/plugin-elements Directives over html elements: details, accordions, keys, ruby, badges, marks, insertions and abbreviations details directive :::details[Summary]kbd directive :kbd[Ctrl]badge directive :badge[new](tone=tip)abbr directive :abbr[PFM](title=…)
Steps @mdsvex/plugin-steps Numbered steps, each heading inside a steps directive starts one steps directive :::stepsstep directive :::step[Title]
Tabs @mdsvex/plugin-tabs Tabs and code groups, each heading or code fence inside a tabs directive is a tab tabs directive :::tabstabs directive :::tabs(group=pm)
mark up text Keys, badges, marks, abbreviations and emoji inside a sentence.
Emoji @mdsvex/plugin-emoji Emoji shortcodes, :tada: becomes the emoji, with an optional accessible label :tada:
show code Code blocks with a copy button, and code groups.
Code blocks @mdsvex/plugin-code-blocks Code blocks with a copy button that announces the result, the title and the caption code block ```js title="a.js"
pictures, video and diagrams Captions, players, and diagrams drawn from text.
Diagrams @mdsvex/plugin-diagram Diagrams: mermaid fences drawn at build time by pele, or in the browser by mermaid code block ```mermaid
Embeds @mdsvex/plugin-embeds Video embeds: YouTube and Vimeo players named by their title youtube directive ::youtube[Title](id=…)vimeo directive ::vimeo[Title](id=…)
Figures @mdsvex/plugin-figures Figures: a figure directive around an image or anything else, with its caption figure directive :::figure[Caption]
link out and refer A policy for links that leave the site, and links from @user or #123.
External links @mdsvex/plugin-external-links External link policy, rel and target on every link that leaves the site link [text](https://…)
References @mdsvex/plugin-references References, links for @user, #123, owner/repo#123 and commits, and for bare urls when asked @user #123 owner/repo#45
cite and cross-reference A bibliography, and numbered figures, tables and equations.
Citations @mdsvex/plugin-citations Citations, :cite[key] from a CSL JSON bibliography and a ::bibliography that lists what a document cites cite directive :cite[key]bibliography directive ::bibliography
Numbering @mdsvex/plugin-numbering Numbering, numbered figures, tables, equations and sections, and :ref[fig:x] references that read as the number ref directive :ref[sec:id]
know each page Facts about a document for a layout or a list of posts.
Page data @mdsvex/plugin-page-data Page data, the reading time, excerpt, inferred title, edit url and last modified date of a document comment <!-- more -->heading # Title
catch broken things Warnings, or a failed build, before a reader finds them.
Link check @mdsvex/plugin-link-check Link checking, warns about #anchors and links to other documents that go nowhere link [text](#id)link [text](./page.svx#id)
Nothing fits?
Write your own
A plugin is a function that returns a bundle: the directives it owns, the components that render them, and handlers that reshape what the parser read. It adds no syntax: everything here works through directives, fences and the nodes the parser already reads.
Using plugins
The first-party plugins are packages of their own, named @mdsvex/plugin-*. Each exports a function, and what it returns goes in the plugins option, in the order they should run:
import { mdsvex } from 'mdsvex';
import { toc } from '@mdsvex/plugin-toc';
import { tabs } from '@mdsvex/plugin-tabs';
mdsvex({
heading_ids: true,
plugins: [tabs(), toc()]
});Every plugin here is read from its package: its name, what it owns and acts on, and its options with their docs. Every output is the plugin's own compile, run when the site is built, and an edited example compiles in your browser with the same plugin.