top of page

f1ed71a5-94e5-4ccd-96da-91a24db84560

​

About the Author

17 hours ago
5 min read

Modern readers expect clear calls to action, prominent quotes, and scannable summaries. Amplience gives organizations a strong digital foundation. Building on top of this foundation, we developed custom extension blocks, allowing content creators to create these engaging elements effortlessly without needing developer support for every change.


For example, a global client in a regulated industry wanted to expand upon Amplience's standard rich text capabilities to better support their specialized content workflows. We partnered with them to introduce five custom content blocks into their Amplience editor: call-to-action buttons, highlighted paragraphs, pull quotes, TL;DR summaries, and call-out boxes. By turning approved brand layouts into ready-to-use blocks, editors simply insert their content while Amplience automatically enforces brand governance and design consistency.

All of the blocks sit in one menu on the editor toolbar, so editors can find them in a single click.

Amplience rich text editor toolbar with a content blocks menu open

This post shows how each block works and the principles behind them.


How Amplience content blocks differ from styles

These blocks aren't new Amplience content types, the components teams use to build page layouts. They live inside a single rich text field, so editors add them as they write, without leaving the text.


At first glance, some of these blocks may look like text styles. The difference is in what gets saved and who controls the design. Ordinary formatting saves how text looks: a font size, a color, a border. A content block saves what the content is.


When an editor makes a pull quote, Amplience records it as a pull quote, not as large italic text with a colored line. When the page is built, the website reads that and applies the approved pull quote design, including the quotation marks, which editors never type.


Because the design lives with the website rather than in each piece of content, a change to the pull quote design updates every pull quote on the site, and no page can drift off brand.

The TL;DR summary goes one step further. It opens and closes, so it's built as its own kind of content, with the summary and the full text stored separately. The website turns that structure into an interactive card.

Call-to-action buttons

A call-to-action (CTA) button tells the reader what to do next, such as "Learn more" or "Order now". Before this work, editors could only add a plain text link inside the content.


Now editors select some text, apply a CTA button style, and add a link. The text becomes a button that matches the buttons used across the rest of the website. Editors can choose a primary style in the brand color or a secondary style in dark gray, so a page can have one main action and one alternative.


A paragraph followed by a primary CTA button in the brand color and a secondary CTA button in dark gray

Highlighted paragraphs

Some information needs to stand out from the text around it: an important note, a key fact or a short warning. A highlighted paragraph places the text in a box with a thin brand-colored border, a small indent and comfortable inner spacing.


Editors choose one of three backgrounds: white, light gray or a light brand tint. This gives them some variety on long pages, while every option stays within the design system.

A highlighted paragraph with a light brand tint background and a thin brand-colored border

Pull quotes

A pull quote lifts a short, strong line out of the text, such as a customer comment or an expert opinion. It shows the quote in larger type with a vertical accent line on the left, in a color the editor picks from the brand palette.


The small details matter here:


  • Quotation marks are added automatically. Editors type plain text, and the block adds typographic quotation marks. This keeps the marks consistent and prevents doubled or mismatched quotes.

  • Attribution is optional. Editors can add a name, such as "Jane D., customer". If they leave the field empty, the attribution line disappears completely, with no stray dash or empty space.

  • Empty quotes never go live. A pull quote with no text is not shown on the website.

A pull quote with a vertical accent line, quotation marks and an attribution

TL;DR summaries

Many readers scan a page before they decide to read it. A TL;DR ("too long; didn't read") block gives them a short summary at the top, with the full details one click away.


The block is a bordered card with three parts: a "TL;DR" label, a summary of one or two sentences that is always visible, and a section with the full content that is collapsed by default. A button at the bottom of the card expands and collapses it, and its label changes between "Read the full story" and "Show less".


This was the only block with interactive behavior, so it needed the most care:


  • In the editor, authors write the summary and the full content in separate fields, and the card is clearly marked so its purpose is obvious before publishing.

  • On the website, the section opens smoothly to the height of its content, whether that is two lines or twenty paragraphs.

  • For edge cases, a card with no summary is never shown. A card with a summary but no full content hides the button, so readers never click on nothing.

A collapsed TL;DR summary card at the top of a page

Call-out boxes

A call-out box is a small box of supporting text, such as a related tip or a definition. On blog pages, it sits on the right side of the main text, and the text flows around it, as in a magazine.


This created a challenge. The editor cannot show text flowing around a box the way the website does, so editors could easily misjudge how the page would look. Our solution was to give the call-out box a clear, distinct style in the editor and a short note explaining that it will appear beside the text on the live page. Editors know exactly what they are adding, even before they preview it.

A call-out box in the editor with a note, and the same box on the live page with text flowing around it

The principles behind every content block

Accessible by design. Each block uses semantic HTML, so screen readers understand what it is. For example, a pull quote is marked up as a real quotation with its source, not just large text. Text colors meet WCAG AA contrast levels, and the TL;DR button works with a keyboard. When the TL;DR section is collapsed, keyboard and screen reader users skip over it, just as sighted readers do.


Visible to search engines. Collapsed TL;DR content stays in the page, so search engines can still read and index it. If JavaScript fails to load, the full content is shown instead of being hidden.


Hard to get wrong. Empty blocks never appear on the live page, quotation marks are always consistent, and colors always come from the brand palette. The blocks handle these details, so editors can focus on the content.

Give your Amplience editors the blocks they need

Amplience gives teams incredible flexibility to extend and personalize the authoring experience. By working with Achieve Internet to customize Amplience around your team's specific needs, content creators gain the autonomy to build rich, engaging pages while keeping every piece flawlessly on-brand.


At Achieve Internet, we build Amplience customizations like these, from custom editing fields and dashboard extensions to search, integrations and content workflows. If your editors are waiting on developers for everyday content, let's talk.

Custom Content Blocks in Amplience: Staying On-Brand Without a Developer

Amplience provides powerful, flexible content management capabilities out of the box, and its extensions allow teams to easily add tailored tools for their editors. One of the most impactful additions is custom content blocks: ready-made elements that make pages easier to read and act on while streamlining the editing process.

Ron Huber

5 min read

Reach out to our team today to learn more about how we can help you take your organization to the next level through impactful digital transformation initiatives and advanced API portals

THE SOLUTION

Case study paragraph

THE CHALLENGE

Case study paragraph

THE IMPACT

Case study paragraph

THE GOAL

Case study paragraph

Recent Posts

Download Your Guide
bottom of page