{"componentChunkName":"component---src-templates-blog-post-js","path":"/bolt-content-and-relations/","result":{"data":{"site":{"siteMetadata":{"title":"Undefined","author":"Anirudh Varma"}},"markdownRemark":{"id":"2845cef4-50a1-5080-a32e-9d14c64aebb8","excerpt":"For a recent website project, I decided to use Bolt CMS, a\nfree and open source content management system that is really powerful while\nbeing flexible and easy…","html":"

For a recent website project, I decided to use Bolt CMS, a\nfree and open source content management system that is really powerful while\nbeing flexible and easy to use. One concept that I really liked was that of\nContentTypes,

\n

From the documentation —

\n
\n

Most websites will also have some form of news-like items, that are shown based\non the date that they were published. Some other sites might have ‘book reviews’\nor ‘event dates’ or even completely different content. All of these different\ntypes of content are called ContentTypes in Bolt, and you can add as many\ndifferent ContentTypes as you need.\nEach ContentType is made up of Fields….

\n
\n

Our project was a dance company site, so we defined the following Content Types\n—

\n
    \n
  1. Team Members.
    2. \n
  2. Videos
    3. \n
  3. Series (Collection of Videos)
    4. \n
\n

In Bolt, all contenttypes are defined in contenttypes.yml. Here is what a\nsample contenttype looks like —

\n

This is pretty similar to creating a database table with the fields title,\ndescription, frameUrl & type. The recordtemplate_ indicates the twig template\nto be used when the page for this content type is rendered.

\n

Relations

\n

Your database has relations, so it would be amazing if your contenttypes had\nrelations, right? Bolt supports creating Relationships between your content\ntypes and it is pretty straight forward. Here is the Series contenttype —

\n

Now, as I mentioned earlier. Series is a collection of Videos. The key here is\nrelations configuration. The works field maps series to the works contenttype.
Multiple — true means that multiple *works *records can be\nassociated to one series record.

\n\n

Here is how to list all related records in twig templates.

\n

Here, the record refers to the current series.

\n

You can read more about relationships here —\nhttps://docs.bolt.cm/3.4/contenttypes/relationships#

\n

About relations in templates —\nhttps://docs.bolt.cm/3.4/contenttypes/relationships#relations-in-templates

\n

This is the first project that I have developed with Bolt CMS and really liked\nworking with it so far, the extension ecosystem looks healthy and the future\nlooks promising.

","frontmatter":{"title":"Bolt CMS: Using content types and relations","date":"December 18, 2017","ogimage":null}}},"pageContext":{"slug":"/bolt-content-and-relations/","previous":{"fields":{"slug":"/react-redux-setup/"},"frontmatter":{"title":"Dev Diary: My React, Redux & React Router Setup."}},"next":{"fields":{"slug":"/angular-structural-vs-attribute-directives/"},"frontmatter":{"title":"Strucural vs Attribute Directives in Angular"}}}},"staticQueryHashes":["426816048","983108779"]}