The Plenti CMS is designed to work out-of-the box with zero configuration. It's a "Discoverable CMS" that reads your content source and provides a default editing experience that you can use locally or deploy to a remote site and use Continuous Integration (CI) to manage updates. You can define defaults, schemas, and components to progressively enhance your editing experience if you so choose.

Creating new content

If you want to be able to create new content through the CMS, you need to define a _defaults.json within your content type (e.g. content/pages/_defaults.json). The CMS will pick up on this and provide a new option in the admin interface under "Add" in the top navbar. The widgets provided will be based on the types of content you use for your default scaffolding, however you can override these by also defining a _schema.json file for your content type (e.g. content/pages/_schema.json).

Creating new component content

Component defaults are defined in a similar manner to content type defaults, however they must go in a special named folded called _components inside your top level content folder (e.g. content/_components/grid/_defaults.json). Components do not get their own pages/endpoints, they only exist within the context of being placed on a particular page. In order to do this, you need a content type (or another component) with a _schema.json file that specifies a component widget for one of its fields:

  "myfield": {
    "type": "component",
    "options": [