Slugs and output filenames

A Slug is the short, URL-friendly identifier for a content item. Acrosite uses it as the published file name and, on most sites, as the page's URL path. Every Post, Page, and Custom Content Type item has one. This page explains the rules and how to choose a good slug.

Where the slug comes from

When you create a content item, Acrosite suggests a slug from your Title — lowercased, with spaces turned into hyphens and punctuation removed. You can edit it in the Slug field in the editor's content details. The editor's Publish Readiness checks confirm the slug is valid before review or publishing.

Slug rules

A good slug is:

• Lowercase — Acrosite normalises slugs to lowercase.
• Hyphenated — words separated by single hyphens, no spaces.
• Letters, numbers, and hyphens only — no punctuation, accents, or symbols.
• Unique within its content type — two items of the same type should not share a slug, so each publishes to its own file.
• Stable — once an item is published and linked from elsewhere, changing the slug changes its file name and URL.

Keep slugs short and readable. pricing is better than our-2026-pricing-and-plans-page.

How the slug becomes a file

When an item publishes, Acrosite writes it as a Markdown file named after the slug, inside the content type's folder:

acrosite/content/posts/<slug>.md       # a Post
acrosite/content/pages/<slug>.md       # a Page
acrosite/content/<type-key>/<slug>.md  # a Custom Content Type item

So a Post with the slug welcome becomes acrosite/content/posts/welcome.md. The slug is also written into the item's frontmatter — see Generated Markdown and frontmatter.

Changing a slug

You can change a slug while drafting with no consequences. After an item is published, treat the slug as part of its address: changing it produces a new file and a new URL, and the old URL may 404 unless your site adds a redirect. Change published slugs deliberately.

Next steps

• Create a Post
• Generated Markdown and frontmatter
• Acrosite-managed content paths