- The problem with static-fielded CMS's
- Intro to Drupal
- Installation
- Entities
- Bundles
- Nodes
- Content Types
- Solving the problem - Paragraphs
- Paragraph Types
- Paragraph Node Field
- Dynamic templates based on fielded data in any order
- Wrapping up
- Pre-defining all the layouts a client will need
- Strict limitations of what is developed
- Shoving everything in the body, or other predefined fields
- Enterprise level open source content management system/framework
- Built on top of Symfony components
- Highly extendable
- Can build a management system to suit the project needs
- Massive community / module ecosystem
- Clone this repo: https://github.com/johnny5th/twd-drupal
- Run
composer install
- Run
docker-compose up
- Open http://localhost
- The building blocks of Drupal
- Almost everything is an entity
- Bundles are sub-configurations of entities
- Nodes are special entities that create most of the pages on a Drupal site
- Node entity bundles are called Content Types
- They allow the creation of structured data types to hold site information displayed as individual pages
- Paragraphs gives a content writer the ability to create rich, dynamicly formatted page content without writing any HTML
- Paragraphs provides a new Paragraph Reference field to embed small Paragraph entities within the node editor interface
- Regardless of the CMS you use, this dynamic structured content, or "Content Blocks", approach is a great way to client-proof your management interfaces
- Some great CMS implementation comparisons and discussions can be found at: https://css-tricks.com/different-cmss-handle-content-blocks/