Custom collections and internal tags in Ghost
Custom collection routes group posts under dedicated URLs. Fantasma writes route definitions into routes.yaml. Which posts appear is decided in Ghost using internal tags on each post.
Why a collection URL can look empty
The usual cause is no published posts with the internal tag slug your Fantasma project documents for that collection — not a broken theme build.
What to configure where
| Piece | Where |
|---|---|
| Collection routes | Fantasma → generated routes.yaml |
| Apply routes | Ghost Admin → Settings → Labs → Routes |
| Tag posts | Ghost Admin → post editor |
Plan (Free vs Pro)
Collection templates and routing may depend on your Fantasma tier — follow tier badges in the builder. Tagging posts is always Ghost.
Steps
- In Fantasma, note the internal tag (slug) shown for the collection — posts need that tag in Ghost (for example
#your-collection-tag). - Download a new ZIP or publish, then upload
routes.yamlin Ghost Labs when routes changed. - In Ghost, add the internal tag to each post that should appear in the collection, then publish.
- Open the collection URL again.
Rules
- Two collections cannot share the same internal tag. Fantasma blocks duplicates in the builder.
- Internal tags are Ghost content, not toggles inside Fantasma’s post preview.
Troubleshooting
- Wrong or no posts: Confirm Labs has current YAML, tag spelling matches, and only one collection owns that internal tag.
- Wrong template: Compare Ghost’s route entry with the template identifiers Fantasma generated.