Search
Search
Open-source content management Git-based (GitHub only).
Available in production Maintened CMS Compatibility WIP
/config/_default/params.yaml
admin:
cms: pagescms
Build a .pages.yml file with Hugo and NodeJS script. This file needs to be versioned.
yarn build:config:pagescms
With media from Pages CMS, you can configure how to handle files you want to upload, attach to or embed in your content.
/config/_default/params.yaml
admin:
media:
audio_folders: true
pdf_folders: true
video_folders: true
Hugolify hides the Pages CMS settings page, so editors cannot change .pages.yml from the interface. Show it again with:
/config/_default/params.yaml
admin:
settings:
hide: false
Hugolify builds the view of each collection from the options the other CMS read too. There is no view param any more.
| Option | view key |
|---|---|
summary_fields | fields, with summary written title |
sortable_fields | sort, and default for the field sorting by default |
nested of 2 and up | layout: tree, each _index.md standing for its folder |
admin:
collections:
posts:
summary_fields: [title, date, draft]
sortable_fields:
- field: date
default_sort: desc
- title
Pages CMS cannot filter entries on a field value, as filter does elsewhere. Leave files out of a collection by name instead:
/config/_default/params.yaml
admin:
collections:
posts:
exclude: [_index.md]
The name is compared at every level of the folder: in a nested collection, whose pages are all _index.md files, excluding it would hide every page.
The rich-text editor has its own Editor / Source switch, so the minimal, modes and buttons params of the markdown fields do not apply. See Markdown editor.