Content Management

It would be great to be able to define a data structure for storing content, where pages would be a single representation instead of a collection.

The structure would be defined in a similar syntax to models:

keystone.set(‘content', {
    home: {
        title: String,
        headerImage: Types.CloudinaryImage,
        intro: { Types.Html, wysiwyg: true }
    },
    about: {
        title: { type: String, default: 'About' },
        content: { Types.Html, wysiwyg: true }
    }
});

… then there would be an easy way to retrieve content for a particular page, something like this:

keystone.getContent(‘about’, callback);

Page content would be stored on a page-per-document basis, in a collection called app_content.

[charleslouis]

Based on @Mentioum solution, here is how we are handleling this at the moment : Disclaimer : this solution is not advanced/better, but the code example might help some people.

1 - We’ve duplicated Post.js model to create a Page.js model

2- created a dropdown with templates template: { type: Types.Select, options: 'page, about, team, contact, portfolio', default: 'page'},

3- display someField if the selected template is ‘about’ someField: { type: String, dependsOn: { template: 'about' } },

and it works 😃

Now, I’d like to have an OR operator in dependsOn: { template: 'about' }, so that I can do something like dependsOn: { template: 'about' OR 'legal' } or dependsOn: { template: 'about || legal' }

Any idea on how to make this happen ?

Thanks !

Full code example for Page.js here : https://gist.github.com/charleslouis/ff5cc15ce7d2f3aee59d

[mxstbr]

We’re closing all feature requests to keep the issue tracker unpolluted. From now on submit feature requests on productpains.com!