SAMPLE ONLY: Editorial design
A review-only showcase of shared article typography, quotations, wide and compact images, galleries, lists, code and tables.
This is a design sample for reviewing our shared article components. The examples below demonstrate editorial layouts; they are not a founder essay or a product announcement. The same typography, image treatment and content renderer are used by the Aeptus website and EOL.
Paragraphs and inline details
A readable article starts with a comfortable line length. Bold text marks a short point that readers can scan, while emphasis changes the stress of a sentence. A filename such as article.json has a separate treatment so technical details remain distinct from prose.
These choices should serve the piece. A paragraph can carry an argument without surrounding every sentence with a card or a coloured label. On a small screen the text keeps its reading rhythm, headings wrap naturally, and media stays inside the viewport.
Quotes and attribution
Sample quotation: leave enough space around a quoted passage for the reader to notice the change of voice, then give them a clear route back to its source.
Design demonstration only. This quotation was written for the sample; it is not attributed to an outside person.
Quotations use a quieter editorial surface and a visible accent. Short quotations can remain in the flow of the article. A longer extract should be selected for what it contributes, with the source and any relevant context stated nearby.
Small pictures and captions
A small image works well for a detail, an object or a supporting illustration. It should not be enlarged to fill the page when its role is modest. Alt text describes the useful visual information; the caption can add context that also matters to sighted readers.
The image alignment is an editorial choice in EmDash. The shared renderer preserves that choice, while the article shell sets how far a wide picture may extend. This keeps ordinary text narrow even when an illustration needs a larger canvas.
A pair of pictures
A gallery keeps related pictures together. Each image has its own description and caption, and the sequence follows the order chosen by the editor. The pair becomes a single column on a phone, where squeezing two pictures into a narrow row would make their detail hard to inspect.
Lists that are easy to scan
Use an unordered list when the items belong together but do not form a procedure.
- Keep each item short enough to scan.
- Use parallel wording so the relationship is clear.
- Move longer explanations into ordinary paragraphs.
Use an ordered list when the reader should follow a sequence.
- State the task and the result the reader should expect.
- Give the steps in the order they will be carried out.
- Finish with a way to check that the task worked.
Technical detail and code
A code example should carry the smallest complete detail needed to explain the point. The filename labels the example, and the code keeps its whitespace. Long lines scroll within the code panel rather than push the whole article sideways.
{"purpose":"editorial design review","locale":"en-gb","sampleOnly":true}
This JSON is demonstration content, not an application setting. Inline code suits a name or a short value; a dedicated code panel is easier to read when the example has several lines.
Tables and comparisons
A table is useful when readers need to compare the same attributes across several items. Keep the labels concrete and the number of columns small. On a narrow screen, an unusually wide table can scroll inside its own frame.
| Element | Use it for |
|---|---|
| Wide image | A scene or illustration that benefits from a larger view |
| Compact image | A detail that supports the surrounding prose |
| Gallery | A sequence of related images |
| Quotation | A clearly identified passage from another source |
Links and source notes
The examples use the native structures described in EmDash’s content guide. Image descriptions and captions remain editable in the CMS, while shared code controls how they render across publications.
A source note should help the reader identify the underlying material. It can distinguish an external quotation from an editor’s summary or a design example. Neither a decorative image nor a sample table should imply evidence for a claim the article has not made.
The article ending
At the end of a real piece, offer a relevant next read and a useful way to respond. Keep the conversation with the article, and make review expectations clear before a reader contributes. Optional subscription or contact links should point to actual destinations configured for the publication.
Review this sample at a wide desktop size and on a phone. Check the transition from prose to media, whether captions remain legible, and whether the discussion form supports the reading experience. Replace this sample with authored editorial content before a public launch.
Keep the conversation with the article
Discuss this article
Questions, field notes and thoughtful counterpoints are welcome. Contributions are reviewed before they appear; your email stays private.
Reader contributions
Loading discussion…
No contributions yet. Add the first useful question or field note.
The discussion is temporarily unavailable. Please try again shortly.