Getting Started
The Evolution of the Web & Builderius
What you’ll learn in this lesson
- Why the web was created
- The principles behind how it works
- How modern tools changed web design
- Where Builderius fits in today
Why the web exists
Before building anything, it helps to understand what the web is for.
The World Wide Web was created by Tim Berners-Lee to solve a simple problem: different systems could not communicate.
His solution was a universal system where:
- Anyone can access information
- Anyone can publish
- Systems can work together
The principles behind the web
The web was built on three key principles:
- Universal access: Any system should be able to access any document.
- Decentralisation: No gatekeepers. Anyone should be able to publish without asking permission.
- Non-linearity: Information should not be locked into a fixed order. Users should be able to move freely, jumping between content as they choose.
These ideas still shape how we build for the web today.
From open web to publishing for everyone
Years later, platforms like WordPress took this further. Their mission was simple: democratise publishing.
They made it possible for anyone to publish content online without needing a technical background. That was a major shift. The web became more accessible, not just in how we consume content, but also in how we create it.
When the web became fragmented
As the web grew, so did complexity. Different [browser] companies began creating their own solutions, languages and approaches. This led to a fragmented ecosystem — sometimes described as a “digital Tower of Babel”.
The problem was familiar: systems once again struggled to work together.
The role of standards
To solve this, the World Wide Web Consortium (W3C) was formed. Think of it as a neutral body that brings organisations together to agree on web standards.
Their goal is simple: interoperability.
That means:
- Code should work across devices
- Browsers should interpret code consistently
- No single company should control how the web works
This is why a website can (in theory) work on a phone, laptop, or even a smart fridge.
Standards are not the same as accessibility
Even if a site follows standards, it does not mean it works for everyone.
A website might load correctly but still be unusable for someone using a screen reader, keyboard navigation, or assistive technology.
That’s where Web Content Accessibility Guidelines (WCAG) come in.
WCAG is built on a simple but powerful idea:
The web only works if it works for everyone.
Accessibility is not an extra feature; it is part of the foundation.
The state of modern web design
Today, web design often sits at two extremes:
- Developers who prefer writing code in full control
- Designers who rely entirely on visual tools
More recently, there’s a third group:
- AI-first builders (sometimes called “vibe coders”) who rely heavily on automation.
Each approach has strengths, but also limitations.
Where Builderius fits in
Builderius is designed to sit in the middle.
It gives you:
- A visual development environment
- Full access to your code
- Optional AI assistance
You are not locked into one way of working.
You can:
- Design visually
- Write code directly
- or combine both
The goal is flexibility without compromises
Built on a separation of concerns
Builderius also follows a core web principle: separation of concerns.
This means:
- Structure, styling and behaviour are kept distinct
- Dynamic data, CSS and JavaScript are organised clearly
- You can focus on one layer at a time without losing context
Everything lives in one environment, but remains logically separated.
Build for the web’s original purpose
The web was designed to be open, accessible and universal. That hasn’t changed. If anything, it matters more now than ever.
So as you start building:
- Think beyond visuals
- Think beyond tools
- Focus on access, clarity and structure
Good web design is not just about how things look. It is about who can use them.
Key takeaways
- The web was designed for universal access
- Standards ensure consistency, not usability
- Accessibility must be built in from the start
- Tools should support the web, not replace its principles
What’s next
If you want to build for the modern web without losing control of your code, you’re in the right place. This is just the beginning.