Your interface stops drifting
Consolidated components mean two pages built a year apart still look like the same product.
Give departments reusable school website components.
We create a Figma system for programme pages, practical notices, staff information and documents. Content variations and interaction states are included so routine publishing does not require a new layout for every department.
A few clients we’ve worked with
What we do
Design systems for schools: Shared values, Content components, Usage guidance.
Decisions that shape the work.
Which patterns repeat across departments?
How should long titles and missing optional fields behave?
What repeated decisions cost you.
Every time a team re-decides a button, a form field or a card, it pays for that decision twice — once in design and once in code. A system is how you stop paying.
Design and code agree
One library, with practical examples of how the parts work together, removes the gap between what was designed and what shipped.
Onboarding is shorter
A new designer or developer has a reference instead of needing someone to explain the unwritten rules.
Design systems: scope of work.
The brief records the website scope, approved source material and responsibilities for review.
Shared values
Define typography, spacing, colour and image treatment for the approved identity.
Content components
Build reusable programme, staff, notice and document patterns.
Usage guidance
Explain states, responsive rules and justified department variants.
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“Norml Studio's professionalism and responsiveness were impressive.”
What you receive.
The agreed engagement produces the following artifacts.
- 01
A component and variant inventory.
- 02
A Figma library and examples.
- 03
Usage and implementation guidance.
Our process
How the work runs.
Inventory content patterns
Collect realistic programme and practical-information examples.
[ 01 ]
Build reusable states
Test long labels and incomplete records in the components.
[ 02 ]
Document adoption
Provide rules for designers, developers and publishing staff.
[ 03 ]The people who do this work.
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.”
Max TymoshynFounder & Architect
Get startedDesign systems for schools: questions.
Can faculties use different colours?
Approved variants can be part of the shared system when they serve a defined information need.
Does the library update the live site automatically?
No. The design library and coded implementation need an explicit adoption process.
Website 2.0 combines strategy, design, development and launch in one engagement.