socketwench.github.io/introToContentTypes
Owww...
Content could be a page, but didn't have to be
Manage > Structure > Content Types
A unique Machine Name
A required Title field
A default Body field
Multi-line, WYSIWYG text field
Optional in Drupal 8
Required in Drupal 7 (kinda)
Grant create, edit, delete to user roles
Manage > People > "Permissions" Tab
Not exhaustive, select representative content
Create mock content if you don't have any
Lots of different ways to do this
Card Sorting by Donna Spencer
Have you heard this before?
Body field isn't flexable enough for different targets
Formatting baked in once and forever
Stuck in a cycle of zoom, scroll, repeat
Squeezes desktop-sized content into a tiny screen
Callouts, embedded media, pagination
Real AI Based on the Human Brain
Real AI Based...
Real AI Based on the...
Real AI Based on the Human...
Separate processes, standards, and staff
Works only as a stop gap
No matter the WYSIWYG buttons or smart tags you use
It's the junk drawer of content
You can't recombine pieces of content later
Does not bake-in formatting
Provides front-ends with what they need
Chunky fields, not blobby bodies
Manage > Structure > Content Types > Click "Manage Fields"
Fields exist independently of content types
Some performance advantages
It's exactly the same across content types
It's settings will never change, no matter the type
Requirements change as your site evolves
Performance gains negated easily elsewhere
Field may already be provided by core
Many OotB field types in Drupal 8
Extend Drupal's functionality
"There's a module for that."
https://www.drupal.org/download
Browse by most installed, or by category (recommended)
File and Image fields OotB
Media Module for D7
Media in Drupal 8, Tomorrow, 3:45pm ITTC #134
drush en -y <module_name>
It's bad for bodies, and fields too.
Our fields need to be flexible!
It's packages of content
Bundles field groups with business rules
Some "fields" are actually content by themselves!
Bundle up multiple fields, and content types
Easier to manage, harder to compose
Entity/Node Reference field type
Blocks
Panels and Panelizer (Drupal 7)
Entity Embed (Drupal 8)
Multiplies work, only a stop gap solution
Limits adaptability and remixing
Content Strategy for Moble by Karen McGrane
The Battle for the Body Field by Jeff Eaton
Card Sorting by Donna Spencer
socketwench.github.io/introToContentTypes
Background by Artwyrd