Slugs and output filenames
What a content Slug is, the rules it follows, how Acrosite suggests one from your title, and how it becomes the published file name and your page URL.
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 on the slug line under the title in the editor. 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 — Acrosite refuses a slug that another item of the same type in the project already uses, so each item 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>.mdx # a Post
acrosite/content/pages/<slug>.mdx # a Page
acrosite/content/<type-key>/<slug>.mdx # a Custom Content Type itemSo a Post with the slug welcome becomes acrosite/content/posts/welcome.mdx with the default settings. 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 the slug of a published item changes nothing on your website until you publish again. When you do, Acrosite adds the file at the new address first and then removes the old file, but only if the old file is still the one Acrosite published. The old page stays on your website until the website is deployed again. If the old file cannot be removed safely, it stays in your repository, so the old address can keep working, and the item shows it as an old file you can remove.
Redirects from the old address, and links to it on other websites, are not updated for you. Add a redirect on your website if visitors should be sent to the new address. See Unpublish content.