Upgrade to Pro — share decks privately, control downloads, hide ads and more …

[Contentful Essentials] Content modeling

Contentful Webinars
April 03, 2019
250

[Contentful Essentials] Content modeling

Contentful Webinars

April 03, 2019
Tweet

Transcript

  1. Housekeeping • This webinar is being recorded; we will share

    the recording and slide deck with all registrants • Please leave your questions in the Q&A box, we’ll answer them after the presentation • To get in touch, write to us at [email protected] before we begin...
  2. 3 1. Core content modeling concepts 2. Reusable content and

    “assemblies” 3. Inheritance and metadata 4. EXAMPLE: Content modeling for localization Topics
  3. Basic Contentful architecture Developers work in code... 5 Authors work

    in the web app... All content goes to the same place... ...and is delivered to any platform!
  4. Contentful Domain Model Organizations Top most parent object, connects users

    to a company. Users A User can have access to all or limited access to certain spaces based on roles & permissions. Spaces A child entity of an organization. A container for content, assets and UI extensions. Environments Are entities belonging to a space, they contain an isolated copy of content and assets. Implications for content modeling 6
  5. What should you store in Contentful? Content • Text •

    Images • Audio/Video Micro-Copy • Field labels & disclaimers • Navigation Localized Content • Localization strategies • Translation permissions/workflows Content Metadata • SEO & Social Media • Images as content types • Tags for navigating the content model Process Metadata • Site functionality (sort, search, etc.) • Editorial workflow • Webhooks Content Modules (“Assemblies”) • Atomic design – chunks not blobs • Giving content creators control over layout • Visual design systems 7
  6. Contentful Content Modeling Methodology Create a Pool of Sample Designs

    • Conduct an audit of existing content • Create prototypes of future content • Assemble screen shots into a slide deck Create a draft model based on visible fields • Create a list of visible fields from instances of each content type • Reconcile similar fields to create a master list • Group fields into content types of appropriate size & define relationships Revise model for functionality & best practices • Add invisible “meta” fields (for queries, workflow, webhooks, etc.) • Optimize for content creators • Optimize for developers • Implement naming conventions QA: Validate with actual content • Try to “break” the content model by using it to build diverse instances or real world content Test with Content Creators • Watch authors use the content model (usability test) • Create documentation, help and job aids Test with Developers • Have developers QA the model against front-end, migration scripts, etc. Test with Designers • Have designers test the content model by creating a variety of designs Assemble key stakeholders to define strategy • Clarify business objectives • Agree on required functionality • Make strategic content architecture decisions STEP 1 STEP 2 STEP 3 STEP 4 STEP 5 STEP 6 STEP 7 STEP 8 9
  7. Shared + independent fields 16 Product Name Manufacturer Color Product

    Type (reference) Shoe Size Sole type Heel type Pants Waist Length Type (formal, casual) Shirt Sleeve length Collar Fabric weight You can add or change fields for every product without duplicating the change for every product type
  8. Field level localization vs entry level localization Title Text (FR)

    Field Level Localization Entry Level Localization using Localization Objects Title Slug Text (EN) Text (FR) ... Title Slug Ref 1 Ref 2 ... Title Text (EN) 18
  9. The field Localized is an array that contains an entry

    for each locale Entry level localization - two content types 19 1 2
  10. Questions? Topics covered 1. Core content modeling concepts 2. Reusable

    content and “assemblies” 3. Inheritance and metadata 4. EXAMPLE: Content modeling for localization