culture happens when we're together.

These guidelines define the identity, voice, and production constraints for VIVA PHX. Use them as the framing for all assets developed in relation to the festival. If something is missing or ambiguous, request it through the contact process below.

0. Intro

Background & how to.

0.1 How to use this hub

  • Assets are linked in the footer and throughout the page. For motifs, logos, and palettes: click the asset to open its download panel.
  • Automation scripts (where applicable) are linked in the footer. These are optional, not required.
  • Use this hub as the framing for any VIVA PHX-related production. When in doubt, request clarification before shipping.

0.2 Background

VIVA PHX is an annual cultural festival built on gathering in Downtown Phoenix, to create and celebrate culture, music, food, art, and spend time together.

VIVA PHX frames culture as more than content delivered to an audience. It is a relational system produced through shared time, movement, and proximity. The festival is not a single stage or single event. It is a network: artists, venues, and audiences forming a temporary circuit across Downtown Phoenix. For six days, the city becomes programmable.

1. Identity

Logo system, typography, color tokens, and graphic language.

Identity primitives

  • Single typeface: TT Neoris Variable
  • Hierarchy via scale and weight, not stylistic variation
  • Strict baseline and column grid alignment
  • Approved colorways only

Fast checks before you export

CheckPass criteriaReference
Grid Elements snap to baseline multiples of 12px and align to the column grid. 1.2.3
Logo No distortion, no recolor beyond approved colorways, clear space preserved. 1.1
Type Sizes follow the defined spine; weights match the allowed tiers. 1.2
Contrast Text/background pairing stays readable and consistent with the system. 1.3

1.2 Typography

Typeface specification

TT Neoris Variable is the sole typeface of the VIVA PHX identity. Hierarchy is expressed through size and a single axis: weight.

The system uses flush alignment, tight spacing, and scale as the primary organizational tool. Decoration comes from weight and ratio, not additional typefaces.

Licensing note: the typeface cannot be redistributed via the hub. For web use, host licensed files locally. For vendors without a license: request outlined type from production.

Weight tiers

TierWeightUse
Soft440Labels, kickers, de-emphasized text
Default560Body text, secondary tiers, running text
Strong700Primary headings, top-tier names, display

Tracking: display -0.01rem (Illustrator: -12). Body/meta 0rem (Illustrator: +12 for very small if needed).

Type scale

Baseline unit: 12px. The spine uses multipliers of 2 and 3 only: 12, 24, 48, 96, 192, 384 with intermediate steps 18, 36, 72, 144.

StepSizeRoleWeightTrackingLeading
012pxMeta / labels5600rem12px baseline
118pxMinor headings / callouts560-0.01rem24px baseline (tight)
224pxKicker440-0.01rem24px baseline
336pxSection headings700-0.01rem48px baseline
448pxDisplay700-0.01rem60px baseline (tight)
572pxHero / poster tiering700-0.01rem84px baseline
696pxHero700-0.01rem108px baseline
Rule align leading to 12px multiples Rule reduce tracking as size increases Rule hierarchy via ratio

1.2.3 Typographic grid system

Baseline unit: 12px. Default layout uses a 12-column grid. Gutters: 12px. Minimum margin: 12px (scale up by multiples of 12).

Extended layouts can use a 24-column grid as a direct subdivision of 12 (each 12-col column equals 2 units in the 24-col grid). Use 24 when you need half-column offsets or finer asymmetric placement.

:root{
  --baseline: 12px;
  --cols: 12;     /* collapses via media queries */
  --gutter: 12px;
  --pad: 24px;    /* multiples of baseline */
}

1.3 Color

Primary color tokens

--color-offwhite
#e6e7e8offwhite
--color-light-grey
#cdcdcdlight-grey
--color-orange-grey
#a4a4a4orange-grey
--color-orange
#f58a4forange
--color-mid-grey
#666666mid-grey
--color-maroon-grey
#272727maroon-grey
--color-maroon
#660333maroon
--color-black
#241f21black

Light / dark mappings

These variables drive the UI and serve as the reference for web production tokens.

/* Light */
--bg-primary: var(--color-offwhite);
--bg-secondary: var(--color-light-grey);
--bg-accent: var(--color-orange);
--bg-accent-muted: var(--color-maroon);

--text-primary: var(--color-black);
--text-secondary: var(--color-maroon-grey);
--text-tertiary: var(--color-mid-grey);

/* Dark */
--bg-primary: var(--color-black);
--bg-secondary: var(--color-maroon-grey);
--text-primary: var(--color-offwhite);
--text-secondary: var(--color-light-grey);
--text-tertiary: var(--color-orange-grey);

