People and credibility
Team visibility route
The team route gives the public site a direct credibility layer. It keeps people visible without turning the page into a generic agency roster.
Overview
Project summary
A focused team page that makes the people behind the work visible fast. The route avoids agency filler and instead surfaces names, roles, personal sites, and LinkedIn profiles in a structure that can expand as Noliv grows.
- Status
- Published
- Period
- Spring 2026
- Effort
- Launch scope
- Route
- /the-team
- Format
- Public roster
- State
- Published
Technical notes
Context, implementation, and next work
The sections below keep the page readable as documentation: a short explanation followed by concrete notes.
Challenge
The site needed people context without bloated profile pages
Visitors should be able to understand who is behind Noliv quickly, with enough supporting links to verify credibility and continue exploring.
- Keep names, roles, and links visible without client-side dependencies
- Make the layout work for a small team now and a larger team later
- Avoid burying important people context behind decorative copy
Approach
A concise roster built from reusable content fields
The implementation favors structured entries: name, role, portrait, personal site, and LinkedIn. That structure can later map directly to CMS people records.
- Server-rendered roster content for crawlability
- Stable portrait dimensions to protect layout stability
- External profile links only where they add useful context
Next
Prepare the model for richer contributor records
The route can grow into fuller people records when the content exists, while keeping the public page direct and easy to scan.
- Add optional biographies only when they carry real context
- Support team grouping or role filters if the roster grows
- Reuse the same content shape in future CMS collections
Content model
CMS handoff notes
The page is still backed by local TypeScript records, but the data shape is intentionally close to a future CMS collection.
- People records can become their own CMS collection
- Project detail page can reference related people by ID later
- Route CTA remains separate from the project case-study URL