Use content where it belongs. Keep control where it matters.

Petra Hasenau
09/17/2026

Sometimes the most innocent little request starts it all. There is a contact block that already works perfectly: right person, right number, right wording. Then another page needs exactly the same thing. Easy enough. Copy it over. And for a while, that feels perfectly sensible.

Until the website grows, the useful little block appears in a few more places, and one day somebody changes a phone number in one version but not the others. Suddenly the question is no longer where the content should appear, but which version we can actually trust? And that is where things get interesting.

Because the same content can be useful in several places, handled by different people, and used inside different structures.

Sounds like a lot to keep aligned? It can be. And that is exactly where the fun starts.

Estimated time to read: 5 minutes

Same content, another place

A new placement does not need a new instance.

Our contact block is still perfectly happy where it is. Nothing about its content has changed. We simply need it somewhere else as well.

TYPO3 already comes with a rather underestimated tool for exactly that: the shortcut content element. Technically, a shortcut is a new instance, but it is a placement instance, not another instance of the content itself. It carries no content of its own. Its job is to place existing content somewhere else.

That makes it a structural element, almost like a very simple grouping container that can be placed wherever it is needed.

Grid Elements brings this directly into the editorial workflow with Paste as Reference. An editor can put an existing content element on the clipboard and, when placing it somewhere else, choose whether to move it, create a copy or paste it as a reference to the original. In that case, Grid Elements creates a shortcut for the new placement.

And it takes this TYPO3 core feature much further by making those references visible where editors actually work with the structure. Instead of dealing with an almost invisible pointer, they can see the referenced content in its new place and use it as a natural part of the page layout. The content stays where it is maintained. Grid Elements gives it another place in the structure and turns a modest shortcut into a genuinely useful part of Structure-first Authoring. And once another place enters the story, context is never far behind.

Same content, another context

A new placement can assign a different role.

Remember our clones? We have already seen that a card, a teaser or a slider item does not automatically need its own Content-Type just because it appears in a different context. The surrounding structure can give the same kind of content a different role.

And of course, that idea works with shortcuts too.

Imagine a profile that is maintained centrally: photo, name, description and contact details. That information only needs to be maintained once, even if it is useful in many places.

A shortcut can bring exactly that content into another structure, where the surrounding Grid Element provides the context. Here it may become a card, somewhere else a teaser, and in another place perhaps an item in a carousel.

The content itself stays the same. What changes is the role of that particular placement and the way it is presented. So the shortcut does more than save us from another copy. It lets centrally maintained content take part in the same flexible, context-driven composition we have already explored before.

Change context. Not content.

Access does not have to include editing rights.

TYPO3 already knows this idea from asset management. A file can live in one central place, complete with the right metadata, copyright information and everything else that belongs to it.

Other editors can still use it in their own content, crop it for a particular placement or give it a specific role there without touching the original asset.

And that is actually quite a comfortable way to work.

The person who needs an image on a page does not automatically have to be the person responsible for maintaining the source. Sometimes they should not be. They simply need to know: this is the right asset, I am allowed to work with it in this particular context, and the original is in good hands.

Content references can follow the same idea. An editor can place centrally maintained content in their own page or structure even if the original lives somewhere they cannot edit. That gives people room to do their job without quietly handing them someone else’s responsibility at the same time.

Different jobs, different permissions

Responsibility can stay where it belongs.

The larger an editorial team becomes, the more useful it is when not everyone has to do everything. A central content pool can hold material that has already been written, checked and kept up to date by the people who know it best. That may be experienced editors, journalists or subject-matter experts. Other colleagues can then concentrate on what they do best: building pages, putting campaigns together, preparing event content or filling the channels that need fresh material.

And this is where references become especially useful. Editors can take content from that pool and place it in their own pages with Paste as Reference, without creating another independent copy and without needing permission to edit the original. They get the content they need. The people responsible for quality keep control of the source. That also makes everyday maintenance much easier.

Content keeps changing, page after page and day after day. Every unnecessary copy adds one more place to remember when something changes. References let the content travel while responsibility stays where it belongs.

That means fewer duplicate tasks, clearer roles and far fewer rounds of the surprisingly popular editorial game called “who changed this?”

Repetition may be bad, but surely inexactness is worse.
Mark Twain

Sometimes there is really only one

A place can decide how much belongs there.

Freedom is lovely. Until five people decide that the same little area would be the perfect home for five different things.

Sometimes the structure already knows what makes sense. A contact area, for example, may be designed for one main contact. One is helpful. Five will probably make everyone wonder whether they have accidentally landed in the staff directory.

This is where Max Items comes in. Set it to one and that place can hold no more than one element. It may still stay empty, of course.

The structure simply knows where the limit is. And suddenly our title becomes quite literal. There really can be only one. The nicest part is that nobody has to remember the rule. It already lives where it matters, inside the structure itself.

One less thing to keep in mind while getting the actual work done.

The right things in the right place

Structure can remember what belongs where.

Quantity is only half the story. The next question is what actually belongs in a particular place.

Grid Elements has been answering that question for a long time, and with more than a simple list of allowed Content Types. Content Defender later took the same idea even further and made restrictions much more flexible. Today, TYPO3 Core offers part of that concept as well, while Grid Elements now supports the broader approach that Content Defender made possible.

That little piece of history is interesting. For editors, the result is even better. A structure can simply know what belongs there and what does not. Maybe it expects a particular kind of content. Maybe a certain Grid Elements layout. Maybe a project needs something more specific. Either way, the rule stays with the place instead of becoming yet another thing somebody has to remember from a meeting six months ago.

The same goes for references. A shortcut can bring existing content into a new place, but that place still has its own purpose and its own rules. Permissions decide what a person may do. Restrictions decide what a place is ready to accept. And when the structure already knows that, editors can spend their time on something much nicer: the content itself.

Freedom that knows where it belongs

Good structure leaves more room for the things that matter.

References, permissions and restrictions may sound like three rather technical topics. In everyday editorial work, they can feel surprisingly simple. Content can be reused without being copied. The people responsible for it can keep that responsibility. And the structure itself can remember what belongs where, so editors do not have to carry every rule around in their heads.

That is the kind of freedom I like. Not the freedom to do absolutely anything, but the freedom to get things done without constantly worrying whether you are stepping on someone else’s toes or quietly creating tomorrow’s maintenance problem. Use content wherever it belongs. Keep control where it matters. And once the system already knows all of this, one question becomes almost irresistible. What if it could also help editors choose the right next step?

That is where things get really comfortable. And where a certain little wizard is waiting for its turn.

Grid Elements brings references, permissions and restrictions together in a way that makes everyday editorial work pleasantly simple. Content can be maintained once and reused wherever it belongs, while the people responsible for it keep control of the source. At the same time, the structure itself can remember what is allowed in a particular place and how much of it makes sense there. That means fewer copies to maintain, clearer responsibilities and less knowledge that has to live in somebody’s head. Content can travel. Responsibility can stay put. And the structure can quietly take care of the rules.
Petra Hasenau