Stop calling everything either a “website” or a “web app”. I think we need a word for “Appsites”. Roast me.
I’m trying to name a product/UX pattern, not claim I invented every single ingredient.
For small organizations, we usually split the digital world into separate boxes:
- a public website
- a CMS
- an admin dashboard
- a member portal
- a document area
- maybe a payment tool
- maybe a calendar
- maybe a file manager
Then we glue everything together and pretend it feels unified.
I built something for small sports associations that doesn’t work like that.
The association still calls it “the website”.
But depending on who enters, that same website becomes different things:
- for anonymous visitors: public site, news, events, sponsors, documents, media
- for parents/athletes via magic link: private portal, certificates, deadlines, payments, uploads
- for staff/admins: athlete database, payments, documents, CMS, calendar, media library, file manager, website configuration
A news item published by an admin appears on the public site without rebuilding or redeploying.
A public document uploaded in the admin area appears in the website’s document drawer.
A YouTube link becomes part of the media library.
An event attachment becomes downloadable from the public calendar.
So I’m tentatively calling this pattern an Appsite:
> a self-contained, role-aware web application where the website itself is the application surface.
Not a SaaS that generates a public website.
Not a website with an admin panel bolted on.
Not just a CMS.
Not just a PWA.
Not just a dashboard.
The site is the app.
Is there already a better name for this pattern?
Or did I just give “a normal web app with RBAC and CMS features” a fancy name to feel better about myself?
I’m ready for the roast.