# A studio site with a planner built in.

> The website of Map It, built in Framer and extended with code components: a project planner, a guided map of how it works, and project pages drawn as maps.

- Sector: Studio website
- Year: 2026
- Project: Map It
- Client: Map It
- Design: Map It
- Development: Nuxsol
- Starting point: The Okapi template for Framer
- Live: https://map-it.framer.website
- Services: Development

Map It plans and runs digital work for companies, with specialists the client chooses. Its site had to show that way of working, not only describe it. Map It designed the site. Nuxsol built it in Framer and wrote the components that Framer does not provide.

## In the project

- Framer site for desktop, tablet and phone
- Project planner
- Guided map of how it works
- Project pages generated from content
- Canvas, frames and notes as components

## The problem

A studio that sells planning needs a site that plans. A list of services and a contact form would say what every other studio site says. Map It wanted a visitor to leave with something: a first plan for their own project.

Framer gave the team a site they can edit themselves, but its standard parts stop at pages, text and images. The planner, the guided walk through the process and the project pages laid out as maps had to be written.

## What we built

The site runs on Framer and started from the Okapi template. Its pages look like a design board, with frames, handles and notes. On top of that sit the code components we wrote. The largest is the planner on the home page, which takes a visitor from a starting point to a plan they can send. Project pages are generated from the content system, so a new project needs content, not a new layout.

## Who it is for

- The visitor with a project: Wants to know what it would involve before a first call.
- The Map It team: Edits pages and adds projects. Needs to do it without a developer.
- The visitor on a phone: Needs the same planner and maps on a small screen.

## What we did

### Development

Used: Front-end, Framer, React, CMS integration.

1. Build the pages in Framer: Home, work, services, about and journal, from the Okapi template, for desktop, tablet and phone.
2. Write the components: React code components for the planner, the maps, the canvas and its handles.
3. Connect the content: Projects, with their boards and steps, come from Framer’s content system.
4. Test and publish: Components are tested outside Framer first, then on the published site.

## Design decisions

1. Build on Framer, extend with code. The team edits text, images and projects themselves. Code is added only as components that sit inside Framer pages.
2. The planner comes first. “Draft your map” is the main button in the hero, and it leads straight to the planner.
3. Project pages come from content. Each project is an entry with its boards, steps and captions. The page, its gallery and its map are generated from that entry.
4. The page walks with the visitor. On the map of how it works, a note follows the scroll and names the step in view, so a long section reads as a sequence.

## How it works

1. Start: A visitor chooses one of three ways in: a consultation, a review of what they have, or a plan for what they need.
2. Your route: They answer in build order, and the plan builds up beside the questions.
3. Send: The plan goes to Map It as the brief for a first call.

## The principle

A site that plans, for a studio that sells planning.

## What it is built to change

- Plans drafted: A visitor who drafts a plan arrives at the first call with a brief. The number of plans sent is the measure.
- Edited without a developer: New projects and page changes are made in Framer by the team.
