01
01 / Experience
Entry by intent
- 01.01
Services and industries
- 01.02
Products and portfolio
- 01.03
Articles, audit, calculator
Rise.sk · Company website
A website that grew with the company.
Rise.sk evolved from a motion experiment into a six-language system for services, products, content, and business journeys. This story explains why it changed and what can transfer to client software.
- Evolution
- 2025 to present
- Localization
- 6 languages
- Status
- Living product
RISE.SK / USER FLOW
One journey does not fit every visitor
Four entry points converge into one path from intent through proof to contact.
- ENTRY 01
Service
- ENTRY 02
Product
- ENTRY 03
Portfolio
- ENTRY 04
Article or tool
- 01Intent
Recognise the situation
- 02Proof
Show comparable work
- 03Definition
Try an audit or calculator
- 04Context
Carry intent into contact
- 05Learning
Observe and adjust
↺
Measurement returns to the next version’s backlog.
Layered progress, not one redesign
Five milestones trace the path from a motion experiment to today’s system.
- 01
06/2025
The first working story
- 02
08-11/2025
Interactions as a laboratory
- 03
01/2026
A production foundation
- 04
04/2026
From website to product platform
- 05
07/2026
Proof before effect
RISE.SK / V1 → V2
The first version versus today
Drag the divider to compare the motion-first landing page with today’s evidence-led version.
Drag to compare
- Version 1
- 04/2026
- Version 3
- 07/2026
RISE.SK / SYSTEM MAP
An architecture that holds story and operations together
Four layers connect the visitor, application, content, and production operations.
- 0202 / Application
One product foundation
- 02.01
Next.js App Router
- 02.02
next-intl · 6 languages
- 02.03
Design system and motion
- 02.01
- 0303 / Content and contact
Evidence becomes context
- 03.01
Typed data · MDX · Keystatic
- 03.02
Form · chat · booking
- 03.03
EmailJS and consented analytics
- 03.01
- 0404 / Operations
From change to healthy production
- 04.01
GitHub Actions and tests
- 04.02
Docker standalone · Nginx
- 04.03
Hetzner · Cloudflare · health
- 04.01
Technology stack
- Next.js App Router
- TypeScript
- Tailwind CSS
- next-intl
- Framer Motion
- Keystatic
- Vitest
- Playwright
- Google Tag Manager
- Microsoft Clarity
A process that transfers to client software
Six steps keep the same rhythm across a website, portal, or internal product.
- 01
Understand
- 01
Map real questions
- 02
Separate the main paths
- 01
- 02
Build
- 03
Prototype the risk
- 04
Build one shared system
- 03
- 03
Verify
- 05
Measure the paths
- 06
Revise from evidence
- 05
The domain changes. The way we decide does not.
A similar goal, built around your needs
