Combines with Input Plugins to create Content Types in the Punchcard CMS
npm install punchcard-content-types --saveContent Types are defined as YAML files. They include a name, a description, and an array of attributes describing which Input Plugins should be used and configured. By default, content types will be looked for in the content-types directory from the current running process. If using the config module, contentTypes.directory can be set to the path being used, again relative to the directory of the current running process.
name: My Awesome Content Type
description: I'm making an awesome new content type!
identifier: favorite-ranger
workflow: self-publish
attributes:
- type: text
id: favorite-ranger
name: Favorite Power Ranger
description: This is my favorite power ranger
inputs:
text:
placeholder: I like the Green Ranger
- type: select
id: favorite-ice-cream
name: Favorite Ice Cream
inputs:
select:
options:
- Chocolate
- Vanilla
- Strawberry
required: publish
- type: email
id: my-email
name: Email Address of Awesome
repeatable:
min: 2
max: 4There are three ways to retrieve content types; you can retrieve the raw content type definitions, the content type definitions with their input plugins merged together with the definition's settings, and a single content type that has been merged. The later will also allow you to pass in configuration from your application to merge with the definition, allowing, for instance, the value of a given input plugin to be added.
All methods return a Promise.
Will return an Array of content type definitions, each being an Object. There are no parameters to pass in.
const contentTypes = require('punchcard-content-types');
contentTypes.raw().then(types => {
// Raw Content Types
console.log(types);
});Will return an Array of content type definitions, each being an Object, with attributes replaced by individual Input Plugin instances that have been merged with the raw content type options. There are no parameters to pass in.
const contentTypes = require('punchcard-content-types');
contentTypes().then(types => {
// Merged Content Types
console.log(types);
});Will return an Array of content type definitions (that contains only one content type), each being an Object, with attributes replaced by individual Input Plugin instances that have been merged with the raw content type options. There are no parameters to pass in.
const contentTypes = require('punchcard-content-types');
const fooContentObj = {
'name': 'FooRific',
'description': 'A very foo content model.',
'attributes': [
{
'type': 'email',
'id': 'email',
'name': 'Email',
'description': 'Your email is your username',
},
],
};
// Content Type object must be an array
contentTypes([fooContentObj]).then(types => {
// Array with one Content Type
console.log(types);
});Will return an Object of a single merged content type, optionally with userland config that will be merged on top of the merged content type. Users may choose to pass in the Array of merged content types in for it to work with, or have it load and merge content types itself.
typeRequired -idname of content type to be retrieved.config-Objectwith keys matching input pluginidfrom content type definitions, values being object containing the keys frominputsand values being object to be merged.loadedTypes-Arrayof loaded, merged content types
const contentTypes = require('punchcard-content-types');
const config = {
'favorite-ice-cream': {
select: {
value: 'Vanilla'
}
}
}
contentTypes.only('my-awesome-content-type', config).then(types => {
// Single Content Type
console.log(types);
});cont content = require('punchcard-content-types');
content.only('my-awesome-content-type').then(type => {
return content.form(type);
}).then(form => {
// use form object within your html to create a content type form (see below)
});<form action="{{action}}" method="post" enctype="multipart/form-data" novalidate>
{{form.html | safe}}
<button type="submit">Submit</button>
<button type="cancel">Cancel</button>
</form>
<script>
{{form.scripts | safe}}
</script>form.html // string of wrapped form elements; should be placed inside a <form> tag
form.script // Validation and UX scripts, wrapped for browser via browserify