Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Essential CSS
Lesson Plan
  1. Introduction
    1. Welcome to Essential CSS
    2. Getting started with the course
    3. What are file formats?
    4. Web standards
    5. What is HTML?
    6. What is CSS?
    7. Devtools, your indispensable best friend
  2. CSS Key Concepts
    1. Some background about CSS
    2. CSS Syntax and Terminology
    3. Selectors
    4. Cascade and Specificity
    5. Origin and Importance
    6. Inheritance
    7. How browsers handle CSS
  3. Basic Mental Model
    1. Everything on the web is a box
    2. The box model
    3. How big is your box?
    4. The relationship between px and em
    5. The `box-sizing` property
    6. The `display` property
    7. Formatting contexts
    8. Block boxes
    9. Inline boxes
    10. What is inline-block?
  4. Flexbox and Grid
    1. The parent-child relationship
    2. Sizing in Flexbox
    3. Flex directions
    4. Basic grid concepts
    5. Setting up a grid
    6. Placing grid items
    7. Box alignment
  5. Building web layouts
    1. Arranging your boxes on the web
    2. Positioning schemes
    3. Floating boxes
  6. Typography
    1. Making your text look good
    2. What is a font?
    3. Typesetting with CSS

Web standards

2m:4s

Web standards are technical documents known as specifications which describe in detail exactly how the various web technologies should work. Although it can be a resource for web developers, these documents’ main target audience are the browser engineers who need to implement features in browsers so we can use them.

The web today is much more standardised than during its early days during the 90s and even the 2000s. Because the web is such a ubiquitously used technology, one of the main guiding principles behind the fundamental web technologies of HTML, CSS and JavaScript is: to never break the web.

In the world of software development, this is a fairly unique concept. If you tried to open apps on a device running iOS4 today, a lot of them probably won’t run properly any more. In the early days of the web, before the establishment of standards, Netscape and Microsoft both did their own thing and competed with each other to offer different features.

The situation looked something like this:

A comic book illustration of warring internet browsers
The Browser Wars (during the 90s) as illustrated inhttps://comic.browserling.com/84

It made life pretty difficult for the folks who were trying to create content for the web. They had to write extra code to make sure their websites would work across the different competing browsers. Developers came up with lots of workarounds and hacks to deal with this.

Eventually, the man known as the inventor of the World Wide Web, Sir Tim Berners-Lee, founded the World Wide Web Consortium (W3C). It is an international community where member organisations, W3C staff members and the public, work together to develop web standards.

When web standards were established, browsers could not simply discard the old features and render everything according to the new standards, because this would break many websites that were not standards-compliant.

Instead, browsers treat websites which are compliant with web standards differently from the older legacy websites by having 2 rendering modes, standards mode and quirks mode. In quirks mode, the browser will try its best to emulate the non-standard behaviour of Netscape Navigator 4 and Internet Explorer 5. Peter-Paul Koch has an excellent article about how this situation came about, which you can read at: https://www.quirksmode.org/css/quirksmode.html.

Today, things are a whole lot better with the widespread adoption of web standards. And browser vendors, in spite of being part of different software companies, cooperate and work together to advance web technologies and develop new web standards.