Concept: a company profile website, static-first
A labeled concept showing how a small service business could present itself with a fast, accessible static website.
TakeawayFor most small business sites, a static build with structured content beats a heavier platform.
Concept project. A design exercise written for this portfolio, not client work.
Problem and constraints
Problem
Small businesses often have a social page with no structure, or a slow template site nobody updates. Visitors cannot tell what is offered or how to start.
Constraints
- Most visitors arrive on a phone.
- The owner updates content rarely, without a developer.
- No budget for a database, a server or platform fees.
- It must stay usable if JavaScript fails.
Options considered
- Not chosen
A social media page only
No cost, but no structure, no search presence and no control over presentation.
- Not chosen
A template site builder or CMS platform
Easy editing, but ongoing fees, heavier pages and lock-in.
- Chosen
A static site generated from structured content
Each change needs a rebuild, in exchange for a fast, secure, inexpensive site.
Architecture
Keep content in structured files, generate plain static pages from them, and serve those from an edge network. Page order follows the visitor's questions, and the enquiry is a prefilled email.
Select any component to see what it does and how it connects. The diagram is illustrative: it shows the shape of a solution, not a specific system.
Illustrative reference architecture
Content
Build
Output
Deliver
Visit
Select a component
Choose any block to read what it does and how it connects to the rest.
- Content files
- Pages, services and articles stored as structured data, separate from the design templates.
- Build step
- A small script combines content and templates and checks for missing or unsafe fields.
- Static pages
- Plain HTML, CSS and a little JavaScript, readable even without scripts.
- Edge delivery
- Files are served from a global network with caching and security headers.
- Visitor
- A prospective customer on a phone, who can read, understand and make contact quickly.
Decisions and trade-offs
Build static pages from structured content files.
Trade-offContent changes need a rebuild, but the site is very fast, secure by default and cheap to host.
Order pages by the visitor's questions: what, why trust you, how to start.
Trade-offLess brand storytelling on the home page, in exchange for a faster first enquiry.
Use a prefilled email enquiry instead of a form backend.
Trade-offLess automated, but no server to maintain and no data stored on the site.
How it would be delivered
Write
Draft the content outline first, then design the layout around it.
Design
Use one responsive layout system with a small set of reusable components.
Tune
Optimise images and fonts, and measure on a mid-range phone profile.
Launch
Deploy to an edge network with a custom domain and a documented update routine.
Lessons and next steps
Current statusConcept project. It has not been built for a client.
Lesson: a fixed content model makes later updates simple, even for non-technical owners.
Next steps
- Replace the sample content with a real business's services if a client project begins.
- Set a performance budget and measure on a mid-range phone profile.
- Write the short update guide the owner would use after handover.
Related work
Talk it through
If this kind of problem looks familiar, I would like to hear how it shows up for you.