01 / Variables
Edit Colors, Typography and Layout in Webflow Variables. Base changes cascade down; override only the responsive mode that needs a different value.
Template system / 03
The shortest safe path to customize OBVIA while keeping responsive behavior, accessibility and motion intact.
Edit Colors, Typography and Layout in Webflow Variables. Base changes cascade down; override only the responsive mode that needs a different value.
Add projects in the Works collection. Complete every required field, write meaningful image alt text and keep SEO titles and descriptions unique.
Use landscape images at least 2400px wide for project heroes. Compress before upload and keep the monochrome or acid-accent art direction consistent.
The mobile menu is one interaction on the toggle: the first click opens it, the second closes it, and tapping any menu link closes it too. Edit it in the Interactions panel under “Open and close the menu when the toggle is clicked”.
Custom code runs one effect: the cursor photo trail in the hero. Every other reveal, hover, marquee and scroll sequence — the hero entrance and the word-by-word fills included — is a Webflow interaction with no code. The page loader is hidden by default so the Home page stays editable — see “The page loader” below.
Check all four responsive modes, keyboard navigation, reduced motion, CMS empty states and the Marketplace licenses page before publishing.
Page loader / 01
The black intro overlay on the Home page is hidden by default, so it never covers the canvas while you work. A Webflow interaction turns it on when the page loads, plays the intro and takes it away again — the whole thing runs in 1.15 seconds. There is no code involved.
The acid-lime hairline is the progress bar. It is a timed animation, not a real measure of loading, so nothing needs wiring up.
Interactions panel → Play the intro overlay and wipe it up on load. Six steps on one timeline, in seconds:
To make it longer, move the last two steps later and stretch the durations to match — keep the final Display: None step at or after the end of the wipe. Anything past about two seconds starts to feel like a wait, which is why it is set where it is.
Nothing else depends on it. The hero still plays its own entrance, because that is a separate interaction.
One small GSAP script runs a single effect: the photos that follow your cursor across the hero. Everything else on the site — the hero’s own entrance included — is a normal Webflow interaction with no code. Here is what the script does and how to take it out.
No code needed — these are ordinary Webflow images.
Use images that are already small — around 460px wide and well under 150 KB each. They load on every visit.
The feel of the trail is set by seven numbers in a SETTINGS block at the top of the script, on the Home page under Page settings → Custom code. Change one, save, publish. Times are in seconds.
A calmer hero: raise DISTANCE to about 140 and AMBIENT_INTERVAL to about 1.4. A busier one: drop DISTANCE to about 60.
Everything the script touches is inside the hero. Nothing else on the site is animated by code.
The cursor trail is gone and nothing else changes. The hero word still rises on load, the manifesto and about sentences still light up word by word, the menu still opens and every reveal still plays — all of that is built with Webflow interactions.