Summary
Brand applications show how the Opries system behaves in real materials. They should be logotype-led, structured, plain-spoken, and easy to scan, using the hollow coordinating marker, Eucalypt/Paperbark/Earth colour logic, Arial typography, open tables, and accessible hierarchy.
These examples are starting points for designed assets. They are not final artwork or print-ready production files.
Application Principles
| Principle | Application rule |
|---|---|
| Logotype first | Use the lowercase opries logotype as the main identity signal. Use the identifier only where space is constrained or as a supporting mark. |
| Structure before decoration | Use alignment, spacing, type hierarchy, and simple rules before adding colour or imagery. |
| Practical use | Every asset should help someone understand who Opries is, what it supports, and what action or context matters. |
| Accessible reading | Keep text left aligned, ragged right, high contrast, and readable in print and screen conditions. |
| Grounded colour | Use Eucalypt on light backgrounds and Paperbark on Earth for dark treatments. Use secondary colours for information and emphasis, not decoration. |
| Subtle motifs | Use contour lines, mono linework, coordinating points, register rows, or field-line motifs where larger materials need warmth and visual rhythm. |
Business Card
Business cards should feel restrained and useful. Use the logotype on one side and contact details on the other, or use a single-sided layout for low-cost printing.
| Element | Guidance |
|---|---|
| Size | Standard business card size for the local printer; allow bleed and safe margins |
| Front | opries logotype with hollow marker, centred or left aligned depending on layout |
| Back | Name, role, email, phone, website, and optional short descriptor |
| Colour | White or Paperbark background with Eucalypt logotype; Earth background with Paperbark logotype for a dark option |
| Type | Arial; name strongest, role/contact details smaller |
| Alignment | Prefer left-aligned contact details for scanning |
Sample copy
| Field | Example |
|---|---|
| Name | Alex Nguyen |
| Role | Program coordination |
| alex@opries.com | |
| Website | opries.com |
| Descriptor | Practical records and reporting for Landcare and NRM work |
Print Document
Use this pattern for proposals, board papers, grant reports, policy packs, and formal PDFs.
| Section | Guidance |
|---|---|
| Cover | Logotype, document title, short subtitle, date, status |
| Cover motif | Optional subtle contour-line field, coordinating points, register rows, or field lines |
| Header | Short document title or section name |
| Footer | Page number, date/version, document status if useful |
| Summary | One short lead paragraph explaining the document purpose |
| Body | Left aligned, ragged right, short paragraphs, clear headings |
| Tables | Open tables with horizontal row rules for text-heavy content |
| Captions | Small, clear captions under figures, screenshots, maps, or tables |
| Sources | Source notes placed close to relevant content |
Example cover hierarchy
| Level | Example |
|---|---|
| Logotype | opries |
| Title | Document Register Review |
| Subtitle | Records, approvals, obligations, and evidence prepared for committee review |
| Metadata | Draft · 13 June 2026 · Prepared for program coordinators |
Poster or Notice
Posters should work at a glance. They should use a strong title, one short summary, and a small number of clearly separated details.
| Element | Guidance |
|---|---|
| Title | One practical message, not a slogan |
| Summary | One short sentence that explains the point |
| Details | Three to five short items, not long paragraphs |
| Visual | Optional real image, simple identifier, or structured text-only layout |
| Motif | Optional mono motif or character cue to support hierarchy without acting as decoration |
| Action | Clear next step, date, location, or contact |
| Accessibility | High contrast, large type, readable from distance, no colour-only meaning |
Sample poster structure
| Area | Example |
|---|---|
| Title | Keep project records ready for reporting |
| Summary | Opries helps coordinators keep documents, approvals, dates, and evidence in one organised register. |
| Key points | Add records · Track obligations · Attach evidence · Export reports |
| Action | Review your document register before the next committee meeting |
Handout or Explainer
Handouts should teach one concept at a time. Use Universal Design for Learning: summary, example, steps, and check.
| Section | Example |
|---|---|
| Title | What belongs in the document register |
| Summary | The register keeps key records together so reporting and handover are easier. |
| Examples | Funding agreements, committee minutes, signed approvals, insurance records, acquittal evidence |
| Steps | Add name · Set owner · Add review date · Attach file · Confirm status |
| Check | Can someone find the latest approved version and supporting evidence? |
Checks
- Is the material logotype-led and recognisably Opries?
- Does the layout use structure before decoration?
- Can the reader understand the purpose quickly?
- Is the body copy left aligned and ragged right?
- Are captions, sources, dates, and status included where useful?
- Does the material work in print, screen, and low-quality reproduction?
- Are colour and symbols supported by readable text?