Brand Center Hotel Vieiras

Brand portal · Design System2026

One place to understand and apply the Hotel Vieiras identity, with organised guidelines, examples and approved files.

Web · desktop and mobile

Hotel Vieiras Design System on desktop and mobile, with the wave pattern and blue identity — Composition of real screens on desktop; Design System capture on mobile. Local environment · 5 October 2026.

The challenge

One brand. A consistent reference.

Identity guidelines needed to stay consistent across documents, the interface and instructions for agents. The Brand Center organises that knowledge in a portal: partners, suppliers, press and staff can find brand foundations, application examples and files, with a clear separation between public and internal content.

How it works

Understand. Apply. Find the file.

Three paths organise the experience. The Brand Book presents the history, personality and tone of voice. The Design System translates the identity into guidelines and visual examples. The Downloads library groups materials by category, version and format.

Understand the brand
Check the guideline
Choose the version
Get the file

Desktop interface / swipe to inspect

Brand Book · foundations before application · local capture from 5 October 2026.

The product in use

From identity to everyday application.

The 15 Design System sections cover logo construction and clear space, colour, typography, composition, components, graphic patterns and pictograms. A table of contents and section anchors help people reach the guideline they need without reading the entire guide.

Design System · real product in a local environment · 5 October 2026.

The reference visual identity is credited to Feitoria in the project documents. The portal organises its application.

Approved files

The right version, in the format you need.

Categories, search and filters help locate brand signatures, patterns, seals and documentation. Each group presents variants and formats. The library also includes approved institutional photography and video, with previews and quality options.

Downloads · brand versions by colour and format · local capture from 5 October 2026.

Staff tools

A public reference. Internal work with context.

The staff area adds planning and utilities to brand reference. Access is separate from public pages; these features are presented here through their documented scope, without exposing internal screens or data.

Institutional calendar

Month, week and day views, search and filters. Recurring dates and confirmed schedules are handled separately, with a distinct adjustment layer.

Email signature

Professional details populate a standardised preview that can be exported as a PNG or JPG image.

Knowledge for agents

The same guidelines for people and tools.

AI tools can consult public brand guidelines as structured data. The API and local MCP share that reference and provide read-only access. An agent index and text search help locate traceable public content.

Guidelines and files
Structured public data
Portal · API · local MCP

A shared reference

Contracts and validations check consistency between data consumed by the interface and by agents.

Queries with a defined scope

The MCP runs locally and queries public content. The documented layer provides reading and text search, without claiming AI generation.

Engineering and decisions

Organised content. Layers with clear responsibilities.

React, TypeScript and Vite form the interface. Server functions handle identity and authorised operations; database and storage support adjustments and files. This diagram summarises the components documented in the code.

Keep the portal foundation

Vite was retained alongside Vercel Functions: adding an API did not justify migrating the interface.

Prose and contracts

Documents hold editorial guidance; typed modules and schemas structure public data for queries and validation.

Purpose-specific access

Auth.js handles staff sessions. Neon Postgres and Drizzle support persistence; Cloudflare R2 serves files while preserving the separation between public and licensed collections.

Architecture: documents feed structured data shared by the portal and public queries; authorised services are separate — High-level documentary diagram · snapshot from 5 October 2026. It represents identified components, without certifying all cloud operations.

Delivery status

A reference portal. A foundation to evolve.

The October 2026 snapshot documents implemented public pages, a material library and internal calendar and signature tools. The portal has a public address; media management and broad administration remain partial. This case captures the local product without assuming full parity with production.

Stack

React · TypeScript · Vite · Vercel Functions · Auth.js · Neon Postgres / Drizzle · Cloudflare R2 · MCP SDK · JSON Schema / Zod

Next projectTREVOX LAB ↗