Botmonster TechCSS container queries
(@container) style a component by the width of its parent, not the browser viewport. Add container-type: inline-size to a parent element. Then write @container (min-width: 400px) { ... } rules on the children. Those children adapt their layout to the space they get, not the screen size. All major browsers have supported them since early 2023: Chrome 105+, Firefox 110+, Safari 16+. As of 2026 they sit at over 96% global support, per Can I Use
.
Javascript
CSS Container Queries: Build Truly Responsive Components
Implement Dark Mode in Vanilla CSS (Zero JavaScript)
You can build a solid dark mode using only the prefers-color-scheme media query and CSS Custom Properties
(variables). This CSS-first approach gives users a flash-free theme switch. It also keeps your site’s code clean, light, and free of JavaScript.
Why Avoid JavaScript for Dark Mode
Most dark mode tutorials reach for JavaScript to toggle a class on <body>. It feels like the obvious fix. You add a button, read a preference from localStorage, and apply a class. It works well enough in demos. But in production, on real hardware and real networks, this approach breaks in ways worth knowing about before you commit to it.
Building a Progressive Web App from Scratch with Vanilla JavaScript
A Progressive Web App requires just three things beyond your existing website: a Web App Manifest JSON file that defines the app’s name, icons, and display mode; a service worker that intercepts network requests for offline support and caching; and HTTPS hosting. Add these to any site with plain JavaScript - no React, Angular, or framework needed - and browsers will offer an install prompt, enable push notifications, and cache your app for offline use. The entire setup can be done in under an hour with three files.
Build Interactive Charts in Hugo without JavaScript
Can you build interactive charts in Hugo without any JavaScript? Yes - by using Hugo shortcodes that transform CSV or JSON data into styled SVG graphics at build time. This “Zero-JS” approach produces charts that render instantly, work in every browser environment including RSS readers and print, and score significantly better on the page-speed metrics Google ranks on than anything built with Chart.js or D3.js .
The Problem with Client-Side Charting Libraries
Chart.js is excellent software. So is D3.js. But both carry a tax that static blog authors rarely think about until they run their first Lighthouse audit.
Core Web Vitals: Fix LCP, CLS, and INP
To pass all three Core Web Vitals, target three numbers. Get LCP under 2.5 seconds by preloading your hero image and cutting server response time. Get CLS under 0.1 by reserving explicit dimensions for all media. Get INP under 200ms by breaking long JavaScript tasks into smaller chunks. Diagnose all three with Chrome DevTools, Lighthouse, and the CrUX Dashboard for real-user field data.
Why Core Web Vitals Matter for SEO and User Experience
Google added Core Web Vitals to its ranking algorithm in 2021, and their weight has grown since. The March 2026 core update brought holistic CWV scoring. Google now aggregates performance data across your whole domain rather than judging it page by page. If 30% of your indexed pages fail LCP thresholds, that drags down the site-wide score even when your homepage is fast.
Web Components: Build Framework-Agnostic UI Elements
Web Components are native browser APIs: Custom Elements, Shadow DOM, and HTML Templates. They let you build reusable UI parts like <modal-dialog> or <accordion-panel> that work in React, Vue, Svelte, Angular, or plain HTML. No build tools, no framework lock-in. With 98% browser support in 2026, they’re the most portable component format around. Write it once, ship it anywhere.
The Three APIs That Make Up Web Components
Web Components is an umbrella term for three browser APIs that work together. You can use each one on its own. Custom Elements without Shadow DOM, Shadow DOM without Templates. But the combination is where they shine.