← Blog

Olivia Morgan

Olivia Morgan is a logistics consultant and author, specializing in sustainable logistics and green supply chain practices. With a background in environmental science and a passion for driving eco-friendly solutions, Olivia helps organizations navigate the complex landscape of sustainable logistics. Olivia is a part time blogger for Apidoke Blog where she offers a comprehensive guide on reducing carbon emissions, optimizing transportation routes, implementing reverse logistics programs, and integrating environmental considerations into procurement and packaging strategies. Olivia's expertise helps businesses align their logistics operations with sustainability goals and create a positive impact on the environment.

Articles by Olivia Morgan

How to Use Apidoke's Version History Feature

How to Use Apidoke's Version History Feature

Apidoke stores a complete version history for every API documentation project you create. This step-by-step guide shows you how to save snapshots, compare changes, restore a previous version, and publish the right snapshot to your readers.

Building an API Documentation Team: Roles, Skills, and Workflow

Building an API Documentation Team: Roles, Skills, and Workflow

Engineering managers and developer relations leads often discover too late that good API docs need deliberate ownership. This guide covers which roles to hire, how to divide work between product and engineering, and how to build a workflow that survives team turnover.

API Changelog Best Practices: A Structured Guide for API Teams

API Changelog Best Practices: A Structured Guide for API Teams

A practical, structured guide to API changelog best practices, covering semantic versioning alignment, breaking change notation, communication cadence, and tying each changelog entry to a versioned reference doc.

How to Write API Release Notes That Developers Read

How to Write API Release Notes That Developers Read

Good API release notes are short, specific, and honest about what changed and why it matters. This guide covers tone, structure, breaking-change communication, and how to publish polished notes alongside your live API docs.

How to Structure a Large API Documentation Site

How to Structure a Large API Documentation Site

As your API surface grows, a flat list of endpoints stops working. This guide covers proven information architecture patterns for large API documentation sites, including how to use API Blueprint groups, resource naming conventions, and navigation hierarchy to keep developers oriented.

API Documentation Review Checklist for Teams

API Documentation Review Checklist for Teams

A structured API documentation review process reduces errors, aligns reviewers, and keeps your published reference trustworthy. This guide covers roles, feedback frameworks, async tooling, and how Apidoke's version history supports audit trails across review cycles.

How to Write API Documentation for Multiple Audiences

How to Write API Documentation for Multiple Audiences

One API, three audiences, one doc site. This guide shows you how to plan navigation, content depth, and structure so developers, partners, and internal teams each find exactly what they need.

Hosted API Documentation: Pros, Cons, and How to Choose

Hosted API Documentation: Pros, Cons, and How to Choose

Fully hosted API documentation tools get you live fast, but they come with tradeoffs around data control, pricing, and lock-in. This guide breaks down every angle so you can choose with confidence.

Developer Experience: A Practical Guide for API Teams

Developer Experience: A Practical Guide for API Teams

Developer experience shapes whether an API gets adopted or abandoned. This guide covers the signals that matter, the documentation practices that move the needle, and how Apidoke fits into a DX workflow without adding toolchain weight.

Writing a Good API Changelog

Writing a Good API Changelog

An API changelog done well reduces support tickets, builds trust with developers, and makes version upgrades predictable. This guide covers structure, tone, and the tooling that keeps your changelog honest.

What Makes API Docs Interactive (Try-It Consoles Explained)

What Makes API Docs Interactive (Try-It Consoles Explained)

Interactive API docs let developers send real HTTP requests directly from the documentation page. This article breaks down how try-it consoles work, what separates them from static references, and how Apidoke builds one in by default.

What Is API Blueprint? (Complete Guide)

What Is API Blueprint? (Complete Guide)

API Blueprint is an open-source, Markdown-based format for describing REST APIs. This guide covers the syntax, real examples, how it compares to OpenAPI, and how Apidoke turns your Blueprint files into a live, interactive reference without any build toolchain.