CloudCannon

Content management Git-based.

Not available in production Maintained CMS Beta

Warning: Not supported features

  • i18n structure
  • Map Widget

Enable CloudCannon

/config/_default/params.yaml

admin:
  cms: cloudcannon

Build config file

Build a cloudcannon.config.yml file with Hugo and NodeJS script. This file needs to be versioned.

yarn build:config:cloudcannon

The script builds the site, copies /public/admin/config.yml to cloudcannon.config.yml, and writes one archetype per collection in /archetypes/, from /public/admin/config/archetypes.json, so a new entry starts with the fields of its collection.

It ships with the GitHub template . Elsewhere, copy the scripts folder of hugolify-admin to your project and add the command to package.json:

"scripts": {
  "build:config:cloudcannon": "node scripts/build-config-cloudcannon.js"
}

Group collections

Each group needs a heading, and '*' stands for every enabled collection that no group names. The same setting orders the collections of the other CMS.

/config/_default/params.yaml

admin:
  collection_groups:
    - heading: Posts
      collections:
        - posts
        - posts_categories
        - posts_tags
    - heading: Other
      collections: ['*']
See order and group collections

Card preview collections

The card of an entry reads the options the other CMS share:

CardOptionDefault
textsummary, written as a CloudCannon templatetitle
subtextNonedescription
gallery.imagethumbnailimage.src

card_preview replaces any part of the card, in the CloudCannon preview format. It is the only way to set the subtext, the metadata or the icon, which no other CMS has:

/config/_default/params.yaml

admin:
  collections:
    persons:
      card_preview:
        subtext:
          - key: persons_statutes
          - key: persons_expertises
          - key: description

Documentation