Skip to content
Case study · Media and communities

Global regenerative network: explaining a complex ecosystem in two languages and connecting its members

For a global regenerative network, KINTO built a bilingual site with an auto-linked glossary and navigable long documents, and a pilot app that uses AI to match what each member offers with what another needs.

By KINTO · Published

Figures, each with its source

  • over ten

    bilingual ecosystem pages

    Measured

  • over ten

    auto-linked glossary terms

    Measured

Ranges or orders of magnitude where a figure could identify the client, each with its source.

How the transformation unfolded From the problem to what changed, in the five steps every KINTO case follows.
  1. Problem

    An ecosystem with many parts (several initiatives under one network) needed one presence that explains a complex proposition, with long vision documents, in two languages and editable by a non-technical team.

  2. Signals

    Four signals: market, business, user experience and support.

  3. How we understood it

    We read the ecosystem’s master documents and the team’s corrections, and took an inventory of the pages and of the ecosystem’s own terms that the audience does not know.

  4. What we built

    A bilingual site with ecosystem pages that render long documents with a navigable table of contents, a blog, a glossary that auto-links every term across the site and a Git-based CMS, plus a pilot AI matchmaking app with passkey login and invitations.

  5. Transformation

    From zero to a bilingual site of more than ten ecosystem pages with a blog and glossary and fixed cross-language navigation; the app went from a static prototype to a deployable service.

Before and after, by dimension Editorial levels from 0 to 4 read from the text of this case, never a figure drawn to scale.
  • Web presence

    Before

    None (level 0 of 4)

    After

    Bilingual ecosystem site (level 4 of 4)

  • Language navigation

    Before

    Broken, orphaned pages (level 1 of 4)

    After

    Fixed across languages (level 4 of 4)

  • Ecosystem terms

    Before

    Unexplained (level 1 of 4)

    After

    Glossary auto-links them (level 4 of 4)

  • Member connections

    Before

    Left to chance (level 1 of 4)

    After

    Pilot app, deployable (level 2 of 4)

The four signals we read What the market, the business, the user experience and support were saying before KINTO built anything.
  • Market

    A global community with members from several continents.

  • Business

    The proposition only makes sense if it can be explored in depth.

  • User experience

    Broken navigation when switching languages and orphaned pages in earlier versions.

  • Support

    Connections between members depended on chance.

How the site was shaped
  1. Master documents And the team’s corrections
  2. Inventory Pages and unfamiliar terms
  3. Site and glossary Long documents, navigable
  4. Pilot matching app What members offer and need

Connections

  • Master documents → Inventory
  • Inventory → Site and glossary
  • Site and glossary → Pilot matching app

For a global regenerative network, KINTO built a bilingual site with an auto-linked glossary and navigable long documents, and a pilot app that uses AI to match what each member offers with what another needs.

Problem

An ecosystem with many parts (several initiatives under one network) needed one presence that explains a complex proposition, with long vision documents, in two languages and editable by a non-technical team. And its members could not find each other: connections depended on chance.

Signals

  • Market: A global community with members from several continents.
  • Business: The proposition only makes sense if it can be explored in depth.
  • User experience: Broken navigation when switching languages and orphaned pages in earlier versions.
  • Support: Connections between members depended on chance.

How we understood it

  • Reading the ecosystem’s master documents and the team’s corrections.
  • Inventory of the pages and of the ecosystem’s own terms that the audience does not know.

What we built and why

  • Bilingual site with ecosystem pages that render long documents with a navigable table of contents, a blog with search and related posts, a glossary that auto-links every term across the site, a team page and a Git-based CMS.
  • AI matchmaking app (pilot): enriches each person’s profile from what they offer and need and matches it against the whole ecosystem; access through passkeys and invitations.

Why this way: An ecosystem with its own vocabulary is only understood if each term is explained where it appears, which is why the glossary automatically links every term across the whole site.

Transformation

  • From zero to a bilingual site of more than ten ecosystem pages with a blog and glossary, and fixed cross-language navigation.

  • The app went from a static prototype to a deployable service.

  • bilingual ecosystem pages: over ten (measured)

  • auto-linked glossary terms: over ten (measured)

What we don’t know yet

  • Real users, matches generated and results: no evidence.
Case studies

Related case studies

Fintech and crypto

Agentic websites

Fintech and crypto: websites where trust is built with clarity, not promises

Several fintech and crypto companies in Latin America and the US received bilingual sites from KINTO with segment landing pages, extensive FAQs and a layer that helps generative search engines cite them correctly.

Latin America, United States Read the case study

Have a problem like this?

Tell KINTO what is going on. The first conversation is to understand it, not to sell.