Vayasya Brand Handbook
Visual Reference
Specialist Reference
Reference-first typography page with the font pack, family roles, surface guidance, hierarchy, and release checks.
When to use this page
Use this page when you need the full family roles, surface mapping, and hierarchy detail behind the root quick chooser.
Specialist audience
Design, product, and engineering teams.
Approved font pack
Download the approved font package before working in design, product, or implementation files.
Family roles
Use live specimens to compare Anek for display, Hind for readable text, and JetBrains Mono for data.
Use by surface
Map decks, product UI, reports, exports, and data-heavy surfaces to the approved family roles.
Hierarchy and review
Check the specimen-led scale, technical values, and release checks before approval.
Assets and references
Vayasya Font Pack
Approved font files for design, marketing, and implementation teams.
Surface guidance
Approved mapping for decks, UI, reports, exports, and data-heavy surfaces.
Hierarchy examples
Specimen-led scale with technical size and line-height detail for release work.
Topic
Use the three approved families by role: display, readable text, and precision-heavy data.
Display family
Headings and high-emphasis hierarchy
Compliance-first industrial services
Use for hero lines, slide headlines, and section titles that need brand presence.
When to use: Page titles, hero headings, deck headlines, and other high-emphasis display moments.
Hard rule: Do not use Anek for long reading paragraphs or dense UI text.
Body and UI family
Reading, labels, and interface copy
Use Hind for the sentences people actually need to read, from emails and proposals to UI labels and helper text.
This is the default family for narrative copy, labels, and calm interface text.
When to use: Body copy, labels, UI text, summaries, email-like content, and long-form reading.
Hard rule: Do not switch away from Hind locally just because a file or tool is rendering badly.
Data family
Data, identifiers, and aligned values
WO-1842 24 technicians 09:30 IST PPE ok
Use where character distinction, tabular rhythm, and precise scanning matter.
When to use: Operational data, reports, IDs, table values, and code-like precision fields.
Hard rule: Keep mono out of narrative paragraphs and normal body copy.
Topic
Choose the type treatment by actual surface so decks, UI, reports, and exports stay aligned.
Operational clarity without visual noise
Pair a short Anek heading with Hind for supporting explanation.
Use: Anek for display headlines, Hind for the body and supporting narrative.
This keeps formal collateral readable without flattening the heading hierarchy.
Hard rule: Do not turn the entire slide or proposal page into display typography.
Status update available for review
Use Hind for nav, labels, helper text, and dense interface reading.
Use: Hind by default, with Anek used sparingly for hero or sparse headline moments.
Dense workflows need calm readability more than brand drama.
Hard rule: Do not pull display typography into working UI screens unless the surface is intentionally headline-led.
WO-1842 24 technicians 09:30 IST Completed
Use mono for aligned values and identifiers, not for the surrounding explanation.
Use: JetBrains Mono for values and IDs, Hind for context labels or narrative explanation.
Use mono where precise scanning helps the reader distinguish similar characters quickly.
Hard rule: Do not set the full report narrative in mono just because the surface includes data.
Use the approved font files before exporting final documents.
Keep the same family roles across editable docs and final exported outputs.
Use: Approved font pack with the same Anek, Hind, and Mono roles used in branded source files.
Exports should preserve the same hierarchy instead of silently dropping into office defaults.
Hard rule: Do not accept a fallback-ridden export just because the document still opens.
Topic
Use the specimen-led scale first, then confirm the technical size and line-height values in the matrix.
Display
40px / 48px
Compliance-first industrial services
Usage: Page titles and hero statements
Keep display text short, intentional, and clearly above the body layer.
Weight 600
H2
30px / 38px
Scope and compliance controls
Usage: Section headings and major deck transitions
Use this level to create structure, not to style every emphasized sentence.
Weight 600
Body
18px / 30px
Use Hind for the copy people actually need to read fully, from proposals to interfaces.
Usage: Primary long-form content and explanatory copy
Readable rhythm matters more than squeezing extra text into the same area.
Weight 400
Data
14px / 22px
WO-1842 | 24 technicians | 09:30 IST
Usage: Tabular values, IDs, and precise operational data
Use only where precision and character distinction materially help the reader.
Weight 500
| Level | Family | Weight | Size / line height | Usage |
|---|---|---|---|---|
| Display | Anek | 600 | 40px / 48px | Page titles and hero statements |
| H2 | Anek | 600 | 30px / 38px | Section headings and major deck moments |
| Body | Hind | 400 | 18px / 30px | Primary long-form content and explanatory copy |
| Data | JetBrains Mono | 500 | 14px / 22px | Data values, table content, and precise identifiers |
Topic
Use these execution checks to keep reading comfort, data precision, and product handoff aligned.
Use sentence case by default.
Sentence case keeps labels, helper text, and document copy calm and quick to scan.
Use: Approval owner Avoid: APPROVAL OWNER
Break dense paragraphs before they feel wide or tiring.
Readable paragraph rhythm matters more than trying to fit everything into one block.
Split long operational explanations into shorter paragraphs or labeled lines.
Reserve mono for values that need alignment or character distinction.
Mono adds precision in tables and identifiers, but reduces reading comfort in narrative copy.
Use mono for work order IDs, counts, timestamps, and table values.
Keep hierarchy jumps deliberate, not decorative.
One clear display layer and one calm reading layer is easier to scan than multiple styling jumps.
Use Anek for the heading, then let Hind carry the explanation underneath.
Topic
Use these checks before approving a branded surface or shipping a product implementation.
Move across the sibling specialist pages or return to the handbook root.
Logo Usage
Reference-first logo page for approved packs, master and vertical marks, placement rules, and misuse review.
Open topicColor Palette
Full copy-ready swatch wall for approved brand, semantic, chart, and alias colors.
Open topicImagery
Full imagery reference for sourcing, proof-first use cases, acceptability checks, and release guidance.
Open topic