Most DITA implementations fail to involve an information architect early enough — or at all. Amber Swope explains the two distinct flavors of IA your implementation needs, and why the role should never be left until the end.

Most Agile teams bring in the information architect too late — and then wonder why the IA feels rushed. Amber Swope lays out a practical method for integrating IA work into product backlogs and sprints from the very beginning of a project.

Content strategists and information architects are often confused for the same role — but they're not. Amber Swope and Chris Hibbard walk through how the two disciplines work in tandem across each phase of a project, from defining success to sustaining the solution.

The terminology of information architecture and DITA can be disorienting at first. This glossary gives you clear, practical definitions of the key concepts — organized to help you build your understanding from the ground up.

DITA isn't a tool or an application — it's an architecture. Amber Swope explains what the Darwin Information Typing Architecture is, why it's built around topic types and reuse, and what it makes possible for organizations with complex content needs.

There's no shortage of information architecture resources — but knowing where to start matters. Amber Swope shares her personal recommendations for the books, courses, and communities that will actually move your IA practice forward.

The DITA ecosystem has a lot of resources — but not all of them are equally useful when you're trying to implement. Amber Swope shares her curated list of the tools, documentation, and communities she actually recommends to teams getting started.

Every enterprise promises to share content across teams — and most fail. Amber Swope explains the four things you have to get right before cross-department content sharing with DITA will actually work: goals, architecture, authoring standards, and storage.