O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a navegar o site, você aceita o uso de cookies. Leia nosso Contrato do Usuário e nossa Política de Privacidade.
O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a utilizar o site, você aceita o uso de cookies. Leia nossa Política de Privacidade e nosso Contrato do Usuário para obter mais detalhes.
Slides from my talk at WordCamp Miami 2019. A review of my proposed process for WordPress product and service providers to begin adopting Gutenberg as part of their WordPress content and development workflow.
Content Architecture is:
● Strategy & Planning BEFORE touching WordPress!
● Data and Content Modeling: Information Architecture
● Content Reuse (instead of duplicating in multiple places!)
● Editorial Workflow & Author Experience (AX)
(the WordPress site you create is the end tool someone has to
use to do their job!)
● Scalability (what will our content need to do in the future?)
A System for Building
Great Content Architectures
+ An enhanced Discovery Process
+ The Content Model
+ WP Architecture
… UI design
+ Author & Content Stress Test
… development, etc
What does this involve?
Enhanced discovery process
We have opportunities here to add much more value to the project!
Content sharing (DRY!)
Identify painpoints and places to improve, speed up, accommodate or automate:
Editorial workflow & publishing governance
Do they CREATE content in WP, or create it
elsewhere and paste into WP after it's
Where should we use structured content,
where can we use freeflowing content?
What is the mental state of the author when
they're doing this: will they have the capacity
for the extra cognitive load of Gutenberg?
Do they have the design skills to make page
level content decisions?
Technical level of author
Do they need flexibility of adding a structured
component anyplace in a post?
Do they need global shared content?
What other channels does this website content
feed out to, what is the
What is the balance between guided & locked
down editorial vs free flowing access to
everything incl plugin installs & gutenberg
Role and privileges of author
Longterm goals for the site: scaling? sharing to
app? integrating with something else?
The Content Model
We have opportunities here to add many more value$ to the project!
Channels: here or there?
What content do you need and why? How is it all related?
Governance & Editorial Workflow
Who are your content creators & their technical abilities?
What are their roles?
What are the access limitations?
What is their editorial workflow? Can we do it in WordPress?
Will they be creating content inside WordPress, or creating outside
and pasting it in?
Is the author allowed to delete pages? Publish? Do they need signoff?
What does the content look like?
Where does it come from?
Is it structured & formatted (aka you can upload &
Similar design styles: your modules
WHY start content entry so early??
Does the ACTUAL content fit the molds you’ve made?
Go through the author process with the actual authors. What is
confusing? Where do they struggle? Listen to their feedback.
Is the client unable to produce any content? There may be issues
getting it from them by the due date. Help coordinate. Maybe an
Edit & revise early!
Catch content structure problems before they become PROBLEMS
Understanding Content Types
Good WP 5 Architecture starts with a good understanding of WordPress
Posts & Post Types
What are we working with? First we must understand WordPress.
● The_content is actually structured now (really).
● Things we used to use multiple queries to post meta are now
available right inside the content.
● We can define blocks.
● We can share blocks (global content!)
● We can create custom blocks.
● We can create templates.
● We can lock blocks and templates and remove attributes and
override style defaults.
● We can give our users the ability to create that rich, longform content
that Google loves and delights people and wins awards and stuff.
We’re overwhelmed, confused,
unprepared, and resentful.
So we’re not using it.
And we’re letting WordPress happen
● We need more legacy users &
devs using Gutenberg.
● We need more devs talking
about building with Gutenberg.
● We need more of our peers
talking about successes and
failures with it.
Here’s what we need to do.
● We need documentation THAT’S NOT
DEVELOPERS: we need to understand
content types, we need to learn
content modeling (deeply), we need to
redefine roles of the tools and
processes and artifacts we work with
daily to structure, style and manage
We need to start shaping how this new paradigm plays out.
Here’s my idea on how to get started:
Block Editor Stories Podcast
WordPress Content Architecture Initiative
● Content Modeling resources & education
● Education on WP content types - for everyone
● Exploring and defining new roles
● Establishing and documenting new patterns for content,
display and development.
We are WordPress.
All of us.
Let’s own this new paradigm. Together
we will work to shape the future of the
Please join me!
Block Editor Stories Podcast: production help, hosts,
people to interview, stories to tell and problems to discuss
I am also looking for people to help me build, refine and
present the WP Content Architecture Initiative!