Greys as tonal matches

The greys are not “neutrals”; they’re tonal counterparts to the chroma colors to keep motifs from fighting typography.

  • Maroon Grey is the b/w version of Maroon
  • Orange Grey is the b/w version of Orange
  • Mid Grey is the mathematical average of Maroon Grey and Orange Grey

Export / swatch files

Swatches + tokens
01-identity/color/

1.4 Graphic language

Motifs and patterns

Voronoi pattern system (SVG/PNG) and usage rules. Use motif tokens so motif contrast stays intentionally low, this way the voronoi background doesn't interfere with typographic contrast.

Voronoi motif files
01-identity/graphic-language/voronoi/

Generative / parametric tools

Interactive generator for producing voronoi texture elements, so that repetition of the same voronoi shapes is limited.

Voronoi generator
01-identity/graphic-language/generator/

Usage constraint

  • Motifs should not compete with primary typography. Default to low-contrast motif tokens.
  • Motifs function as atmosphere and structure, not illustration.
  • When the layout is dense (lineups, multi-tier listings), motif contrast should be reduced further or removed.

2. Voice & messaging

Verbal identity, language principles, and boilerplate copy for reuse.

2.1.1 Tone

VIVA PHX is confident, thoughtful, and serious.

Default direct Default grounded

2.1.2 Language principles

Approved framing

  • Center Phoenix: use “Phoenix” or “Downtown Phoenix” as the subject of sentences wherever possible.
  • Use connection terms: connection, culture, communication, sharing, relation, cooperation.
  • Fallback line: culture happens when we’re together.

Prohibited framing

  • Avoid colonial language: “takes over”, “conquers”.
  • Avoid framing as solely a music festival; it’s broader cultural production and connection.
  • Avoid consumptive language; foreground relationship and proximity.

2.1.3 Boilerplate copy

Short

VIVA PHX is an annual cultural festival built on gathering in Downtown Phoenix, to create and celebrate culture, music, food, art, and spend time together.

Why support VIVA PHX?

VIVA PHX connects local culture with national attention. Independent artists, established acts, scenes, audiences, and partners converge across a curated set of venues. The result is density, discovery, and measurable cultural impact.

Why multi-venue and multi-day?

Culture doesn’t happen in isolation. It builds in clusters, scenes, and neighborhoods over time, together. The multi-venue model preserves local identity while increasing exposure. It enables organic discovery and lets artists plug into a broader ecosystem without losing context.

2.2 Naming conventions

Correct name usage, sub-event naming patterns, and Base definitions.

Brand name usage

  • Always set the name as VIVA PHX in all caps.
  • Use full name wherever possible.
  • “VIVA” alone is acceptable only infrequently in long body text; never in headlines or headers.
  • PHX should appear whenever possible (the project is about Phoenix).

Programs

  • Arts events: DEEP TIES

5. Assets & downloads

Naming conventions, directory structure, section bundles, and the full kit ZIP.

5.1 File organization

Naming convention: {brand}_{asset}_{variant}_{colorway}.{ext}

  • kebab-case for nonsemantic separation (replacing spaces)
  • underscores for semantic separation (brand vs asset vs variant vs colorway)
  • Example: viva-phx_logo_primary_negative.svg
viva-phx-brand-kit/
├── 01-identity/
│   ├── logo/
│   │   ├── primary/
│   │   ├── alternate/
│   │   └── co-brand/
│   ├── typography/
│   ├── color/
│   └── graphic-language/
│       ├── voronoi/
│       └── generator/
├── 02-voice/
└── 05-assets/
    └── viva-phx_brand-kit_full.zip

Per-section bundles

01 Identity bundle (ZIP)
05-assets/viva-phx_identity_bundle.zip
Graphic Language bundle (ZIP)
05-assets/graphic-language.zip
Color bundle (ZIP)
05-assets/color.zip
Logo bundle (ZIP)
05-assets/logo.zip

Full kit

Single downloadable archive containing the complete directory structure and all assets.

VIVA PHX brand kit (full ZIP)
05-assets/viva-phx_brand-kit_full.zip

6. Meta

Versioning, changelog, and contact process.

6.1 Version & changelog

Current versionv01.04.00
Last updated2026-03-04

6.2 Contact

Creative Direction & Design Questions?

max@eros-works.com

Requests

  • Missing assets or format conversions
  • Approval on non-standard applications
  • Outlined type requests for vendors without TT Neoris licensing