Framer websites designed and built so your team can add pages after launch
For teams that have chosen Framer, we design the site in Figma and build it in Framer, or build in Framer from a design file your designers have finished. Your Figma components become the parts every Framer page is assembled from, case studies and articles live in CMS collections your team edits, and motion appears where it shows the visitor something. Framer sites that are half built can be completed, and a WordPress site can be tested in Framer on a single page before you decide whether the whole site should move.
Norml works in Framer for companies that picked it as their platform. There are four ways in: we design and build the site, build from a Figma file your designers finished, design for your own Framer developer, or complete a site someone else began. Handover includes a guide to adding pages and collection entries.
What a Framer project can include
The starting point decides the order of work: a brief with no design yet, a finished Figma file, a Framer site in progress or a live WordPress site. The rows below are combined to fit that starting point.
Design in Figma before the buildWhen there is no design yet, the key pages are drawn in Figma around your real copy and work samples: screenshots, campaign images and results. We agree how each type of material is shown, for example full width, as a sequence of screens or side by side, and the approved sections become the components the build reuses.
01
Figma components rebuilt in FramerEach Figma component is rebuilt as one Framer component with the same name and variants, and auto layout becomes Framer stacks. Components are set up at the desktop, tablet and phone breakpoints, so a page your team assembles later uses the same parts instead of copies of old sections.
02
CMS collections your team editsCase studies, articles and other repeated content are stored as Framer CMS collections, with one field per section of the page template. A collection shown on several pages, such as client logos or testimonials, is kept in one place. A new entry appears in the approved layout as soon as your team publishes it.
03
Interactions and motionHover states, scroll effects and carousels are added where the design calls for them, and each effect is listed with what it shows the visitor. Content stays readable when an effect doesn't play, and effects that make a page stutter on a phone are simplified before launch.
04
Search and accessibility checksEach page gets one H1, a consistent heading order, its own title, description and social image, and alt text on its images. Structured data is added where a page type needs it. Text contrast in each component state and visible focus states are checked against the WCAG level agreed in the scope.
05
Finishing a Framer site already in progressThe pages already built are checked against the agreed page list, and each is marked to keep, change or complete. Shared type, spacing and components are settled before the remaining pages, and the pages your campaigns will send visitors to are finished first.
06
Pages that receive paid trafficEach page that ads send visitors to starts with three answers: who the ad reaches, what it promises and which enquiry the page should produce. When customer groups need different offers, each group gets its own page and form. Every form is submitted on a phone before launch and confirmed at its destination.
07
A one-page test before leaving WordPressOne representative page is rebuilt in Framer at a separate address while the WordPress site stays live. Your team edits it, its forms are sent to your CRM, and each language version is read in the HTML the server returns. You then get a written recommendation on the full move: whether it is worth doing and what it involves.
Shows team-run publishing in WordPress: at an AI/ML engineering studio, a content manager puts out routine articles and careers listings with no developer involved, and each named engagement has its own case-study template built around its proof points.
Shows motion with a stated purpose: on an insurtech platform's site, layout, hierarchy and motion were set to signal stability, and its product pages and lead funnels were shaped for carriers, agencies and solo agents.
Shows a site where photography leads and a collection invites browsing: a bridal boutique's gowns sit in a directory sorted by designer, with a page of photos and details for each gown, and booking a fitting is one step from any part of the site.
Shows a rebuild in stages on a site whose leads arrive through search and paid ads: a nutrition platform left Elementor for a custom WordPress theme in parts, and we watched each part's traffic and tracking beside the old version before starting the next.
Your Figma file or design materialThe Figma file with its components and variants, if the design is done. For a new design: brand files, copy, and the work samples and results the site should show.
01
An invitation to your Framer projectIf a Framer project already exists, an invitation to it, so we can review what is built and publish from the same project. Without one, the project is created in your account.
02
Content for each collectionThe entries for each collection, such as case studies or articles, or one finished example of each, and the name of the person who will add new ones.
03
Domain and form destinationsAccess to the DNS settings for your domain, and the inbox, CRM or other tool each form should send to.
04
WordPress and analytics access for a moveFor a test move: administrator access to the WordPress site and viewer access to its analytics and Search Console, shared by invitation, so the Framer page can be compared with the live one.
05
Approved wording for regulated claimsIf your business is licensed or regulated, the wording for licences, compliance statements and badges comes from your team. We place only approved wording, next to the claim it supports.
06
Sign-off at each stageChoose who signs off the components, each batch of pages and the launch. The rest of your team sends comments through them.
07
The order a Framer site is built in
[Review what exists]
We go through the brief, the Figma file, the Framer project or the live site, and agree the page list, the collections and the component set before anything is built.
Step 01
[Components and collections first]
Shared components are built at each breakpoint and the collections are set up with their fields. You review them on a temporary Framer address before full pages are assembled.
Step 02
[Pages in an agreed order]
Pages are assembled from the components, priority pages first. When the site launches in phases, each phase is checked and published before the next one starts.
Step 03
[Checks before launch]
Each page is compared with the design at desktop, tablet and phone widths, then checked for titles, alt text, contrast and focus states. Forms, links and menus are tested at each width before launch.
Step 04
[Go live, then publish a first entry together]
We connect your domain, redirect any changed addresses and confirm the site is open to search engines. Your team gets a short guide to the components and collections and publishes a first entry with us.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Can you build from a Figma file another designer made?
Yes. Before the build is planned, we review the file: its components and variants, auto layout, the breakpoints drawn and states that are missing, such as hover or error states. Each gap is listed with a proposed answer, and anything that needs new design is agreed with you before it is built.
Will the built pages match the Figma design?
At the widths drawn in Figma, yes: layouts, spacing and type are checked against the design page by page. Between those widths, Framer's layout settings decide how sections stretch, so we agree that behaviour on the first components instead of after every page is built.
What can our team change after launch?
Text, images and collection entries, in Framer's editor and without a developer. New pages can be assembled from the existing components, and the guide shows which sections fit together. A layout that no component covers is new design work, which we scope with you.
Can the case-study page be a template we reuse?
Yes. The case-study page is one collection template with sections for the starting point, the work, results and a client quote. Results and the quote can be left out of an entry, so a project without approved figures still reads as complete. The template is tested with your longest real project before the other entries are added.
Do the pages already built in Framer have to be rebuilt?
No, unless the review shows a page can't take the shared components. Pages that work are kept and brought into the same type, spacing and components. The review names any page that needs rebuilding and the reason.
Should we move our WordPress site to Framer?
It depends on what the site does and why your team is considering Framer. Sites made of designed sections and collections that a marketing team edits can be rebuilt in Framer. Shops, member areas, bookings or forms with conditional logic need a connected service there, or are a reason to stay on WordPress. The one-page test answers the question on your own page before the live site changes.
How do you handle search when a site moves to Framer?
Before the switch, every page of the old site is listed with its address, title, description and canonical tag, and its Framer version is compared in the HTML the server returns, language versions included. Changed addresses get redirects, so the Framer site plan has to be one that includes them. Nobody can promise rankings, so we record each main page's search figures before the move to compare afterwards.
Can you design the site for our own Framer developer to build?
Yes. The Figma file is then prepared for Framer: components with their variants, desktop, tablet and phone breakpoints, the fields each collection template needs, and a note for every interaction. Before launch we review the built pages against the design and send a list of fixes.
Who owns the Framer project and the site plan?
You do. We work inside your Framer workspace by invitation, or create the project there at the start, so the site plan and domain stay on your account. At handover you decide whether our access stays for later changes or is removed.
Does the build include a shop, member area or ad campaigns?
Not as part of the build. A shop, customer accounts, a member area or a booking system on Framer comes from a connected service, which we scope separately after reviewing it. Claims about licences, compliance and other regulated matters are approved by your team. We run Google Ads campaigns and ongoing SEO as separate services, each with its own scope.
Read these projects in full
Start with the one closest to your site: a team-edited content model, a brand site where motion signals stability, a collection browsed by designer, or a theme replaced step by step.