As the Web matures, platforms diversify, and browsers’ capabilities leapfrog their predecessors, there is increasing interest in improving the tools used to craft content. While the product we've been building, Marquee, has been brought into the conversation from time to time, our team has made an effort to keep relatively quiet as we worked through what we thought were some fundamental structural flaws with both existing and emerging approaches.

With organizations behind web-native publications growing in both numbers and complexity, it became apparent the systems serving them were ill-suited to meet the diverse needs of their stakeholders. What was needed was a unified platform addressing the full spectrum of diverse requirements across an organization, without falling into the trap of a monolithic, one-size-fits-all approach that serves no one.

Over the last few years, we’ve built a publishing framework — a coupling of services, tools, and data — that meets the needs of publishers of any scale and helps brings long-term sustainability to web-native content.

Publishers are increasingly facing the daunting decision of how to power their future on the Web. The nature of the challenges are so important, so personal, that attempting to describe the benefits of one approach over another in an easily digestible checklist of features is almost impossible. (We know, we’ve tried.) Instead, we think the best way of understanding if a system is right for you is understanding the thought process, motivations, and philosophy behind its stewards.

What follows is an in-depth look at how the team at Marquee approached these problems, the mistakes we made, and what we've learned. It introduces you to our platform in the same way we came to understand the nature and role of our business, because we think that's the only way for you to know if we're a good choice for your project.