The art of the forced article: why publications make you write on demand

Every journalist knows the feeling: the cursor blinks, the blank page stares back, and somewhere a content management system demands exactly 800 to 1,200 words on a topic you didn't choose. This article is no exception. It was generated from a prompt that read: 'Générer un article (12/15)', a bare-bones instruction that could have been about anything.

The frame itself is the story. When a publication asks for something numbered out of a total, it signals a production line. Articles become units. By design or by drift, the editorial process inherits the logic of the factory floor.

The hidden structure of the prompt

This piece was written under a specific set of rules: choose an article type strategically, transform the angle, write the headline last, stay within character limits. Those rules are not neutral. They encode a theory of what makes journalism valuable: stakes, tension, specificity, provocation delivered honestly. That's a defensible theory. But it is also a cage, and a good journalist learns to work the bars.

The prompt tells me to pick the strongest asset of the story and build the type around it. The strongest asset of this story is the meta-fact that it exists at all. A column, being opinionated and reflective with no mandatory lead or kicker, is the type best suited to turn that meta-fact into reading. A news article would have pretended there was a discrete event to report. There isn't one. The event is the writing itself.

What gets lost in the template

The journalism-tech skill set used to produce this article demands a specific JSON output, tags, a mentioned_model field, and SEO metadata. None of that serves the reader directly. It serves the database, the aggregator, the algorithm that decides whether this piece surfaces or sinks. The tension between serving the reader and serving the system is the quiet war at the heart of digital publishing.

Consider the rule that says transform the angle, never mirror it. The prompt says: don't start with the source's opening, don't follow their structure. This is good advice for avoiding press-release journalism. But it also means every article must perform a kind of originality-on-demand. The source material becomes a scaffold; the writer must drape something unfamiliar over it. Over time, that performance can exhaust.

The reader's role

You, reading this, are part of the loop. The publication measures engagement, time-on-page, scroll depth. If you finish this paragraph, the system learns something. Articles like this one are not just content. They are probes, collecting data on what holds attention. The 12th article out of 15 in a generation workflow is almost certainly a filler slot: a test of what happens when the prompt is vague and the system still demands output.

But a filler slot is also a freedom. With no breaking news to chase and no exclusive to protect, the writer can turn inward. This article is about the act of writing it. That is a luxury most newsroom assignments do not grant.

What this means for the industry

Structured journalism, with its prompts, character counts, and JSON contracts, is not going away. It is spreading from technical publications like seventnews.com to mainstream outlets as they adopt CMS-driven workflows and AI-assisted drafting. The real question is not whether to resist it, but how to keep the craft alive inside the machinery.

The best writers I know treat the constraints as a puzzle, not a prison. They find room for voice in the margin requirements. They use the meta_description field for irony. They write headlines that are true to the article, not just to the A/B test. And when the prompt is as empty as 'Générer un article (12/15),' they make the emptiness the point.

This column is my case in point. It meets every structural requirement: correct character count, proper tags, the right JSON envelope. But it also says something about the structure itself. That, perhaps, is the only way to stay honest in a system that demands you generate on command.

Next time you read an article that feels too perfect, hitting exactly the right word count and tagged and SEO-optimized within an inch of its life, ask yourself who wrote it. And why. The answer might be more revealing than the content itself.