Collateral is where the brand travels without its context. These artefacts are often seen once, at small size, next to other companies’ material — so they lean harder on the mark and the wordmark than in-product surfaces do.
This is the multi-page printable view of this section. Click here to print.
Collateral
1 - Business card
The primary format is digital — a vCard shared via QR code or direct link, not a printed card.
Paper stock
The same card on white. This is the form to hand a printer when a physical card is required, and the one to reach for when the card will sit on a light surface it does not control — a conference badge holder, a scanned page, a slide.
Three things change, and nothing else does:
| Digital | Paper | |
|---|---|---|
| Surface | midnight-dark-1 | White, in both modes — paper has no colour mode |
| Accent | A 12% wash bleeding off the corner | A 3px rule down the leading edge |
| Mark | Light-on-dark colourway | midnight-9 shell, white cut, orange-9 bud |
The wash does not survive the change of surface. At 12% on midnight it reads as a soft light source; at 12% on white it reads as a printing fault — an uneven patch of ink that a press will faithfully reproduce. So the accent moves to a rule down the leading edge, which is one line, prints cleanly at any size, and is the same device the signature uses.
The name, role, and contact rows keep their type sizes and weights exactly. Only
their colours change, to the light-mode text steps: midnight-9 for the name,
slate-9 for the role at 5.58:1, and slate-11 for the mono rows at 5.18:1.
Switch the site’s theme and the digital card follows it; this one does not. A card printed on white stock is white under every lighting condition there is, and a specimen that goes dark when the reader’s browser does would be showing something that cannot be printed.
Layout
- Midnight surface, mark top-left, name in Plus Jakarta Sans 700.
- Role in Source Sans 3 400, in
slate-dark-11. - Contact rows in IBM Plex Mono at 11px — addresses and handles are data, and monospace makes them scannable and unambiguous.
projectious.workalways present.- Accent used once, on the QR frame or the primary contact method.
Print fallback
If a printed card is required:
- 85×55mm, matte stock.
- Single-colour midnight on uncoated white, or reversed white on midnight.
- Use the monochrome mark — no accent on press unless a spot colour is budgeted.
- Respect the 1× clear-space rule; do not bleed the mark to the trim edge.
Handing colour to a printer
The brand is defined in sRGB hex. Press is not sRGB, so a printed card needs the values converted — and the conversion is the vendor’s job, not a lookup table’s.
Give the printer the Lab values. They are device-independent: they describe the colour itself rather than one recipe for making it, so the vendor can hit them on whatever stock and profile the job actually runs on.
| Colour | Hex | Lab (D50) | CMYK — unmanaged |
|---|---|---|---|
| Midnight | #1d3352 | L 20.7, a −0.5, b −21.9 | 65 / 38 / 0 / 68 |
| Orange | #E05232 | L 54.9, a 55.2, b 48.5 | 0 / 63 / 78 / 12 |
| Accent solid | #cc4528 | L 49.3, a 53.3, b 46.8 | 0 / 66 / 80 / 20 |
| Slate | #546a82 | L 43.7, a −3.7, b −16.2 | 35 / 18 / 0 / 49 |
| Midnight dark | #132440 | L 13.9, a 1.0, b −20.3 | 70 / 44 / 0 / 75 |
Those numbers are the naive device conversion — the arithmetic one, with no colour management. They are here so a proof is not blocked on a phone call, and they are wrong on any specific press.
Convert through the vendor’s own ICC profile before production — FOGRA51 for coated stock in Europe, GRACoL 2013 in North America — and sign off on a physical proof on the actual stock. Matte and uncoated paper absorb ink and will run darker and flatter than the screen, most visibly on Orange.
Do not guess a Pantone equivalent. If the job budgets a spot colour, give the vendor the Lab value and let them specify the closest ink; a Pantone number picked from a screen swatch is a different colour with an authoritative name on it.
2 - Email signature
Email is not the web. Every value below is a literal, every layout is a table, and nothing depends on a stylesheet the client is free to discard.
Two forms are supplied:
| Form | Source | Use for |
|---|---|---|
| Full | brand/email/signature.html | First contact, and any message leaving the organisation — it carries the legally required details |
| Short | brand/email/signature-short.html | Replies and internal mail, where the full block repeated down a thread becomes noise |
The signature
Jane Doe Principal Consultant Projectious GmbH Musterstraße 1, 10115 Berlin, Germany Projectious GmbH · Registered seat Berlin Amtsgericht Charlottenburg, HRB 000000 · VAT ID DE000000000 Managing director: Jane Doe This message is intended only for the addressee and may contain confidential
information. If you received it in error, please tell the sender and delete it. |
Jane Doe Principal Consultant · Projectious GmbH |
Both specimens are rendered on white, because that is where a signature actually lives. The surrounding page has a colour mode; a mail message generally does not.
One rule, and it is vertical
A signature accumulates dividers as it accumulates fields — one under the name, another above the legal block, another before the disclaimer — and each reads as a section break in a message that is not sectioned. On a white background the result is a small form stapled to the bottom of a letter.
So there are no horizontal rules at all. One vertical accent rule runs down the left of the whole block: it marks the signature as a unit, ties it to the brand, and costs one line instead of four. Everything else is separated by space and by type size.
Group the fields — identity, contact, address, legal — and separate the groups with about 9px of space. Let the type sizes do the ranking.
Add a rule between groups, a coloured band behind the name, social icon rows, a quotation, or a “please consider the environment” line.
Fields
Replace every [PLACEHOLDER]. Delete any row that does not apply — the block is
built so that removing a row leaves no gap behind it.
| Field | Required | Notes |
|---|---|---|
| Full name | Always | 15px, 700, midnight-9 |
| Job title | Always | Its own line — a title merged into the company line reads as part of the company |
| Company legal name | Always | The registered name, not the trading shorthand, wherever the legal block appears |
| Phone | Recommended | With country code; a signature is often read from another country |
| Email address | Always | Even though it is in the header — messages get forwarded |
| Website | Always | |
| Postal address | Regionally required | Street, postcode, city, country |
| Register details | Regionally required | Legal form, registered seat, register court and number, VAT ID, directors |
| Confidentiality notice | Optional | Two lines at most; delete it unless your organisation requires it |
What the law asks for
A starting point, not legal advice — confirm against your own jurisdiction before shipping a signature.
| Jurisdiction | Business email must carry |
|---|---|
| Germany | Legal form, registered seat, register court and number, and every managing director (§ 35a GmbHG, § 37a HGB) |
| EU / UK | Company registration number, registered office address, and VAT number where registered |
| United States | No statutory signature requirement; confidentiality notices are convention rather than law |
| Canada | CASL requires sender identification and a postal address on commercial messages |
| Australia | ACN or ABN on business correspondence |
Construction
| Rule | Why |
|---|---|
Table layout, role="presentation" | Flexbox and grid do not survive Outlook’s Word renderer; the role stops screen readers announcing a data table |
| White declared on table, row, and cell | A client repainting for dark mode decides what to invert per element. White on the cell alone leaves the table around it unpainted — see below |
Each background written twice, as bgcolor and background-color | The background shorthand alone is not enough: several clients strip shorthands and keep longhands, and Outlook’s renderer prefers the attribute |
| Inline styles only | Most clients strip <style>, and none support custom properties — so no var(--pj-*) anywhere |
| Web-safe font stack | Brand faces will not load in a mail client; the stack degrades to a system sans without changing the layout |
| Maximum width 520px | Below the 600px that forces horizontal scrolling in narrow reading panes |
| Literal hex values | The brand steps, written out — see the table below |
| No images | A hosted logo is blocked by default in many clients and leaves a broken frame. The accent rule carries the brand with nothing to load |
| No background images | If a fill is ever needed, use the bgcolor attribute |
Declaring white three times is not belt-and-braces
It is the difference between a signature that survives dark mode and one that does not, and it is the most common way this block breaks.
<table … bgcolor="#ffffff" style="…background:#ffffff;background-color:#ffffff;…">
<tr bgcolor="#ffffff" style="background-color:#ffffff">
<td bgcolor="#ffffff" style="background:#ffffff;background-color:#ffffff;…">
A client that repaints a message for dark mode works element by element: it
looks at each one, decides whether it has a background it should keep, and
inverts the rest. Declare white only on the <td> and the <table> around it
has no background to keep — so the cell stays white while its own container is
repainted dark. The result is a white island with a dark halo, or worse, the
dark text inverted to light and then drawn on the white cell that was kept.
Every enclosing element that has a painted area needs the declaration, and each
one needs it in both forms: the bgcolor attribute, which Outlook’s renderer
prefers, and background-color, because several clients strip the background
shorthand while keeping longhands.
Several clients — Outlook mobile and some webmail among them — invert or shift signature colours in dark mode, and none can be reliably prevented from doing so. The signature is therefore built to survive recolouring rather than to fight it: the hierarchy is carried by size and weight as much as by hue, so it still reads when the palette is altered.
Colours
Three families, which is what a signature should have.
| Role | Value | Use |
|---|---|---|
| Heading | #1d3352 | The name |
| Primary text | #142438 | Title, phone |
| Secondary | #546a82 | Company, address |
| Link | #3a5a82 | Email, website |
| Legal and notice | #546a82 | Register details, confidentiality notice |
| Accent | #E05232 | The vertical rule, and nothing else |
Before shipping a change
- Send to Outlook (Windows), Gmail web, Apple Mail, and one mobile client.
- Reply to that message twice and check how the signature looks quoted inside a thread.
- Turn on the client’s dark mode and confirm the hierarchy still reads.
- Forward it, to confirm nothing depends on the original message’s styles.
3 - Email
The signature covers the block at the bottom of someone else’s message. This page covers the message itself: a full-width, sendable email with a header, sections, a call to action, and a footer.
Everything the signature page says about construction — tables, inline styles,
web-safe stacks, literal hex, role="presentation" — applies here unchanged and
is not repeated. What follows is what a whole message adds.
| Source | |
|---|---|
| Newsletter | brand/examples/email-newsletter.html |
It opens straight from the filesystem — no runtime, no build step — so it can be pasted into a sending tool and previewed as-is.
Structure
600px, centred on a neutral surround, in this order:
| Band | Fill | Contents |
|---|---|---|
| Preheader | hidden | One sentence, ~90 characters — see below |
| Masthead | midnight-9 | The wordmark. Nothing else |
| Lede | white | Issue overline, headline, and a standfirst that says what is inside |
| Sections | white | Numbered overline, heading, two or three sentences |
| Call to action | white | One bulletproof button |
| Footer | midnight-9 | Identity, why they are receiving it, unsubscribe, postal address |
600px is the width every mail client can be relied on to render without
horizontal scrolling, and it is the reason the message is not laid out on the
1100px measure. Below
that, max-width:100% on the outer table lets the content reflow in a phone
client.
Sections are numbered — 01 · agent pattern — in the accent, in the overline
style. The number is the only ornament in the body: it gives a scanning reader a
structure to skip through without a rule, an icon, or a background tint per
section.
The preheader
The first line of hidden text is what the inbox shows next to the subject line. It is not optional and it is not a repeat of the headline:
<div style="display:none;max-height:0;overflow:hidden;opacity:0;">
Cloud · Agile · Agentic AI — this month: three agents worth stealing, and
why generic SaaS is losing its edge.
</div>
Leave it out and the client fills the space with whatever text comes first, which is usually the wordmark followed by “View in browser”.
The bulletproof button
A styled <a> is not a button in Outlook’s Word renderer: padding collapses and
the fill shrinks to the text. So the call to action is built twice — a VML
rectangle inside a mso conditional comment, and a table cell with bgcolor
for everyone else.
<!--[if mso]>
<v:roundrect xmlns:v="urn:schemas-microsoft-com:vml" href="https://…"
style="height:44px;v-text-anchor:middle;width:220px;"
arcsize="9%" fillcolor="#cc4528" strokecolor="#cc4528">
<w:anchorlock/>
<center style="color:#ffffff;font-family:Arial,sans-serif;font-size:14px;font-weight:bold;">
Read the case study
</center>
</v:roundrect>
<![endif]-->
<!--[if !mso]><!-->
<table role="presentation" cellpadding="0" cellspacing="0" border="0">
<tr><td bgcolor="#cc4528" style="border-radius:4px;" align="center">
<a href="https://…" target="_blank" style="display:block;padding:13px 26px;
font-family:Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;
color:#ffffff;text-decoration:none;mso-line-height-rule:exactly;">Read the case study</a>
</td></tr>
</table>
<!--<![endif]-->
Three things are load-bearing:
- The fill is
#cc4528, not#E05232. White on the identity accent is 3.87:1; onaccent-solidit is 4.72:1. The same rule as solid controls in the interface, and email is where it matters most, because a mail client will not offer a hover state to compensate. - 44px tall. A mail is read on a phone more often than not, so the touch floor is the binding constraint.
arcsize="9%"approximates the 4px radius the HTML path sets. VML has no pixel radius; it takes a percentage of the shorter side.
One button per message. A second call to action does not add a second chance — it splits the first one.
Colour in a message
The signature’s colour table holds, with two additions a whole message needs:
| Role | Value | Use |
|---|---|---|
| Body text | #142438 | Paragraphs — midnight-12, never #333 and never #000 |
| Section overline | #c04424 | The numbered section labels — orange-11, 5.13:1 on white |
| Button fill | #cc4528 | With white text, 4.72:1 |
| Footer text | #c5daf0 | On the midnight-9 footer, 8.90:1 |
| Footer link | #f0a48c | Unsubscribe, on midnight — 6.31:1 |
| Hairline | #e5e3de | Section dividers, as a 1px table row |
| Page surround | #f5f4f2 | Behind the 600px sheet. Not a system token — it is the neutral the standalone brand documents use, and it exists so the white sheet has an edge in clients that show one |
The accent appears as text in the overlines and as a fill on the one
button — and #E05232 itself appears nowhere carrying text, in either role.
The footer is not decoration
Commercial mail has to say who sent it, why it arrived, and how to stop it. Those three facts are the footer’s whole job:
- Who — the legal entity and its postal address.
- Why — one sentence: “Sent to you because you subscribed to Field notes.”
- How to stop — an unsubscribe link that works in one click and does not require signing in.
An unsubscribe that leads to a login screen is, in most of the jurisdictions on the signature page, not an unsubscribe.
Before sending
- Send to Outlook (Windows), Gmail web, Apple Mail, and one mobile client. The VML path only exists for the first of those, so it only gets tested there.
- Check the preheader in the inbox list, not just in the opened message.
- Turn images off. The message must still make complete sense — which is why there are none in the layout to begin with.
- Turn dark mode on. Clients recolour aggressively; as with the signature, the hierarchy is carried by size and weight so it survives.
- Click the unsubscribe link from a logged-out browser.
Write the preheader. Keep the message at one call to action. Fill solid buttons
with accent-solid. State why the reader is receiving it.
Ship a styled <a> as the only button, use #E05232 behind white text, rely on
an image to carry the message, or hide the unsubscribe behind a login.
4 - Social and OG images
Priority
LinkedIn and GitHub first, blog second, Twitter/X as backup. The templates are sized for those surfaces in that order.
Template rules
- Backgrounds are midnight or midnight-dark, or white with an accent top bar.
projectious.workis always visible.- Never place text over a busy background.
- An accent glow circle at subtle opacity provides visual interest without competing with the text.
- Typography hierarchy is unchanged: Plus Jakarta Sans for headlines, Source Sans 3 for body.
not a constraint.
Open Graph
- 1200×630px.
- Headline at Display weight, capped at roughly 60 characters — longer headlines are truncated by most platforms anyway.
- The mark sits bottom-left or top-left, never centred.
- Test the rendering at 320px wide: most impressions are in a mobile timeline.
Keep one message per card. Check contrast against the actual background, not the design canvas.
Fill the card with a screenshot, use more than one accent element, or rely on text smaller than 24px at 1200×630.
5 - Service one-pager
The card, the signature, and the social artwork all carry the brand in a few square centimetres. The one-pager is the opposite problem: a whole page, handed over or attached, that has to explain a single service to someone who has not asked yet.
| Source | |
|---|---|
| Service flier | brand/examples/flier.dc.html — “Cloud migration accelerator” |
One service per sheet
A one-pager describes one offer. A sheet listing four services is a capabilities brochure, and it is read by nobody, because a reader who wants one of the four has to find it first.
If there are four services, there are four one-pagers. They share the structure below and differ only in their content — which is what makes the structure worth specifying.
The bands
Four horizontal bands, top to bottom. The sheet is 1000px wide in the HTML source and prints to a single A4 or Letter page.
| Band | Fill | Job |
|---|---|---|
| Header | midnight-9 | Wordmark, an overline naming the artefact, the service name at display size, and one sentence of promise |
| Benefits | white | Three columns: icon in a tinted tile, a short heading, two lines of body |
| Process | white | A numbered horizontal sequence — the steps, with a duration under each |
| Close | midnight-12 | The one-line commitment, the contact route, and one accent button |
Two midnight bands, at the top and the bottom, with white between them. The sheet opens and closes on the brand and leaves the middle to the content — the same shape as a title-and-closer deck, for the same reason.
The header carries a single decorative element: an orange-9 circle at 6%
opacity bleeding off the top-right corner. That is the entire ornament budget for
the page.
Three benefits, not five
Three columns fit a 12-column grid at four columns each, three items are readable at a glance, and three is roughly how many distinct reasons a person retains from a page they were handed.
Each benefit is an icon tile, a heading of no more than five words, and body text of no more than two lines. The icon is Lucide at 20px inside a 40px tile filled with the tag background — it is a marker, not an illustration.
The heading states the benefit, not the feature: “Self-hosted where it matters”, not “Self-hosting support”.
The process band
A numbered sequence with a connecting rule, each step carrying a duration. The durations are the point: a one-pager that says “we migrate your cloud” competes on adjectives, and one that says “week 3: stand up self-hosted core” competes on a plan.
The numbers are set in IBM Plex Mono inside midnight-9 discs, because they are
data. The connector is a 1px slate-5 rule, not an arrow — the numbers already
carry the direction.
Do not put a duration on the sheet that the engagement cannot hold. The portfolio principle — make maturity and limitations easier to see, not harder — applies to sales collateral without modification.
One call to action
The close band gets one accent element. It is a button shape carrying white text,
so it fills with accent-solid (#cc4528) and not the identity accent — the
same 4.72:1 rule as the interface
and the email.
Beside it, exactly one contact route, in mono. Two routes make the reader choose before they act.
Printing it
The example is HTML, and the export path is the browser’s print dialogue — the same route as the resume template.
- Colour is not guaranteed. A one-pager is frequently reprinted on an office mono laser. The layout must survive greyscale: the bands separate by value, the numbers stay legible, and no meaning is carried by the accent alone.
- Turn on background graphics in the print dialogue, or the midnight bands print as white and the reversed text disappears.
- Check the fold. If the sheet will be folded, nothing important sits within 10mm of the fold line.
- For volume print, hand the vendor the CMYK values rather than the hex.
Keep one service per sheet, three benefits, and one call to action. Put real durations on the process steps. Check it in greyscale before it is printed.
List a service catalogue, use stock photography of people in meetings, add a second contact route, or promise a timeline the engagement cannot hold.