$work/skShubhra Krishan

One content model feeding a site, a newsletter and print

Long-form editorial modelled as data, so the same writing reaches three surfaces without being rewritten for each.

Shubhra Krishan — hero image
ClientShubhra KrishanIndustryMedia & PublishingOutcomeStructureYear2024
At a glanceThe same essays were being reformatted by hand for web, newsletter and printModelled as structured content, each surface now reads the same sourceEditing happens once, in a studio built around how the writing actually works
TBCSurfaces from one content model

Objective

Long-form work was being manually reshaped for each channel, which cost time and introduced drift between versions.

The requirement was one source of truth with surface-appropriate rendering, not three copies.

Objective image A
Objective image B

Solution

Content is modelled as data with structure that reflects the writing — sections, pull quotes, references — rather than as page markup.

The studio is built around the editorial workflow: custom inputs, validation that prevents bad entries, and preview of the real surface.

Newsletter and print templates read the same model, so a correction propagates rather than being reapplied.

Solution image A
Solution image B

Outcome

TBCSurfaces from one modelTBCTime to publish across channelsTBCDuplicate copies of an essay

A piece is written and edited once. Web, newsletter and print render it differently from the same data, and a correction lands everywhere.

Because the studio was built around the workflow, it is used without help.

What’s next

An archive search over the structured content, and audio versions read from the same model.

I write it once. That is the whole point.Shubhra KrishanAuthor
Quote or film still