six courses that give your directory its internal skeleton
You can't build on a site that isn't organized. The types, categories, plans, forms, widgets, and file infrastructure that make everything work the way members and visitors expect.
Skip the structural work — or do it out of order — and a platform full of content still works against members and visitors at every turn.
You're running on the default content model. You never defined your own types — events, listings, and articles all share one generic template, so nothing displays right and the data can't support filtering or relationships.
Your categories reflect how you think. The taxonomy was built around your internal logic, not how visitors browse — so they can't find anything and head straight to the search bar.
Your forms ask for too much. Designed around internal data wishes instead of the person filling them out — long, jargon-filled, and bleeding completions for fields nobody acts on.
Your files live everywhere and nowhere. Documents, uploads, and assets scattered across inboxes and drives — retrievable only if you remember where you put them.
"How do I define the distinct content types my platform needs before I start filling it with data?"
"How do I organize content into categories that match how users actually search, not how I think?"
"How do I design pricing tiers that capture value while giving members a clear reason to upgrade?"
"How do I build forms that collect exactly what I need without friction that kills completion?"
"How do I choose, place, and configure modular tools that make the site useful without clutter?"
"How do I build a file infrastructure that keeps everything organized now and manageable a year from now?"
No single course gives you the whole picture. The pod does.
"Your site has whatever structure the platform defaulted to. Visitors can't find anything because the category tree reflects your logic, not their browsing. Your forms ask for too much, your widgets are placed by habit, and documents live everywhere and nowhere."
"Your content and listing types are explicitly defined; your categories match how real users browse; your tiers are priced deliberately to move people up; your forms ask exactly what you need; every widget has a reason to be there; and your documents have a home, a naming system, and access controls."
You stop building on top of defaults and start building on top of decisions — a deliberately designed structural foundation your traffic, members, and content can actually grow on.
Working documents — your whole operational layer — grouped into five outcomes.
Content, defined
Categories, browsable
Plans, priced to upgrade
Forms, that convert
Widgets & files in order
…and 57 more
$2,770 value when complete
All 6 Structure courses — for a fraction of the parts.
The price goes up as content ships — the founding price never comes back.
Not ready to commit? Attend our live workshops, sprints, and challenges for free — just show up. No signup, no credit card. If you like what you experience, the founding price locks in everything permanently.
Or go bigger — the same deal at every scope:
Pod
All 6 Structure courses
$320Pillar
All 36 Framework courses
$960University
All 324 courses
$4,320Same deal at every scope — everything included, price goes up as content ships. See How We Build →
Prices and the bundle checkout are placeholders — wire the bundle order form to its Simplero product.
All 6 courses · one-time payment · lifetime access
[ Simplero checkout / order-form embed renders here ]
Replace this block with the Simplero checkout for the Structure bundle product [bundle id].
Types comes first because categories organize types — you can't structure what you haven't defined. Category follows because the taxonomy organizes records within each type. Plans comes third because tiers bundle types into access levels, so you need to know what types exist before pricing them. Forms, Widgets, and Documents follow in that order because forms collect the data those types require, widgets surface types and categories to visitors, and documents store the assets the entire structure generates and depends on. Each course produces the structural decisions the next one needs.
Structure is where a configured platform gets its internal skeleton: content types defined, categories organized, plans priced, forms built, widgets placed, and files stored. It picks up after Config — your operational platform — and feeds into Engine, where you compose these pieces into the pages members actually interact with.
Yes — each course stands on its own and links to its own site. But they're designed to build on each other, so most people start at Types and work through in order. The bundle is the better value if you're structuring the whole platform.
The numbered order: Types → Category → Plans → Forms → Widgets → Documents. Each course produces the structural decisions the next one assumes.
It's self-paced — roughly 48–72 hours of work across 6–8 weeks. Each course is real architectural work with deliberate gaps for testing and stakeholder review; the spacing is part of how it works.
Ideally you've completed the Config pod — Structure assumes a configured platform to define content types and infrastructure on. If you have that already, you're ready.
Yes — the Structure pod is priced below the total of the six courses bought individually, and you get lifetime access to all of them in one purchase.
72 working artifacts across the six courses — a defined content model, a browsable taxonomy, a deliberate pricing architecture, converting forms, a placement-tested widget set, and a real document operating system. Documents you use, not certificates.
Give your site the skeleton it holds everything on. Six courses, from content types defined to every file in its place.