You’re in it. Development has begun. You’re building out content types, sorting out view modes. But wait. You have a LOT of questions for your designer. Do we really need these two components that are nearly identical? From where does this component pull data? Is this populated manually or dynamically? Why wasn’t this all documented earlier?!
During this talk, I’ll show how designers can help their developers sooner. It starts with a robust content model, plus components and content view modes definition. And how developers can get clarity in the design phase, way before getting to code.
During this session, you’ll learn:
- How a content model can be a tool for developers and designers;
- How to define content view modes in a content model;
- How to collaborate with the full team earlier on in the process for fewer unknowns and better outcomes.
By the end, you’ll have a new method to achieve more efficiency in your development process; reduce friction in the design to development handoff; and speak the same language among the full team.