Target Architecture

Target view

flowchart LR
    S[Travel product sources]
    T[Transformation / indexing workflow]
    M[(Meilisearch index)]
    W[Webflow Deals experience]
    A[Administrative tooling]
    B[Controlled backend]

    S -->|source product data| T
    T -->|normalised documents| M

    W -->|query + filters + sort + page| M
    M -->|hits + facets| W

    A --> B
    B -->|privileged index operations| M

Responsibilities

Source systems

Remain authoritative for travel product information.

Transformation / indexing workflow

Converts source records into a stable search-oriented representation and manages index updates.

Search index

Owns query execution, faceting, filtering, ranking, sorting and pagination.

It is a derived projection and must be reproducible from source data.

Webflow

Owns layout, interaction, responsive behaviour and presentation of results.

It consumes the search contract rather than the source-system model.

Administrative tooling

Provides controlled visibility and management of indexes and settings without exposing privileged credentials to public clients.

Information model

The indexed representation contains only fields needed for discovery and presentation, such as:

• reference and URL/slug;
• operator;
• destination;
• departure point;
• date;
• duration;
• price-from;
• countries;
• travel types;
• other search/filter attributes.

The target architecture therefore introduces an explicit information boundary between operational source data and customer search.