Engineering notes
Articles for people who
ship the stack
Rewrites on React, Node.js, TypeScript and AI. A translated body is shown when it exists. If it does not, you see the English text and a note that says so.
Tagged: Cascade
From Stylesheet to Screen: Where CSS Fits in the Browser Pipeline
Follow CSS from download to pixels: how the DOM, CSSOM and render tree are built, where the cascade runs, and which style origins compete for each element.
8 min readHow the Cascade Picks a Winner: Importance, Specificity and Source Order
See how browsers resolve competing CSS declarations, how to read specificity as a four-part comparison, and why hover rules and !important so often surprise you.
11 min readWhere CSS Values Come From When You Set None: How Inheritance Works
Learn how browsers decide whether a property inherits, why children receive the parent's computed value, and how inherit and initial give you explicit control.
10 min read
FAQ
About these articles
Yes. Each piece is an original English rewrite prepared for this site. Structure and code examples follow the source material; prose is rewritten and checked for overlap before export.
English is the source. Another language is shown only when that translation body exists. A missing or empty translation stays in English, including on a localized URL.
New drafts land in the publish queue as they pass editorial checks. Running the site import picks up only new or changed slugs — nothing is duplicated.
Treat samples as illustrative. Validate against your stack and licences before production use. For delivery work, contact us with the brief.
Request a 24h estimate
Need the same stack in a production operator layer? Send the brief — estimate within 24 hours.