Skip to content
Interface language: English
Design / Signal

Pasted from a document, published on a page: what should an editor preserve?

Design a content editor that preserves structure, links and meaningful lists through paste, preview and draft reopening.

Article language: English

Illustration of two people at a table before a large circular structure and mountains.
In this article

The event programme looked impeccable in the document. Once pasted onto the site, it has three typefaces, gaps as wide as the intervals between concerts and numbering that starts at one every time. Some problems can be fixed with one command. Others disappear only along with information that should have been preserved.

Designing a content editor means deciding what to carry across: words, structure or appearance. Usually we need the words and the meaning of their arrangement, while appearance should follow the site's rules. “Paste without formatting” can be useful, but it is not a universal way to preserve headings, links and lists. A clean paragraph can be just as wrong as erratic typography.

Start with content that must survive a change in appearance

Consider a fictional programme for a small festival. The document contains a title, directions, a list of things to bring and a booking link. An editor transfers it into a CMS. A correct result is one in which a website visitor can recognise the sections, read the instructions in order and open the right address. We do not require a printed page layout to be reproduced on a phone screen.

A heading is a structural role, not just large bold text. The editor should let a person assign that role without manually choosing a font size. Changing the size of a section title should not accidentally remove its structural role. Conversely, an ordinary paragraph enlarged for decoration should not automatically become a new level in the text hierarchy.

W3C technique H42 explains how heading markup conveys role and level to assistive technology and supports navigation through the structure. That is a reason to check more than how similar letters look on two screens. Good appearance alone does not establish that the same information about content organisation was carried over.

Names in the toolbar should help an editor choose the right role. “Section heading” may be clearer than an anonymous set of sizes, provided it corresponds to the actual level in that field. A page-title field and a body field need not offer identical sets. The design must establish how their contents combine into the final structure.

Likewise, a list should remain a list. Typing a dot before every paragraph does not automatically produce the same result. For numbered instructions, check continuation and restarting. A “3” may be the third step or ordinary text containing a number. The editor should not take away the author's ability to distinguish those cases deliberately.

The order of setting up a station matters in the festival programme. If every pasted step starts at one, it is not enough to say “the text is correct”. If the list of things to bring becomes a sentence separated by spaces, readers lose an easy way to scan it. These are different effects of conversion and need separate acceptance cases.

A link has a label and an address. The editor should be able to check both, even when “Booking” looks right. Pasted text should not suggest the right function while retaining an old address for a previous edition of the event. Make link properties easy to open and the end of editing recognisable, rather than requiring the whole part of the sentence to be typed again.

Site typography (in Polish) determines how these roles look. The editor should lead to the intended set, not to a free mixture of typefaces from every document. If a brand needs a quotation or organisational note to stand out, a named variant is better than asking an editor to remember a colour and spacing.

That does not mean leaving only one button. Limiting the set makes sense when it fits the content. Removing list creation from the panel of a company that publishes instructions will not simplify its work. It will move the work to manual workarounds that later need to be recognised and corrected.

What enters the editor and what only looks familiar

Pasting transforms content between two representations. The source application, clipboard, browser and editor configuration affect what reaches the page. The editor does not need an explanation of that whole chain for every action. The team does need to know what it has actually tested before promising that formatting is preserved.

CKEditor 5's Paste from Office documentation notes that the preservation of structure and formatting depends on features enabled in the specific editor configuration. That limit has a practical meaning: support for headings does not automatically establish support for every document element. A vendor example does not replace a trial with the commissioning company's own material.

Tiptap's schema documentation shows that elements and attributes outside the permitted model are not retained; its example concerns bold text without the corresponding extension. Here a schema means rules for the permitted content structure. It is not an instruction that authors must first learn the editor's code, but information needed to define its behaviour.

In Aeneia Design's editor and content-component work, these limits can be translated into tool names, previews and messages. Start with an actual programme, instruction or service description used by the company. The chosen library and its settings establish technical boundaries; the design gives them a form the editor can understand.

Provide two modes if both fit the tasks: ordinary paste and paste as plain text. The second description should explain the loss of emphasis and links if that is how the chosen solution works. Do not call it “fix formatting”: sometimes it removes exactly the meaning needed. The editor must know why the list needs rebuilding after that action.

Removing formatting from a fragment already pasted also needs a defined scope. Do only colour and typeface disappear, or also a heading, list or link address? The button name, the indicated selection and the outcome should tell the same story. A single command that silently removes different things in different places makes the outcome hard to predict.

