v3.0.2 is out — restored design-system guidance and corrected navigation. Read the notes
projectious·work
On this page

Documentation

The projectious.work brand and design system — foundations, logo, interface patterns, collateral, and usage terms.

About this documentation

This documentation is rendered by the design system it describes. Every colour chip, type row, and code block on this site is produced from the same tokens the pages document.

The current contract is synchronized from design system v2.1.1. It applies to every brand surface: product UI, marketing, documentation, slides, email, terminal output, and portfolio material. The rendered UI mockups supplied with the system’s preview cards, UI kits, and slides are the visual reference when prose could be read more than one way.

Brand in one view#

  • Name: projectious.work — always lowercase; the dot is part of the name.
  • Positioning: Cloud · Agile · Agentic AI — agent-first consulting.
  • Tagline: Redesigning work.
  • Mission: Augment people’s strengths to improve life for everyone.
  • Vision: Humanistic ideals determine actions in an AI-completed world.
  • Voice: modern, composable, authentic, no-nonsense, agent-first, and humanistic.
  • Audience: technical leaders at European and international organisations adopting AI-native workflows.

The four convictions behind the system are: do more with more; specialized beats generic now; remain provider-independent; and run what we recommend.

Writing the brand#

Write like an honest principal engineer who has stopped trying to impress: direct, technical, humanistic, and restrained. Use plain words, short to medium sentences, and a confident claim instead of loud punctuation or marketing language. Treat agents as a normal part of good work rather than something to gush about.

  • Use sentence case except for proper nouns.
  • Use we for projectious.work and you for the reader; never I or the team.
  • Address the reader’s situation, not their feelings.
  • Join the practices with a middle dot: Cloud · Agile · Agentic AI, never an ampersand.
  • Use the middle dot for compact metadata too, and use spaced em dashes sparingly for asides.
  • Do not use emoji on a brand surface.
  • Use digits in technical contexts. In prose, spell out one through nine unless the number has a unit.

Stock lines, in priority order, are Cloud · Agile · Agentic AI, Redesigning work, and Agent-first consulting, built on what we teach.

Stock lines — use in this priority order
Cloud · Agile · Agentic AI Primary positioning line
Redesigning work Alternative campaign line
Agent-first consulting, built on what we teach Long-form descriptor

Where to start#

If you want to…Read
Use the palette correctly across all appearancesColour
Set text in the brand’s voiceTypography
Place the logo without breaking itLogo usage
Build an interfaceInterface
Produce a deck, signature, or social cardCollateral
Know what you are allowed to reuseGovernance
Pull the raw values into a projectTokens
See what the system includesFeatures
Implement it in a productDeveloper guide
Synchronize or release itMaintenance
Review shipped dependenciesSBOM

How the system is organised#

Foundations are the primitives — colour, type, spacing, shape, motion. Everything else composes from them.

Logo covers the mark, the four lockups, and the rules that keep them legible.

Interface applies the foundations to screens: components, code surfaces, appearances, icons, and forms.

Collateral covers the artefacts that leave the product — decks, cards, signatures, social imagery.

Governance covers licensing, trademark, the pre-launch legal assessment, and asset provenance.

Source of truth#

This site is the authoritative readable presentation of the supplied projectious.work design system. Values originate in the synchronized token sheet and src/data/brand.yaml; rendered specimens and mockups provide the visual acceptance reference. Code and tokens are MIT-licensed. The name, wordmark, and logo remain reserved brand marks.

Updated Aug 17, 2026