Public Surfaces
Website, profile, and market-facing brand system
Use this for homepage framing, proof language, and public-facing service structure.
Operating Pattern
Choose the right surface. Start from the approved default.
The brand system is meant to speed up real work, not create another layer of indecision. Use this page to decide which branded surface to reach for, which rules matter most, and when to escalate from a direct-use export to an editable template or a new cataloged default.
Rule 1
Start with the actual use case, not the tool or platform.
Rule 2
Use the export when the deliverable already exists; use the template when it must be personalized.
Rule 3
If a new variation becomes the repeated default, register it in the catalog and docs.
Selection Rules
Use the system in this order
Move from need, to approved asset, to template, to new default. Skip unnecessary invention.
1. Identify the channel
Pick the actual surface first: website copy, social banner, deck, document, proposal, card, or print item.
2. Check for a direct-use export
If a production-ready PNG, PDF, or DOCX already exists, use that before opening a template.
3. Open the default template
When personalization is required, start from the registered HTML, DOCX, PPTX, or source file.
4. Register any new standard
If a new variation will be reused, add it to the catalog, approved deliverables, and changelog in the same pass.
Channel Map
Which asset family fits which need
Use this map when the question is “where should this live?” rather than “what does the rule say?”
| Need | Default family | What to prioritize |
|---|---|---|
| Profile headers and personal/company presence | Social and campaign surfaces | Short promise, crop safety, immediate recognizability. |
| Client-facing narrative and capabilities | Deck and document system | Operational clarity, proof structure, restrained hierarchy. |
| Contact exchange, networking, handoff | Contact and print surfaces | Fast capture, low friction, print-safe execution. |
| Logo use, avatars, favicons, app icons | Identity and platform assets | Correct file variant, spacing, compact readability. |
| Public website or company-facing branded surface | Public brand surfaces | Service architecture, proof categories, market-facing naming. |
Rules That Matter
Apply the definition layer while you build
Every application should still reflect the same brand logic. The channel changes; the underlying system does not.
Language
- Lead with operations, systems, implementation, visibility, and adoption.
- Use the market-facing name
Tech Ops PHconsistently. - Use the descriptor selectively on high-context surfaces, not everywhere.
Visual hierarchy
- Prefer quiet, purposeful layouts over decorative density.
- Let green support hierarchy; do not let it overwhelm the page.
- Keep logo use restrained and only as strong as the surface needs.
Detail Pages
Go deeper by asset family
These pages group the production system into browsable operational slices.