From mocks to an API: the data contract

Resorts, branches, contacts and assets arrive through typed data snapshots. The current repository reads a local mock. Components receive data through a layer’s public export and do not choose a server endpoint themselves.

The knowledge base uses KnowledgeSnapshot, with KnowledgeRepository.read() as the source boundary. A separate backend replaces the read() implementation while retaining the snapshot structure.

interface KnowledgeRepository {
  read(): Promise<KnowledgeSnapshot>;
}

const snapshot = parseKnowledgeSnapshot(
  await knowledgeRepository.read(),
);

Validate the API response at the boundary: RU/EN locales, unique IDs and slugs, an existing category, safe links, dates and article-section identifiers. Invalid responses must not silently become invented information.

Models and repositories belong to entities. User workflows belong to features; page composition belongs to _pages and _app. Shared components and utilities do not import business entities from upper layers.

• Match the DTO to the local contract, including empty values and both locales.
• Check load failures and unknown identifiers.
• Use one snapshot for the page, metadata, JSON-LD and sitemap.
• Configure server-cache refresh after publishing or updating an article.
• Repeat search, direct links, language switching and offline reading of a visited article.

Materials and sources

• Interface patterns and data
• Zod — input validation