STON.fi

a multilingual Next.js website

I focus on the landing page's actual scope: three addressable language versions, working interactions and a client-supplied design, not exchange infrastructure.

Field
Web3
Built with
React / Next.js / SSR
English STON.fi landing-page design draft showing the swap product section and mobile interface.
Project detail

Related Figma landing-page draft from the project archive, not a live screenshot or verified record of current product terms.

The challenge

STON.fi needed a public website to explain its product to different audiences. The client supplied the design. The project scope was the landing page and its frontend behavior, not development of the exchange or its financial infrastructure.

The approach

The supplied layouts became React and Next.js pages with server-side rendering, modal windows, animation and an external API connection. The content was organized into language packages for three locales, with a separate URL for each version and a visible language switcher.

The project, in detail

The images show the interface and its context. Captions distinguish project archives from current-site views.

Languages as part of the structure

Each language package carries its own page content and metadata. Choosing a language changes the URL, making each version addressable and allowing titles and descriptions to be managed independently.

From design to functioning pages

The implementation covered the supplied layouts and interaction states, alongside the basic technical SEO work in the brief.

The work, up close

Illustrated platform feature cards in the client-supplied STON.fi design.
Project detail

Illustrated platform feature cards in the client-supplied STON.fi design. Original Figma project draft, not a live product screenshot.

The outcome

Delivery

A Next.js landing page with the supplied design and required interactions.

Localization

Three language packages with separate routes and a language switcher.

Details of STON.fi

What kind of website work was this?

The client-designed landing page had three addressable languages and working interactions; exchange infrastructure was outside the scope.