WPCampus: A content modeling workflow for planning custom post types

Transcript

1. A content modeling workflow
   for planning custom post types
   Amy Grace Wells
   

   View Slide

2. Why am I here?
   A little too attached to
   higher ed
   ● Positions at Ohio University,
   Texas A&M, University of South
   Carolina
   ● Master’s in Higher Education
   A little thing called UX
   ● Editorial director, UX Booth
   ● Master’s in UX Design (almost)
   @amygracewells
   

   View Slide

3. DON’T @ ME
   

   View Slide

4. Before we begin...
   

   View Slide

5. Custom post types
   solve user and author
   problems
   @amygracewells
   

   View Slide

6. Death to WYSIWYG
   @amygracewells
   

   View Slide

7. View Slide

8. Add functionality
   @amygracewells
   

   View Slide

9. View Slide

10. Create connected content
    @amygracewells
    

    View Slide

11. View Slide

12. View Slide

13. View Slide

14. View Slide

15. Connected content
    isn’t about words.
    It’s about data.
    @amygracewells
    

    View Slide

16. What does content
    first really mean?
    @amygracewells
    

    View Slide

17. Content first requires talking
    about content before
    CMS requirements,
    functionality
    visual brand standards,
    board approval, etc.
    @amygracewells
    

    View Slide

18. How it works
    CONTENT
    Identify, Understand,
    & Align
    VISUAL
    Create connections
    DEVELOPMENT
    Build connections
    @amygracewells
    

    View Slide

19. Let’s talk
    LUMEN
    h/t Kent State UXD program
    Learn
    Understand
    Imagine
    Evaluate
    Inform
    @amygracewells
    

    View Slide

20. LUMEN & Workflow
    Ask the questions
    Stakeholder interviews,
    content audits, user
    research
    Understand & map
    Identify content types
    and taxonomies, assign
    attributes
    Play with connections
    Domain and content
    model visualization
    Test & listen
    Again with
    stakeholders, assign
    priority, talk to users
    Get going
    CMS requirements,
    content spec sheets
    Learn Understand Imagine Evaluate Inform
    @amygracewells
    

    View Slide

21. Ask the questions
    Interview stakeholders who have a claim to content
    ● Individual interviews or by small department
    ● Explain what’s happening and what to expect
    File the notes for reference (because you will refer to them)
    @amygracewells
    

    View Slide

22. Ask the right
    questions
    Learn about their goals
    Their understanding of
    their audience
    How they use the website
    to provide their service
    How the website helps
    them and how it doesn’t
    @amygracewells
    

    View Slide

23. Ask the questions
    Interview users to understand their needs and priorities
    ● Use current site content to evaluate usefulness
    ● Identify user’s top tasks
    Audit what you have
    ● Leave room to assign content types
    @amygracewells
    

    View Slide

24. Understand & map
    Map the top journeys
    Task-based
    2-3 for each audience
    Meet user goals, not business goals
    @amygracewells
    

    View Slide

25. A content type is:
    Specific
    Templated
    Solves a need
    @amygracewells
    

    View Slide

26. Workshop it
    (aka post-it note time)
    Identify each content type
    Each get a post-it
    Discuss, play, move
    Stand back and observe
    @amygracewells
    

    View Slide

27. Define & Assign
    Each needs a one
    sentence definition
    Identify the attributes of
    each. What are the pieces?
    Annotate where needed
    @amygracewells
    

    View Slide

28. View Slide

29. Play with connections
    Welcome to the hardest part!
    Your task is to create a map of how the content types
    relate to each other.
    @amygracewells
    

    View Slide

30. View Slide

31. View Slide

32. Test & listen
    Explain the process and share it with stakeholders
    in a meeting. Not in an email.
    Let them try to destroy it! Let them find the missing
    connections.
    Refine your model and prioritize your build.
    @amygracewells
    

    View Slide

33. Get going
    Attributes become:
    CMS requirements for
    developers
    content spec sheets for
    authors
    @amygracewells
    

    View Slide

34. View Slide

35. View Slide

36. Take the time
    to do this so
    you can:
    Future-proof
    Adapt quickly
    Revise quickly
    Eliminate ROT
    @amygracewells
    

    View Slide

37. What does it
    take?
    Leadership that values
    the process
    Understanding that
    content is time intensive
    Patience and
    communication
    @amygracewells
    

    View Slide

38. Let me hear it
    Reach out with your ideas
    Amy Grace Wells
    I’m here to help make things
    less sticky:
    amygrace@contentandux.com
    When you’re stuck
    Let me share your successes
    (and struggles):
    amygrace@uxbooth.com
    When you want to share
    @amygracewells
    

    View Slide