Typography
The typography model is shared across Landcare Australia, Landcare, Coastcare, and Junior Landcare. Use Open Sans for almost all typography: headings, sub-headings, body copy, captions, documentation, applications, web, and print. Keep Sari for specifically approved brand logotype and logo-related work so the distinctive Landcare wordmark is not diluted by overuse.
For large display specimens and promotional examples, use approved brand palette values only. The typography specimens use Forest where a dark green heading is needed because it is an approved secondary colour with stronger reading contrast than Landcare Green in long or large text settings.
Roles
| Typeface | Role | Guidance |
|---|---|---|
| Primary Typefaces | ||
| Sari | Distinctive Landcare logotype family | Place first because it is brand-defining, but keep it restricted. Use only for approved logo artwork, wordmarks, lockups, and rare brand-signature treatments. Do not use it as the everyday heading style. |
| Open Sans | Core working family | Use for almost all typography: display titles, H1s, headings, sub-headings, body copy, captions, documentation, applications, web, print, and production templates. It is free through Google Fonts and should be the normal choice. |
| Secondary Typefaces | ||
| Futura PT | Alternative design option | Use only when a layout needs a specific secondary design voice. Do not use as the default body, heading, documentation, or governance face. |
| Calibri | Microsoft Office and system fallback | Use for PowerPoint, Word, Excel, Outlook, email, and other Microsoft Office contexts when Open Sans is unavailable. |
Digital Typography Specs
For websites, documentation sites, and applications, use the generated Landcare CSS rather than copying type values by hand. Import the brand CSS first, then the component CSS:
@import "https://landcare.dev/packages/css/dist/landcare.css"; @import "https://landcare.dev/packages/css/dist/components.css";
The brand CSS provides the typography tokens, such as:
--lds-type-h1-font-size --lds-type-body-line-height --lds-type-eyebrow-letter-spacing
The component CSS provides reusable digital type classes:
<h1 class="lds-type-h1">Landcare event report</h1> <p class="lds-type-lead">A short summary of the project, place, and outcome.</p> <p class="lds-type-body">Use Open Sans for readable online body copy.</p> <p class="lds-type-caption">Photo: Your Name Landcare.</p>
Use the CSS classes when working in an online environment. Use the token names only when a local component needs custom styling that still follows the Landcare system.
Print Typography Specs
For print, signage, posters, reports, and other promotional design work, use the print size and print leading columns in the type table below as the reference specs. These are supplied in points because print designers usually need to set type manually in design software.
Print specs are starting ranges, not one fixed size for every format. Scale the hierarchy to the size and viewing distance of the artefact while preserving the same relationship between Display, H1, H2, Lead, Body, Caption, and Eyebrow.
Use Open Sans for normal print typography. Reserve Sari for approved logo artwork, wordmarks, lockups, and rare brand-signature treatments only.
Hierarchy
Display
Landcare Design System One major first-read statement on documentation landing pages, campaign posters, social tiles, report covers, or high-level section openers. Use Open Sans to keep the brand system consistent and avoid diluting the logotype.H1
Brand Governance Page, template, campaign, or artefact title. Use once per composition where possible. Use Open Sans for normal headings and titles.H2
Logo Licensing Major section heading. Use Open Sans for clear structure and consistent production across web, print, and applications.H3
Clear Space Subsection title, card title, rule block title, or artefact heading.Lead
The shared source of truth for brand-governed documentation, tokens, and artefacts. Opening summary under H1. Keep to one or two short sentences.Body
Body copy should be quiet, readable, and set to a comfortable measure for sustained reading. Default reading text for documentation, promotional body copy, governance notes, artefact descriptions, and application copy.Caption
Source: Master Brand Guidelines 2024, page 14. Image captions, source notes, colour details, compact annotations, and print credits.Eyebrow / Metadata
FOUNDATIONS Navigation labels, metadata headings, short status labels, campaign categories, and source categories. Use sparingly.Brand Logotype
Landcare Restricted brand logotype role. Use Sari only in approved logo artwork, official lockups, or specifically approved brand-signature treatments.Text Elements
These specimens define how semantic HTML text elements should appear in documentation, generated artefacts, and application references.
Paragraph
Paragraphs are the default reading unit. Keep them short, left aligned, and set to a comfortable measure.
Inline Emphasis
Bold text can create visual weight. Important text carries semantic importance. Italic text can mark a title or alternate voice. Emphasized text changes stress within a sentence.
Marked text highlights a phrase. Smaller text supports secondary reading. Deleted text and inserted text show editorial change.
Scientific and technical notation can use H2O, CO2, or m2.
Links And Rules
Links should be clear, underlined, and specific. Horizontal rules separate major reading modules.
The rule above uses the same quiet line system as section headings and tables.
Quotes
Brand consistency is maintained through shared rules, reviewed changes, and inherited tokens.
Landcare Design System principle
An inline quote uses quotation marks supplied by the browser
.
Abbreviations, Address, Citation, Direction
NRM groups can reference source guidance consistently.
Landcare Australia[email protected]
Master Brand Guidelines 2024 is cited as a source document.
This sentence demonstrates bidirectional override.
Lists
- Use unordered lists for related points without sequence.
- Keep list items parallel and short.
- Use ordered lists for steps or ranked sequences.
- Start with the action, then add context.
- Design token
- A named value used across documentation, CSS, templates, and applications.
- Group fork
- A downstream repository that customises approved group variables while inheriting protected brand rules.
Tables
Tables are part of the typography system because they depend on labels, alignment, spacing, line weight, and scan order. Use them when readers need to compare structured information, not as a substitute for normal paragraphs.
| Table element | Guidance |
|---|---|
| Headers | Use Open Sans, uppercase only for short labels, strong weight, and enough spacing to separate labels from data. Keep headings short and concrete. |
| Body cells | Use body small or compact body sizing. Keep text left aligned. Use sentence case unless the content is a code, token, acronym, or formal name. |
| Numeric data | Align numbers consistently. Right-align only when readers compare quantities down a column; otherwise keep the table simple and left aligned. |
| Rules and dividers | Use quiet horizontal rules and avoid heavy boxes around every cell. Let spacing and row rhythm do most of the work. |
| Section rows | Use section rows sparingly to group related rows, as in the typeface table above. They should clarify the structure, not add decoration. |
| Long tables | Allow horizontal scrolling on small screens. Do not shrink text below readable sizes just to force every column into view. |
| Accessibility | Use real table markup for data tables, keep headers meaningful, and avoid using colour alone to communicate status or meaning. |
Comparison Table
Use for comparing choices, rules, or available options.
| Use case | Recommended style | Reason |
|---|---|---|
| Public webpage | Open Sans body, clear section headers | Supports scanning and consistent brand implementation. |
| Event flyer | Display title, short body copy, quiet captions | Keeps the first read strong without crowding the page. |
| Governance note | Body small with clear labels | Helps dense information stay readable and auditable. |
Specification Table
Use for tokens, sizes, spacing, and technical values.
| Token | Value | Use |
|---|---|---|
--lds-type-body-font-size | 16px | Default screen body copy. |
--lds-type-caption-font-size | 13px | Captions, source notes, and compact annotations. |
--lds-type-eyebrow-letter-spacing | 0.08em | Short metadata labels only. |
Sectioned Table
Use when a small table needs internal grouping.
| Typeface | Role | Guidance |
|---|---|---|
| Primary Typefaces | ||
| Sari | Logotype | Restricted to approved brand-signature use. |
| Open Sans | Working family | Default for almost all typography. |
| Secondary Typefaces | ||
| Futura PT | Alternative | Use only for specific secondary design treatments. |
Type Tokens
The type table defines both digital CSS values and print reference equivalents. Online projects should use the CSS imports and classes above. Print designers should use the print columns as production reference information.
| Role | Typeface | Screen size | Print size | Screen line height | Print leading | Weight | Digital use | Promotional / print use |
|---|---|---|---|---|---|---|---|---|
| Display | Open Sans | clamp(56px, 8vw, 96px) |
54-88 pt |
0.96 |
0.96-1.0 |
800 |
One major first-read statement on documentation landing pages, campaign posters, social tiles, report covers, or high-level section openers. Use Open Sans to keep the brand system consistent and avoid diluting the logotype. | Campaign headline, poster title, major social tile statement, or first-read cover message. |
| H1 | Open Sans | clamp(48px, 6.5vw, 84px) |
40-60 pt |
0.98 |
0.98-1.05 |
800 |
Page, template, campaign, or artefact title. Use once per composition where possible. Use Open Sans for normal headings and titles. | Primary page, flyer, report, or template title. |
| H2 | Open Sans | 24px |
22-30 pt |
1.12 |
1.08-1.15 |
800 |
Major section heading. Use Open Sans for clear structure and consistent production across web, print, and applications. | Major section heading in posters, flyers, reports, signage, and multi-panel layouts. |
| H3 | Open Sans | 18px |
15-20 pt |
1.2 |
1.15-1.25 |
800 |
Subsection title, card title, rule block title, or artefact heading. | Subheading, card title, callout heading, or supporting module title. |
| Lead | Open Sans | 21px |
16-22 pt |
1.45 |
1.25-1.4 |
500 |
Opening summary under H1. Keep to one or two short sentences. | Introductory copy, campaign summary, deck opener, or short poster explanation. |
| Body | Open Sans | 16px |
9.5-11 pt |
1.62 |
1.35-1.55 |
400 |
Default reading text for documentation, promotional body copy, governance notes, artefact descriptions, and application copy. | Readable body copy for flyers, brochures, reports, forms, and longer promotional text. |
| Body Small | Open Sans | 14px |
8-9 pt |
1.5 |
1.3-1.45 |
400 |
Dense metadata, helper copy, long table cells, and compact UI descriptions. | Dense notes, disclaimers, partner information, print metadata, and compact template copy. |
| Caption | Open Sans | 13px |
7.5-8.5 pt |
1.35 |
1.25-1.4 |
600 |
Image captions, source notes, colour details, compact annotations, and print credits. | Captions, image credits, source notes, and small annotations. |
| Eyebrow / Metadata | Open Sans | 11px |
7-8 pt |
1.2 |
1.1-1.25 |
800 |
Navigation labels, metadata headings, short status labels, campaign categories, and source categories. Use sparingly. | Short metadata, campaign category, date/location label, or template section marker. |
| Brand Logotype | Sari | not for general text setting |
use approved logo artwork and minimum-size rules |
not applicable |
not applicable |
Regular or Bold as supplied in official artwork |
Restricted brand logotype role. Use Sari only in approved logo artwork, official lockups, or specifically approved brand-signature treatments. | Logo, wordmark, approved lockup, or rare brand-signature treatment only. Do not use as a general heading, campaign headline, or body face. |
| Button / Action | Open Sans | 14px |
9-11 pt |
1.2 |
1.1-1.25 |
700 |
Primary and secondary actions in documentation, tools, and application UI. | Call-to-action labels, QR-code prompts, sign-up links, and action panels. |
| Code | Monospace | 0.92em |
8-9 pt |
1.45 |
1.3-1.45 |
600 |
Paths, generated token names, CSS variables, and short technical references. | Technical references, CSS variables, repository paths, and implementation notes. |
Typesetting Principles
- Use Open Sans for display titles, H1s, headings, sub-headings, body copy, captions, UI, documentation, and practical promotional design.
- Reserve Sari for approved logotype, wordmark, lockup, and logo-related work.
- Avoid using Sari for general headings, campaign headlines, page titles, body copy, buttons, captions, or repeated template text.
- Use Futura PT as an optional secondary design face, not as the default body or governance face.
- Use Calibri only for Microsoft Office and system-fallback situations where Open Sans is unavailable.
- Use scale, weight, spacing, and alignment before adding colour.
- Keep documentation, print templates, and campaign layouts flush-left and rag-right unless a specific composition requires otherwise.
- Do not justify body text; it creates uneven spacing and makes sustained reading harder.
- Keep body text to a readable measure of roughly 65 to 78 characters on screen, or an equivalent print measure.
- Use uppercase eyebrow or metadata labels only for short labels.
- Use tables for comparison and structured data, not decorative page layout.
- Keep table text readable; do not shrink content below practical reading sizes to fit more columns.
- Use quiet rules, clear headers, and consistent alignment so tables can be scanned quickly.
- Reserve Display and H1 styles for true first-read messages.
- For posters and social tiles, increase scale but preserve the hierarchy relationship between display, heading, lead, body, and caption.
- Use bold keywords to support scanning in learning materials, but avoid bolding whole paragraphs or too many words in one section.
For education-specific text patterns, see Accessibility and its Universal Design for Learning guidance.
Source: Font Brand Guidelines LA 2024, pages 1
Source: Master Brand Guidelines 2024, pages 14, 26, 39, 51, 64, 96, 108, 122