Aeneia conceptual photography

When an operation changes a larger fragment, the user needs a way to inspect and undo the result. Rules for undoing a particular change (in Polish) help establish exactly what returns. In an editor, also decide whether one undo removes the whole paste or only the latest automatic correction. If the editor later added a sentence, ordinary undo history may remove that newer change first. Do not promise a separate undo of an earlier paste while keeping every later correction if the product does not offer it. The acceptance case should show the actual sequence and how to redo a change undone by mistake.

Tables deserve a separate decision. If the chosen content model does not support them, pasting cells as successive paragraphs can destroy the relationship between a time and an event. Agree a suitable replacement: a named programme component, a manually built list with times, or a table supported throughout the publication path. Do not leave the decision to accidental conversion.

The insertion point matters too. The same steps can go into an empty field, the middle of a paragraph or an existing list. When two items are pasted between steps two and three, the editor should be able to tell whether one list was extended or a separate list created. Acceptance material must show both neighbouring fragments. Checking only the pasted words will not reveal whether the following instruction was numbered incorrectly or incorporated into the final item.

A photograph visible after pasting needs checking as well. Establish whether it is already stored in the site's library, awaiting upload or referencing an external location. The design should show a state consistent with the system's actual behaviour. An image visible in the editor currently open does not prove it will remain available after reopening the draft.

Do not couple that with a promise that arbitrary pasted content is safe. Technical control of permitted data and its display needs a separate implementation. What matters visibly to the editor is which elements were accepted, what needs fixing and whether they can return to the previous state without loss. An attractive toolbar does not replace any of that information.

Decide how to communicate loss of an unsupported element. Omitting a note for participants or a footnote with a condition of participation may change the meaning of the programme. There is no need to raise an alarm for every removed colour. There is a need to decide which missing elements require conscious completion and how the editor will find them. If the mechanism cannot detect an omission, provide an explicit checklist for that kind of material instead of pretending the automatic check is complete.

Aeneia Design

Bring a document your team actually uses to transfer content to the site. Let us design text roles, paste rules and preview so the editor can recognise the structure retained and the elements needing correction. Discuss an editor suited to your company's content

Preview should reveal a difference before publication

The editing view need not look like the finished page, but it should not hide the page's limitations. An editor may work in a wider column with extra structural indicators. They still need a route to a preview using the actual display rules. Otherwise they approve content based on a layout the audience will never see.

The CMS publication process (in Polish) separates draft, approval and public result. Here we check an earlier question: did meaning survive the transfer from document to the site's model? This need not require a trial festival programme to be made public. A good preview lets the team assess the result before festival visitors can see it.

Include a short but awkward fragment in the acceptance material. It might contain:

  • A subsection heading and similar-looking bold text in an ordinary sentence.
  • A numbered list with an explanation between steps and continued numbering.
  • A link with a short label whose address must be read separately.
  • A programme line with a time, a long event name and a photograph.

Describe the expected result for each fragment before comparing screenshots. The heading should retain the proper role, numbering should follow the agreed order, the address should match the label and the photograph should follow the intended storage path. Record intentional removal too. Absence of a foreign font may be correct; absence of the second instruction step is not.

Run the trial with the applications the team actually copies documents from and the browsers it actually uses. Retain the input material's version, editor settings and a description of the difference observed. Without these, “it breaks after pasting” cannot be reproduced. Do not attribute one behaviour to all editors just because their icon bars look similar.

After pasting, add a sentence, change a link, save and reopen the draft. Check that the result still matches the preview. This reveals a difference between the temporary screen state and content the system actually stores. Acceptance testing should not end the instant the clipboard releases its contents.

On a phone, inspect long names, text, lists and the division of the programme. A separate article discusses designing for long names and text (in Polish). An A4 page layout may need a different presentation without changing the content. Do not make the editor rescue it with a series of spaces. Indentation and spacing belong to designed rules that should survive a change in screen width.

If the editor offers quick actions through a command palette, they should assign the same roles as visible tools. A separate article discusses command palette design (in Polish). A shortcut to “Section heading” cannot mean only a larger font. Different routes lead to one content model and then to one understandable result on the page.

Finally compare the document and the preview against the reader's tasks: find directions, bring the necessary things and choose the right booking address. If that information survives and the appearance suits the site, the editor has done its job. Faithfulness to an accidental shade of text in the document does not need a medal of its own.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear