Papyrus keeps authoring close to regular Astro Markdown. A post stays readable as plain text, builds into a clean article page, and can expose source, share, tag, table-of-contents, and metadata features when the site enables them.

Use this page as a compact authoring reference when templating a new site. Every section below shows a Markdown feature in the same shape a real post can use.

Headings

H1 inside content

H2 inside content

H3 inside content

H4 inside content

H5 inside content

H6 inside content

Paragraph features

Normal text remains readable. Bold text, italic text, bold italic text, strikethrough text, inline code, and normal links all sit cleanly in a paragraph.

Autolinks stay visible: https://github.com/marcelofpfelix/papyrus

Escaped characters remain literal: *not italic* and `not code`.

Images

Lists

Unordered list:

• keep the site repo focused on content and configuration
• import reusable components from astro-theme-papyrus
• avoid copying a whole upstream theme into each site
• keep overrides small enough to review

Ordered list:

1. Write the post in src/content/posts.
2. Let Astro build the static route.
3. Use Papyrus layouts for repeated post UI.

Nested list:

• Theme
  • layout
  • post list
  • prose styles
• Site
  • content
  • config
  • minimal pages

Task list:

• base layout
• post layout
• search entry point
• graph view

Table

Right and center alignment:

Blockquotes

A good theme makes normal markdown readable before it adds more features.

Nested quote:

First level

Second level

GitHub alerts

Code

Inline code like pnpm build keeps paragraph line-height calm.

TypeScript with a title and highlighted lines:

import { PapyrusBaseLayout, PapyrusPostList } from "astro-theme-papyrus/components";
import { publishedPosts } from "astro-theme-papyrus/utils";

const posts = publishedPosts(await getCollection("posts"));

Rust:

#[derive(Debug, Clone)]
struct Repo {
    owner: String,
    name: String,
}

impl Repo {
    fn slug(&self) -> String {
        format!("{}/{}", self.owner, self.name)
    }
}

fn main() {
    let repo = Repo {
        owner: "marcelofpfelix".into(),
        name: "papyrus".into(),
    };

    println!("{}", repo.slug());
}

Diff with add/remove line styling:

- .papyrus-icon-button:hover {
-   background: var(--papyrus-panel);
-   border-color: var(--papyrus-accent);
- }
+ .papyrus-icon-button:hover {
+   background: transparent;
+   color: var(--papyrus-accent);
+ }

Shell:

pnpm install
pnpm build
pnpm papyrus-llms src/content/posts public "$SITE_URL"

Mermaid

Diagram source links:

Mermaid sourceOpen the Mermaid source file

PlantUML sourceOpen the PlantUML source file

Excalidraw sketchOpen the editable Excalidraw file

Link preview

Footnotes

Footnotes are useful for small asides without breaking the main flow.¹

Definition list

Papyrus : reusable layouts, components, and CSS

Site : content, config, and route composition

Details

Horizontal rule

The content after the rule stays connected to the rest of the post.

What this page shows

Public posts can double as useful documentation. Readers see how authoring features work, and maintainers get one page that covers headings, prose, images, lists, callouts, code, diagrams, artifact links, link previews, footnotes, definition lists, and raw HTML details.