LEGKO / Web architecture
Simple parts. Deliberately assembled.
Websites built to stay understandable, fast and easy to change. LEGKO brings proven parts together for business sites, content libraries and publishing systems.
Explore the systemLayout · typography · imagery
Pages · manuals · relationships
Routes · schemas · reusable parts
Independent layers. One coherent system.
01 / The system
Built around what matters most.
LEGKO is a deliberate web architecture. Its advantage is how familiar parts work together: fewer moving parts, clear responsibilities and changes you can inspect.
- 01
Content & relationships
Model pages, data and relationships so content stays consistent as a site grows.
- 02
Presentation & components
Build a readable, responsive experience. Keep assets and scripts proportionate to the job.
- 03
Technical SEO
Build in useful URLs, metadata, crawlable links and accurate structured data. Rankings are not promised.
- 04
Build & delivery
Review changes in Git, check the build and publish a known version with a path back.
- Ownership
- Keep source access, portable content and control of accounts. Make another maintainer possible.
- Maintenance
- Fewer moving parts reduce routine work. Dependencies, integrations and recovery still need care.
02 / Built for change
Keep the bones. Change the expression.
Separate content, presentation and routing so a change stays focused. Inspect what changed, debug the right layer and roll back when needed.
Stable
- Slugs & routing
- Content identities & relationships
- SEO and publishing mechanisms
- Component interfaces
Adaptable
- Copy & metadata
- Section order & depth
- Typography & visual direction
- Imagery & internal links
How content
publishing works
From source material to a reviewed, published change.
- 01Start with the source
- 02Draft and check
- 03Preview and approve
- 04Publish the change
Outline view. Same article, same address. Only the arrangement changes.
01 / Low-cost hosting depends on configuration and provider limits. Running costs →
02 / Extensions require their own scope and checks. Reusable architecture →
03 / Applications
Different websites. Related principles.
From a small business site to ongoing publishing. Use a focused architecture where it fits; choose another system when the requirements call for it.
Business & services
Clear services, people, locations and contact routes. Small-business websites are one useful application.
Content & publishing
Editorial sites, reference libraries and programmatic SEO infrastructure, with structured content and review.
Migrations & custom systems
Move suitable sites from heavier CMS setups, or build public pages from structured data with focused integrations.
04 / Working with the system
Update it with AI. Keep the judgement.
Use AI to draft content, update metadata or prepare a scoped change. Verify sources, review the preview and decide what gets published. The value is in architecture, integration and quality control, including knowing what to leave out.
05 / Field notes
The thinking, documented.
LEGKO.ca is a working example and living documentation: how we build, why we choose these parts, and where the approach has limits.
- 01Reusable architecture, not a fixed templateWhat is worth standardizing, what should stay adaptable, and why different websites need different decisions.
- 02How content publishing worksThe controlled path from source material to draft, checks, preview, approval, and a versioned public update.
- 03Ownership and portabilityWhat easy ownership means for the domain, accounts, source, content, version history, and the ability to leave later.
- 04Running costsWhy fewer moving parts can reduce infrastructure cost, which services cost separately, and what maintenance still involves.