John Eckman: Structured Content in the Age of Gutenberg

One response on “John Eckman: Structured Content in the Age of Gutenberg

  1. John Eckman

Continue the discussion

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Published

October 14, 2018

Content Strategists like Karen McGrane make a distinction between CMS implementations that store content in large, unstructured “blobs” and those which store finely grained, structured “chunks.” WordPress is often accused of being on #teamblob but with appropriate use of custom post types, post meta, taxonomies, and term meta, can be an excellent example of #teamchunk.

Now enter project Gutenberg, with inline block creation, block templates, block types, shared blocks and dynamic blocks.

Is this a return to #teamblob? If you create a block for, as an example, staff profiles, will you end up with hardcoded staff phone numbers in different blocks on different pages? Will you have to rewrite the staff directory to be a dynamic block? What’s all this about storing the content as html comments?

This talk will not be a deep dive into the code of Gutenberg, but will explain how Gutenberg’s approach fits into the debate about structured content versus unstructured content, and how you can best leverage the new WordPress editor without going all blobby.

Rate this:

Event

WordCamp Boston 2018 7

Speakers

John Eckman 17

Language

English 6757

Download
MP4: Low, Med, High
OGG: Low
Subtitles
Subtitle this video →
Producer
%d bloggers like this: