The Delivery Information Architect is the person who makes sure content doesn't just exist — it works on the platform where users actually encounter it. This sample job description gives you a template for hiring or defining the role.

The Management Information Architect is the role responsible for how content is structured at its source — across all delivery channels. Amber Swope's sample job description gives you a clear, adaptable template for defining or hiring for the role.

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.

A CCMS implementation built on weak information architecture will fail. Amber Swope's readiness assessment gives you a concrete checklist of everything your IA needs to have in place before your implementation begins.

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.

Every DITA implementation reaches a point where the team has to decide: do we figure this out ourselves, or do we bring in an expert? Amber Swope breaks down exactly which tasks require outside expertise and which don't — so you don't pay twice for the same work.

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.

Most information architects didn't set out to become one. Amber Swope surveyed 35 working IAs to understand how they got there, what they actually do day to day, and what it takes to do the job well — whether you're already in the role or considering it.

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.

Not every organization needs the same level of DITA investment — but how do you know where you fall? The DITA Maturity Model by Amber Swope and Michael Priestley gives you a framework for aligning your investment in IA, technology, and process with the specific results you're trying to achieve.

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.