Practical Brand System
Catalog the work. Use the right asset fast.
This site is the publishable applications layer for the Tech Ops PH brand guide. It translates the
canonical brand book into a browsable operating surface for decks, documents, social, business cards,
merchandise, and export-ready collateral.
24+
approved templates and native source files registered in the current production pack
9
application families covering website, social, decks, documents, identity, and print
1
front door for finding what to use without digging through the repo structure first
Quick Route
Jump by output, not by guesswork.
Use the family routes when you already know the kind of asset you need. Use search and filters when you are comparing options across the full system.
Public Surfaces
Website framing, profile copy, proof, and public narrative.
Social And Campaigns
Banners, tiles, carousel storytelling, and scan-fast graphics.
Decks And Documents
Capabilities decks, proposals, one-pagers, and controlled PDFs.
Contact And Print
Business cards, email signature, merch, and handoff assets.
Identity And Platform
Lockups, wordmarks, favicons, and compact production assets.
Download Packs
Grab grouped ZIP bundles when you want a clean family handoff fast.
Current State
What this surface is for
The brand-definition layer is already locked in Markdown. This site focuses on application: what each
branded output is, where it lives, which file to start from, and which rendered asset is already ready
for direct use.
Canonical references
- Brand rules still live under
docs/brand-book/.
- This page is the browseable applications layer, not a replacement for the written guide.
Production bias
- Every card points to the real approved template or export path.
- Tools, platforms, and mockups stay secondary to operational use.
Selection rule
- Use exports when the deliverable already exists.
- Use templates when a new branded asset needs to be created cleanly.
Application Families
Browse the production catalog
Each card combines purpose, preview direction, template source, and direct-use assets where they already exist.
- Lead with operational problems, systems implementation, and proof categories rather than generic agency claims.
- Use the canonical naming and service stack before platform or tool detail.
- Use one operational promise plus one support line at most.
- Keep profile-photo crop zones and mobile crop zones clear.
- Use short statements, not long consulting paragraphs.
- Square and carousel layouts should remain clear under fast-scanning conditions.
- Use the deck to explain the operating problem, intervention model, and proof structure clearly.
- Keep slides executive-friendly, but anchored in workflow and implementation reality.
- Use paper-led reading surfaces with restrained green accents and quiet footer identity.
- Proposals should feel structured and accountable, not promotional.
- Keep the front contact-led and the back support-led.
- The QR exists to remove friction for contact capture, not to dominate the front face.
- Use one mark, one URL, and only the necessary contact fields.
- Avoid stacked badges, banners, or descriptor clutter.
Proposal
No catalog cards match the current search or filter. Clear the search or switch back to a broader filter.
Pack Downloads
Grab the family bundle directly
Use zipped packs when you need the current approved family files together without navigating the repo structure first.
Public Narrative
Public brand surfaces pack
Core strategy, naming, service, proof, and application chapters for public-facing use.
Social
Social and campaigns pack
Banners, campaign templates, and carousel defaults in one handoff bundle.
Sales And Delivery
Decks and documents pack
Deck themes, proposal cover, letterhead, SOW, invoice, and one-pager defaults.
Contact And Print
Contact handoff pack
Business cards, QR/vCard assets, email signature, and merch starter files.
Identity
Identity and platform pack
Current lockups, wordmarks, icon assets, favicon, and app-icon entry points.
Mini Site
Browse by family, not just by card
These pages group the catalog into fuller operational slices with guidance, downloads, and the right next step.
Guide
How to use the brand
Start here if you need to decide which asset family to use or which rule applies.
Public Surfaces
Website and public-facing narrative
Use this for profile copy, service framing, proof logic, and public brand surfaces.
Social
Headers, campaigns, and shareable graphics
Use this for banners, square layouts, and LinkedIn carousel storytelling assets.
Sales And Delivery
Decks and documents
Use this for proposals, SOWs, decks, invoice covers, and one-pager surfaces.
Contact
Business cards and print handoff
Use this for QR cards, email signature, proposal cover, and merch extensions.
Identity
Logos, favicons, and compact platform assets
Use this for the production pack, lockups, wordmarks, app icons, and favicon surfaces.
Operating Pattern
How to use the catalog without creating drift
The system should help you move faster, but only from approved sources and with the right escalation path.
1. Start with the need
Choose the actual channel first: deck, proposal, banner, document, card, social post, or print item.
2. Pick the default
Use the approved template or direct-use export linked from this catalog before creating anything custom.
3. Check the rule page
Use the brand-book application and voice chapters when copy or hierarchy decisions become unclear.
4. Register new defaults
If a new asset becomes the standard, add it to templates/ or assets/ and log it in the book.
Source Of Truth
Linked references
Use these supporting surfaces when a question is about rules, not just file selection.