Calypso, the REST API, and WordPress's JavaScript Tell

Platform strategy is usually inferred. Now and then it is performed. WordPress performed twice in six weeks this quarter, and the pair, read together, is the year’s clearest platform tell.

First, in late November, Automattic unveiled Calypso. The WordPress.com interface, rebuilt from scratch as a JavaScript application. React, as it happens, for readers of our March position. It talks to WordPress purely through APIs, and it shipped as an open-source codebase and a desktop app. The PHP that renders WordPress’s admin is nowhere in it. Calypso treats WordPress as a service and builds the experience in the browser’s language.

Second, WordPress 4.4 arrived December 8 carrying, among its features, the REST API’s plumbing into core. This is the first phase of the project that will eventually let any WordPress site speak JSON natively.

And at the community’s flagship conference between the two, Matt Mullenweg compressed the strategy into four words that have already become the ecosystem’s homework assignment: learn JavaScript, deeply. That is not a hint. That is a roadmap, delivered from the stage, and our job is reading it for the planning horizons institutions actually hold.

What the tell actually says

Assemble the three exhibits and the trajectory reads cleanly. The PHP-rendered CMS is growing an API-first personality. The platform’s next era treats WordPress’s core as a content and application service. Experiences, admin interfaces first, front ends increasingly, are free to be JavaScript applications consuming it.

Calypso is the existence proof at production scale. The world’s largest WordPress property now runs its daily editorial experience through the API. That retires the question of whether the architecture works, and replaces it with the questions of when and for whom.

The 4.4 infrastructure landing is the open-source half of the same motion, deliberately staged. Plumbing now, content endpoints in a future release. That is the project’s long-practiced absorption pattern. Capabilities proven in the ecosystem migrate into core in digestible steps, compatibility preserved throughout.

And the ‘learn JavaScript, deeply’ directive is the labor-market half. It is aimed at a developer base whose PHP fluency built the platform, and whose next decade, the leadership is saying plainly, requires the second language. Our own team’s training budget heard it. As with the React and Drupal retooling before it, the shops that move early on platform-announced skill shifts hire easier and bid stronger for years.

What it changes for platform decisions

• The decoupling file gains a credible candidate. April’s headless review scored WordPress’s API story as maturing-but-plugin-phase. Core plumbing moves it a full grade. When the content endpoints land, every WordPress site becomes an API-capable content platform by default. The verdict-by-fit framework is unchanged. The re-purchase list still governs, and the marketing-site majority still belongs coupled or progressively decoupled. But the platform column of the worksheet just strengthened, and the hybrid patterns already common in the field get a native base.

• The platform-selection file notes the stability during change. The detail worth admiring, and the one enterprise evaluators should weight: nothing about this transition breaks existing sites. 4.4’s other features ship alongside the API plumbing in an ordinary, absorbable release. Among them: native responsive images in core, incidentally finishing the srcset work our performance series celebrated last year, now default for a quarter of the web. The platform is modernizing beneath stable ground, which is the maturity pattern we praise wherever it appears. The contrast with big-bang replatformings is the argument.

• The prediction file takes a wager. Per custom, dated and checkable. We expect the content endpoints in core within the coming year. A first wave of decoupled-WordPress projects, some excellent, many premature, to follow at once. And the durable pattern to be the hybrid one already visible. WordPress-rendered sites with API-fed apps embedded where interactivity earns them, per the React deployment line. The all-JavaScript front end for content sites remains, at 2015’s tooling, a trade our SEO and performance practices price against. That line moves when server-side rendering of JavaScript apps becomes routine rather than pioneering. Not before.

What Calypso quietly demonstrates about editorial experience

One reading of the quarter deserves its own paragraph, because it belongs to a story we have covered since the 2.7 admin redesign. Calypso is, before anything else, an editorial experience statement.

Automattic rebuilt the daily writing and management surface for speed and fluidity. Instant navigation. Live previews. The responsiveness the JavaScript application model exists to buy. Why? Because the editing experience is the product that keeps publishers, and the adoption lesson we have argued at every tier says systems people enjoy get used.

The competitive implication reaches past WordPress. The bar for what content teams expect their tools to feel like just moved, at the scale of the web’s largest publishing platform. Every CMS evaluation we run next year will happen in front of stakeholders who have, somewhere, felt an interface that fast.

The enterprise tier’s authoring investments and the open platforms’ admin roadmaps are all now racing the same expectation. For the buyers in our readership, the practical takeaway is a new reference point for the editorial-experience weighting our platform worksheet has always carried. When the demo feels sluggish against the year’s best, that is no longer a matter of taste. It is a preview of your team’s daily adoption battle.

The architecture headlines belong to the API. The retention story, as ever, belongs to the people at the keyboard.

The year’s last post

For site owners, the reassuring translation of a strategic quarter: no action required, and that is the point worth savoring. The platform carrying a quarter of the web just showed exactly where it is going. It staged the transition in compatible steps and told its ecosystem which skills to build. All without breaking a single existing site.

That is how infrastructure should announce its future. The believe-the-announcements lesson applies in its gentlest form. The calendar here is measured in years. The prep is fluency rather than fixes. The organizations that simply keep their sites current will arrive at the API era without having scheduled a thing.

As an end to 2015, the tell makes a fitting final post. This was the year mobile passed desktop, the protocol modernized, and both major open platforms shipped their next architectures. The web’s platforms are converging on components, APIs, and JavaScript. From every direction at once. Exactly as the year’s files kept recording.

The 2016 assignments write themselves. We turn ten this spring, and we will be here checking them. Learn JavaScript, deeply. Keep the fundamentals, permanently. See you in January.