~/richi.codes $ ls lab
Learning by building, in the open.
Richi Gallego's second brain and code lab: working prototypes, automated technical notes and a new game every day. Stuck on a problem with your website or your code? You can write to me.

- technical notes published
- 63
- games to play
- 16
- radar editions
- 7
- years writing code
- 20+
Experiments
Things I build to understand how they work. All of them are live and you can play with them.
Schedule a weather alert
A Web Push experiment: install the PWA on your phone, pick a place and a time, and an n8n workflow sends you the forecast right then.
Step 1 · on your phone
Open this page on your phone and enable it there: the notification goes to that device, not this one.
Step 2 · schedule the alert
The honest friend
That friend who looks at your website and tells you what's wrong, no sugar-coating. It may sting, but better to hear it from them than from a client, from Google or from a user who leaves and never comes back.
- 01 · Reads the public HTML of the page you give it.
- 02 · An AI (Gemini) reviews it like a friend would, not like a salesperson.
- 03 · Asks for no email or personal data: the result shows up right here.
Second brain
63 technical notes connected by topic. Search, or tap a node in the graph to filter.
For now most notes are in Spanish; English ones are on the way.
63 notes
- Week in the lab: seven games chasing the light22 Nov 2026 · week-in-review, gamedev
- Intl.Locale info: the browser knows your week21 Nov 2026 · javascript, i18n
- CSS @scope: the nearest theme finally wins20 Nov 2026 · css, scope
- CSS typed arithmetic: turn any length into a number19 Nov 2026 · css, calc
- moveBefore(): move DOM nodes without resetting them18 Nov 2026 · dom, javascript
- CSS Grid Lanes: native masonry, now in Safari17 Nov 2026 · css, layout
Each line joins two topics that show up together in a note.
Frontend & UX/UI trend radar
Chrome 158 is now stable with two big changes: sites can request installing a web app straight from HTML, and XSLT stops working. Chrome 159 also enters beta, and W3C wants to bring the accessibility guidelines for authoring tools up to date.
Chrome 158: install apps from HTML
Chrome 158, stable since November 17, adds the <install> element and navigator.install(): a page can ask the browser to install a web app from its manifest URL, and the element allows cross-origin installs without JavaScript. It also ships ::highlight(*), which styles every Custom Highlight with zero specificity.
XSLT stops working in Chrome
Per Chrome's timeline, from version 158 (November 17) XSLT stops working on stable, both XSLTProcessor and the processing instruction, except under the origin trial or enterprise policy, which end in Chrome 176 (August 2027). Alternatives: transform on the server, move to JSON, Saxon-JS or a WASM polyfill.
Chrome 159 beta: a real AccentColor
Chrome 159, in beta since November 12 with stable scheduled for December 8, makes AccentColor and AccentColorText reflect the element's effective accent-color so custom styles match form controls, fixes scroll snap in single-axis containers and trials a passive mode for WebAuthn conditional UI that suggests passkeys without a sign-in form.
W3C wants to renew ATAG
Shawn Lawton Henry, who leads WAI, explains (November 10) that ATAG 2, the accessibility guidelines for authoring tools published about ten years ago, needs updating for WCAG, new technologies and the use of AI. W3C proposes a working group and opens a Community Group to anyone: CMSs, no-code builders and social platforms shape how billions of people publish.

About this lab
I'm Richi Gallego and I've been programming for over twenty years. This site is my notebook: I build whatever makes me curious, leave it running and write down what I learn along the way.
- Everything published here works and you can try it. If it breaks, that is part of the experiment too.
- The notes and the radar are written by an AI pipeline, and every piece says so.
- No courses or subscriptions here. But if you have a problem with your website or your code, write to me and we’ll take a look.
Want to tell me something?
A problem with your website or your code that you need solved, an idea for an experiment, a note that doesn’t add up, or just a hello. I read it myself, no bots in between.
Email is optional, but if you need a hand, leave it so I can reply.