Article API Lab · Category collection

Static & distribution

Let finished articles travel cleanly.

Once an article has been approved, it may become a static page, an RSS item, or an email edition. Those outputs share a source but have different responsibilities. A static build must include complete pages and assets. A feed needs stable identity and consistent links. A newsletter needs its own editorial introduction and an explicit sending decision. This collection shows how to keep the common article record intact without pretending that every channel is interchangeable. Begin with the Hugo guide for a file-based publishing model, then read the RSS and newsletter guide to plan distribution. Review the resulting reader experience, not just whether a build command completed.

Articles in this collection.