Applying reusability on information architecture
Time & Location
About the Event
Edwin Maldonado talks about some of the ways to support pure content changes from the editorial team so you can handle broadcasts from your editors to multiple devices.
To design a reusable information architecture, you should take in consideration the business, project, and technical constraints in play. Edwin goes through the process of requirements gathering and the information architecture design iterations. To validate our designs we ask the following questions:
Reusability: How easy is it to reuse the different pieces of content?
Governance: How granular can we go in terms of roles and permissions?
Fit: Are we solving what we actually want to solve with this design?
Composition: Which pieces of content do we need to have on the delivery side? Do we have enough blocks of content in place?
Sync versus async publishing: Is there a need to have asynchronous publications? (Imagine releasing content first for a region or country due to legal terms.)
Learn by doing and make sure to bring a notebook and a pen; we’ll making diagrams and mockups.