Edwin Maldonado explores 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 consider the business, project, and technical constraints in play. You’ll go through the process of requirements gathering and information architecture design iterations.

To validate the designs, you’ll address the following topics: Reusability (the ability to reuse different pieces of content), governance (the granularity in terms of roles and permissions), fitting needs (the design solves what you want it to solve), composition (the pieces of content you need on the delivery side and if there are enough of them), and sync versus async publishing (if you need to have asynchronous publications, such as releasing content first for a region or country due to legal terms). You’ll learn by doing and get to make diagrams and mockups.