224 Website System Docs
Your site runs on the 224 Go To Market Website System, built using the Lumos framework. This guide shows you how to use it.
Your site comes with 224 Agent Instructions installed, so an AI agent connected to your site can walk you through anything in this guide, on your own site. See Asking Your AI Agent below.
Contents
The Mindset
Your website isn't a static thing you'll eventually outgrow and rebuild. It's a system, designed so your marketing team can run it, change it, and grow it without developer dependency. This guide exists to teach you that system, not Webflow. You don't need to become a web developer, you only need to understand how your site is put together, and that's a much smaller, more learnable thing.
The shift we want you to make is to start building with components. Components are the building blocks of your site, and they're what you'll use to create new pages, add sections, and update content. The other three parts support them. Utility classes are styling controls you apply inside a component. Collections hold content that repeats, like blog posts, FAQs and testimonials. Variables are the settings the whole system is built on. Get comfortable with components and the rest follows.
What this system is and isn't designed to do
What this system is designed to do
- Let your team make everyday changes, like copy, images, new pages, and new blog posts, without a developer in the loop.
- Keep your site consistent automatically, so a change in one place flows everywhere it should.
- Grow with you. New campaigns, landing pages and sections are built from blocks you already have.
- Give your team ownership of the site, and the confidence to run it.
What this system is not designed to do
- Open up every Webflow setting. We've limited what's exposed so your team can move quickly without breaking the build underneath.
- Be learned in a day. Start with small edits and build from there.
Who does what?
The system is built so the things you'll do most often are also the safest. There's a clear line between editing within the system, which you're set up to do freely, and changing the system itself, which needs more care. Knowing the difference is what lets you move quickly without worrying you'll break something.
Go for it. This is yours to run
- Editing text, images, and links on existing pages
- Adjusting component properties like headings, colour themes, padding, and visibility
- Building new pages from existing components
- Adding, editing, or archiving CMS content like blog posts and case studies
- Reordering sections and duplicating existing layouts
Changes to the system itself. Take care, and email us if you're unsure
- Editing a main component, which changes every instance across your site
- Changing variables during a rebrand or design overhaul
- Adding custom code, scripts, or new integrations
- New section types or templates that don't yet exist in your system
- Structural changes to site architecture, navigation, or the CMS setup
- Anything where you find yourself adding classes or properties you don't understand
Update your content, create new pages and build with components with confidence. If the system itself needs updating, we'd recommend reaching out to us at support@224industries.com.au.
Asking Your AI Agent
Your site comes with 224 Agent Instructions. They teach an AI agent connected to your site through Webflow's MCP server, such as Claude or ChatGPT, how your system works.
The agent is set up to show you how to make a change before it offers to do it for you. That's deliberate, so you can do it yourself next time.
Read this site's agent instructions before you do anything, then tell me what rules you're working under.
If it can't list the rules back, it hasn't read them. Ask again before you give it real work.
What can you help me with on this site?
Describe the outcome, not the styling. "Make the heading on the pricing section one size smaller" works better than "set the h2 to 32px". Your system doesn't use pixel values, so the agent has to translate them, and it can get the translation wrong.
Tell it where to look. Name the page and the section, then say what you want:
On the [page name] page, find the [section name] section and [what you want to change].
For example: "On the Pricing page, find the pricing section and update the price on the first card." Naming the page and section means the agent doesn't have to guess which heading or card you mean.
It's set up to leave publishing to you. Changes stay as drafts until someone on your team reviews them and publishes.
If it suggests changing a u- class, a variable or a main component, take care. That changes the system itself, so make sure you understand what it will affect, and email support@224industries.com.au if you're unsure.
The System
Your system has four main areas: components, collections, utility classes and variables. This section covers what each one does.
Where you'll be working
You'll do your editing in the Webflow Designer, directly on the canvas.
Depending on how you're set up in your team, you'll be in one of two roles:
Designer gives you the widest access. You can build new pages, edit content and media, work with components and collections, and adjust everything covered in this guide. This is the role most of our clients use, and it's what this guide assumes unless noted otherwise.
Marketer gives you the same visual editing experience for day-to-day work, including content, media, components, collections, and building new pages from existing components, but the underlying design system is locked. You can't accidentally change a component's core structure, edit utility classes, or alter variables. If you're in the Marketer role, think of it as the same canvas with a safety net: everything in the “yours to run” column is open to you, and the system itself is protected by default.
Two pages to know: Styleguide and Examples
Your site includes two reference pages built specifically to help your team. They're the fastest way to understand what you've got and how to use it.
The Styleguide is your reference for styles. It shows your utility classes alongside visual examples of them in use, like typography, spacing, and other styling controls, plus the smaller building-block components like buttons and icons, so you can see what each one does and how it looks applied. When you want to understand the styling options available in your system, this is where you look.
The Examples page is your showroom. It collects real layouts and section setups we've built with your system, so you can see how the pieces fit together in practice. When you're about to build something new, browse here first, as there's a good chance a similar layout already exists for you to learn from or reuse.
Walk me through this site's Styleguide and Examples pages. What's on each one, and when would I use it?
1. Components
Components are the core building blocks of your site. With them you can build entirely new pages, or go back into existing ones to reorder sections, change content, and apply design controls like a section's colour theme or padding.
Components keep your site consistent. Each one is built once and reused, so a change to the main component shows up everywhere it's used. The system uses components for nearly everything, from headings to the navbar and footer.
Every section is built from a series of components. You start with basic elements like typography, buttons, and image components, wrap those in layout components, and finish with a section component. Depending on how your site was built, you may primarily use Open or Closed components. Both are explained below.
To browse the components available in your site, open the components panel in Webflow. For the smaller building blocks like buttons and icons, you can also see them in use on the styleguide page, and for full section layouts, the Examples page shows how they come together.
Your site will most likely include additional custom components built specifically for your project. These are just the core building blocks the system was created with.
For example, say you want to add a features section to a page. Rather than building it from scratch, you'd find a features section component, drop it onto the page, and update its properties to swap in your own headings and copy. The layout, spacing, and responsiveness are already handled.
Understanding Component Properties
Component properties let you modify specific aspects of a component instance, like text content, an image, or a layout or colour theme. If a component has many properties, they are sorted by the aspect they update (for example Styles, Heading, Paragraph, Image).
To edit a content property such as a heading or image:
- Locate the component instance that contains the element you want to modify.
- Select the element on the canvas.
- On the right side of the designer you'll see a properties panel. Most section components have a large number of properties sorted into dropdowns. Open and close these to focus on the property type you want to update.
- Modify the element's property values (update the text, replace an image, set visibility, and so on).
On the Home page, find the hero section and help me change the heading and image. Show me which overrides to use.
Not all components are the same, and some have fewer overrides than others, depending on what they're built to do.
Updating Styles Within a Component
The system lets you update visual styles within some components using component properties. Each property has a name, and often a placeholder, so use that to understand what changing it will do. For example, updating a heading from h3 to h1 changes how the heading looks. The most important style properties are set up using component variant dropdowns. This makes it easy to see your options and avoid unintended changes.
A common one: most section components have a Colour Theme property. Switching it from Light to Dark flips that section's background and text together in a single click, with no manual restyling.
Other custom properties let you select a CSS class for a specific use case, such as changing a border radius or max width. To see all the possible classes for each use case, check the styleguide.
Try the properties to see what each one changes. Not sure which class to use? Ask your AI agent what would work here, or check your Styleguide page to see the main classes and what each one does. If an override has no visible effect, clear it rather than leaving it in place: typing something like dark or 10 into a Class property does nothing if that option doesn't exist. Click the property's blue label to reset it to its default.
Component Slots
Some components let you place other components inside them for extra flexibility, like putting a set of cards into a section. To do this, drag a component from the sidebar onto the canvas and rearrange as needed, or copy and paste an existing component to create more.
Webflow will let you put any component inside a slot, but not all slots suit all components. For example, sections should not go inside other sections. To make this clear, components are divided in the sidebar by their role.
If a component is meant to hold a specific other component, the slot is named accordingly. A Tabs component is built to hold Tab Links, so it has a slot named Tab Links.
The Two Main Component Setups
Closed Components
Closed components are used where a component should be the same everywhere it appears on your site. When it's updated, every instance across the site picks up the change. Your navbar and footer are examples.
Open Components
Open components are how you build sections from scratch, combining several layers of components into a custom section with unique content.
Open components allow more customised layouts when you need a unique section or set of content. They take a bit more knowledge of how sections are structured, and a change to one won't flow across the site the way a closed component's will.
When building sections with open components, use the following structure as a general guide and customise from there.
Simple Content Section structure
- Section
- Layout
- Column 1 Slot
- Eyebrow
- Heading
- Paragraph
- Button Wrapper
- Button
- Column 2 Slot
- Visual Image or Visual Video
- Visual Overlay (optional)
- Column 1 Slot
- Layout
Component Naming Conventions
Components have different types of names based on how they are used, and they are grouped by function in the component panel. The most common keywords are explained below.
- Section. Prebuilt sections you can drop onto a page, with specific style controls. They help you quickly fill out new pages with prebuilt responsive designs.
- Layout. More specific layouts than the default Grid component, built to be reusable inside other open components.
- Card. Elements used inside a component slot, giving you flexibility over how much content sits inside each component.
- Icon. Icon elements. They can be dropped into icon cards or list items.
- Form. Any element related to a form. Use the Form component and drop fields into it to create a custom form.
- CMS. Collection lists turned into components so they can be used inside other components, such as sliders, tabs, or open sections.
Editing a Main Component
To make the same change across all instances of a component, you need to edit the main component. You can do this from any component instance by:
- Double-clicking the component instance
- Right-clicking the instance and choosing Edit component
- Selecting the instance and clicking the pencil icon in the label
- Selecting the instance and clicking Edit component in the Style, Element settings, or Interactions panels
- Selecting the instance and pressing Enter
When you do this, all other elements on the page get a dark overlay, showing you are updating the main component and that any change will affect every instance.
Editing a main component changes every copy of it across your site, so take care. Most changes only need the component's properties. Main components can only be edited in Design mode, so staying in Build mode stops it happening by accident. If you're unsure, email us at support@224industries.com.au.
Editing main components is locked off entirely, another reason this is rarely something you'll need to think about.
2. Collections
Collections are the Webflow CMS. They let you manage dynamic, repeatable content like blog posts, case studies, team members, or job listings, so you can add and update content without rebuilding pages every time.
Each collection has a set of fields (like title, slug, body, image, date) that define the structure of every item inside it. When you add a new item, it slots into that structure and appears on your site wherever the collection is referenced.
Day to day, you'll use the Webflow Builder or the CMS panel in the Designer to add new items, edit existing ones, or archive content you no longer need.
The most common day-to-day example is publishing a blog post. You'd open the Blog collection, create a new item, fill in the fields (title, body, featured image, author, publish date), preview how it looks, then publish. The post automatically appears anywhere that collection is referenced on your site, like your blog index and any related-posts sections.
Walk me through adding a new post to the Blog collection, field by field.
Adding and editing items inside a collection is yours to run, in both Designer and Marketer roles. Changing a collection's structure, like adding fields or creating a new collection, is a system change, so take care and email us if you're unsure.
3. Utility Classes
Utility classes are pre-built styling controls in your system, all prefixed with u- (for example u-gap-4). Components use them behind the scenes to keep spacing, sizing, and layout consistent. You'll mostly encounter them rather than create them. It's useful to recognise what they are so the system makes sense, but adding or changing classes yourself is rarely needed and easy to get wrong.
All the utility styles on your site can be viewed on the styleguide page. If you're not sure what a class does, ask your AI agent.
What does the u-gap-4 class do on this site, and what other gap options do I have?
To make utility classes easier to use, we recommend the Lumos Chrome extension, which makes component class selectors easier to read.
How to Use Utility Classes in a Component
When a component has a property for utility classes, it includes the word Class, sometimes with a descriptor for a more specific role like Grid Classes. To update the utility classes, click into the property and type u- to see a list of classes you can add.
Context matters here. You don't want to add a gap class to a typography element. Pay attention to the kind of element you're working with and keep the default classes in mind. For example, if a layout has a u-gap-4 utility, click into it and backspace until it reads u-gap- to see your other gap options.
If you add a utility class and see no effect, remove it. You don't want to apply styles you don't understand. Only add classes that start with u- inside a component property.
Editing classes is locked. If a layout needs a styling change beyond what a component's properties allow, that's a good moment to email support.
4. Variables
Variables are the foundation your whole system is built on, the master settings for things like colours, font styles, and your site's max width. Because they control your site globally, this is the one part of the system you'll rarely, if ever, need to touch.
If you go through a rebrand or need a minor design change (like updating your h6 font style from medium to bold), this is where it's made.
Open the Variables panel in Webflow to see how yours are set up.
Variables can only be changed in the Designer role, and even then it's almost always done as part of a rebrand or design update.
Your First Step: Build a simple section
The best way to get comfortable with the system is to build something small. This walkthrough adds a simple section with a heading, a paragraph and a button, then edits the content. It's the core skill everything else builds on.
On the About page, help me add a section with a heading, a paragraph and a button. Which component should I use, and how do I set it up?
- Open the page you want to add to. Pick a page where a new section makes sense, or duplicate an existing page to practise safely.
- Add a section component. From the components panel, find a simple content section and drag it onto the page where you want it. It'll drop in fully styled and responsive.
- Edit the heading. Select the heading text on the canvas and type your own. Notice it keeps its style automatically, as you're changing the words, not the design.
- Edit the paragraph. Do the same with the body text. Click in, and replace the placeholder copy with your own.
- Update the button. Select the button to change its label, then set where it links to in the settings panel.
- Adjust the section properties (optional). With the section selected, open its properties panel. Try switching the Colour Theme or padding to see how the controls work. Clear any property that has no effect rather than leaving a guess in place.
- Preview and publish. Preview to see your section live in context. When you're happy, publish to push it to your live site.
For more layouts, browse your Examples page. If you want something the existing components don't cover, we'd recommend reaching out to us at support@224industries.com.au.
Every step above is available to you, as building pages from existing components is core to that role. The only thing you won't do here is edit the components themselves, which you don't need to for this.
Keeping Images Light
Large images are the main thing that slows a site down. Webflow can compress them for you in two places: the Assets panel for images on your regular pages, and the Collections panel for images inside CMS items like blog posts.
Compressing converts JPG and PNG files to WebP, a much smaller format that looks the same on screen. Webflow will ask you to choose between WebP and AVIF. Choose WebP, as social platforms don't have full AVIF support, so an AVIF image won't show as the preview when someone shares your page.
Compressing images in the Assets panel
- Open the Assets panel and click the expand icon to see the full view.
- Select the images you want to compress, or use Select all.
- Choose WebP, then click Compress. Each image is swapped in place, so everywhere it's used on your site updates automatically and nothing needs re-linking.
Compressing images in your collections
- Open the Collections panel and click the more options icon.
- Select Compress assets.
- Choose WebP, then click Compress. This runs across the images in your collections in one action.
It's worth running whenever you've added a batch of new content.
Good to know
- Take a backup first. The compressed file replaces the original and can't be converted back. Webflow keeps a backup automatically, but downloading the originals from the Assets panel before you compress means you'll always have them.
- Only JPG and PNG files are compressed. GIFs, SVGs and images that are already WebP are left as they are, and so is any image Webflow can't make smaller.
Compression won't resize. If an image displays at 800px wide, there's no need to upload it at 3000px. Save it at around twice the display width, so 1600px here, which keeps it sharp on high-resolution screens. Upload photos as JPG and keep PNG for images that need a transparent background. Both come out as WebP once compressed.
Using HubSpot Forms
If your site uses HubSpot forms, this section is for you. If it doesn't, skip it.
HubSpot forms usually take a second or so to appear after the page loads, which leaves a gap and can make the page jump. Your site has a Hubspot Form Loader component that holds the form's space and fades the form in once it's ready. It doesn't change your form or your HubSpot setup.
On the Contact page, help me add a HubSpot form.
Where do I find the Form ID for my HubSpot form?
Setting it up by hand
Adding it to a page
Each HubSpot form on a page gets one loader.
- Open the page with your HubSpot form.
- Add the component. In the components panel, find Hubspot Form Loader in the Form group and drop it immediately above your Hubspot Form Embed component. It's invisible, so it won't change your layout. Keeping the two together makes it easy to see which loader belongs to which form.
- Fill in the Form ID. Select the component and paste your Form ID into the Form ID property. See below for where to find it.
- Fill in the Height. Enter the form's height as a number only, like 423. No px on the end.
- Preview and publish.
If a page has two forms, add two loaders, one immediately above each form, and give each its own Form ID and Height.
Where to find your Form ID
- In HubSpot, go to Marketing > Forms.
- Hover over your form and click Edit.
- In the top right, click Review and update, then Update, then Get embed code.
- In the embed code, look for
data-form-id="...". The Form ID is the long string of letters, numbers and hyphens inside the quotes. It looks like this:d32746b4-4dc8-4c86-9568-321525c26743
Copy only the ID, without the quotes. HubSpot's menus change from time to time, so if those steps don't match what you see, their guide to embedding a form should have the latest.
Finding the Height
The height is how tall your form is once it has loaded, in pixels. The easiest way to get it is to ask us. Send the page link to support@224industries.com.au and we'll send the number back.
In the meantime you can leave Height at its default of 420. That suits a typical form with around five fields and a button. If your form is much shorter or longer than that, the page may still move a little when the form appears, so it's worth updating the number.
Which HubSpot forms this works with
HubSpot has two form editors, and the loader is built for forms made in the newer one. You can usually tell from the embed code:
- A newer form's embed code includes
hs-form-frame. The loader works with these. - An older (legacy) form's embed code includes
hbspt.forms.create. The loader won't do anything for these. The form still works as normal, it just loads the way it used to.
If you're not sure which one you have, email the embed code to support and they'll check.
Good to know
- If you forget the loader, your form still works and submissions still come through. You'll just see the gap and the small jump while it loads.
- If the Form ID is blank or has a typo, your page still works. The loader falls back to the default height of 420, so double-check the ID if the placeholder looks the wrong size.
- The placeholder is a general shape, a few grey bars for fields and a button. It's not an exact copy of your form. If your form looks very different and you'd like a closer match, email support and it can be adjusted.
- If HubSpot doesn't load at all, for example when a visitor's browser blocks it, the placeholder is designed to clear itself after about 12 seconds so there's no empty grey block left behind.
Filling in the Form ID and Height is yours to run. Changing the code inside the loader is a system change, so email us if you're unsure.
Have a question?
Email support@224industries.com.au