We build WordPress websites, and finish partly built ones, where profiles, results, schedules and other record pages are filled from a spreadsheet by an import instead of being edited one by one. Each type of record gets one template, a changed row updates its existing page, and pages are checked against the sheet before launch. Your team edits the data in one place, and the next import carries each change to every page that shows it.
A few clients we’ve worked with
Norml builds or completes the WordPress side: the data map, the record templates, the import that fills them and the checks that pages match the sheet. Your team keeps ownership of the data, and the spreadsheet stays the place where it is edited.
Before any template is built, we agree on what counts as one record, which pages show it and where each value is edited.
On a partly built site, we start with what exists: the sheets, the import settings, the custom fields and the page templates. We follow one record through each of them to its rendered page, then report what to keep and what to change, with a reason for each.
Every row gets an ID that never changes, and rows in other tabs refer to it, so a result points to its profile by ID, not by name. Where a column mixes formats or one cell holds several values, we propose the smallest change that makes the import reliable.
Profiles, results, schedules, standings or product pages each get one template, so image sizes, spacing and the order of details match on every page. We test each template with a complete record, a sparse one and one with many linked rows.
A profile can list its own results, and standings or rankings can be calculated from the same rows. Each total or ranking gets one agreed source, so two pages showing the same figure read it from the same place.
The import matches each row to its existing page by ID, so an edited row updates that page instead of creating a new one. We agree how imports are started, what an empty cell does, and whether a removed row unpublishes its page or leaves it online.
Unfinished components are completed within the design direction you already have, and each template is built for phones first. Wide tables of results or statistics get a phone layout that stays readable, and every template is tested at phone, tablet and desktop widths.
We compare the sheet with the published pages: row counts against page counts, a sample of records field by field, linked rows on the right profiles, and the effect of renamed, emptied and removed rows.
You receive the data map, the import settings and short written steps for adding a record, correcting one and confirming that an import finished. They are written for whoever maintains the sheet.
The Farm Soho
The Farm Soho's location pages on WordPress come from a geo-location content system we built with Airtable. A content editor can manage those pages through Airtable without touching code.
Nasdaq Private Market
Relevant for its method rather than its website platform: Nasdaq Private Market's company pages are generated from its own dataset. We engineered the data pipelines with their team, designed the pages and built the programmatic generation that creates them.
“Norml Studio's professionalism and responsiveness were impressive.”
“They were proactive in suggesting improvements we hadn't considered.”
“They delivered what they said they would, on time.”
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”
An administrator account on the site and access to its hosting or staging copy, set up as invitations to your accounts rather than shared passwords.
View access to the sheets the site uses, shared with our account. Edit access waits until a change to their structure has been agreed.
The import settings, the list of custom fields and any notes on how data reaches WordPress today. Where nothing is written down, the review documents it.
The page types the site needs, what each one shows, and the designs or existing pages that set the visual direction.
One person who can confirm what each figure should be, so sample checks have a reference and questions about the data have an owner.
We study the site and the sheets as they are, then agree with you what stays, what changes and in which order, before any major change is made.
We agree on the record types, IDs and fields, then build one record with all its linked rows on a staging copy, so you can check it against the sheet.
Each template is built and filled by the import on staging, where you review real records on your own phone and computer.
We run the full import and compare the result with the sheet. Mismatches caused by the import or the templates are fixed, and errors found in the sheet itself go to your team as a list. A second run confirms that repeating the import changes nothing unexpected.
After launch we make one real change in the sheet with you and follow it onto the site, then hand over the written steps.
No account layer between you and them. These are the Norml specialists this work runs through.
Founder & Architect
Co-founder · Design & Strategy
Full-Stack Developer
Full-Cycle SEO Specialist
QA Engineer
“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
