| Don’t Let Your Redesign Ruin Performance: A Case Study (mac/per) | | 85 |
| performance, redesigning |
| A Leap in the Evolution of Airtable’s Codebase: Scaling TypeScript to Thousands of Projects (air) | | 84 |
| typescript, scaling |
| Blast From the Past: 2advanced.com (web) | | 83 |
| design, flash, history |
| How a BBC Navigation Bar Component Broke Depending on Which External Monitor It Was On (jos) | | 82 |
| debugging, javascript |
| “We Were Wrong”: An Oral History of WIRED’s Original Website (vir/wir) | | 81 |
| podcasts, history |
| How Vercel Adopted Microfrontends (mar+/ver) | | 80 |
| vercel, micro-frontends |
| How Is This Website So Fast!? (wes) | | 79 |
| videos, performance |
| Prioritizing Design Systems (ale/uxd) | | 78 |
| design-systems, prioritization, processes |
| Breaking Into UX Research: Non-Traditional Paths to Success (uxd) | | 77 |
| user-experience, career |
| How We Built a Design System in 2 Weeks (3_s) | | 76 |
| design-systems |
| Why Gumroad Didn’t Choose htmx (shl/htm) | | 75 |
| htmx |
| Pfizer’s Future of Development (rhe/abi) | | 74 |
| visions, prioritization, processes, culture |
| Tackling a System’s Accessibility Without Testing (jbu+/gov) | | 73 |
| accessibility, wcag, heuristics |
| Mutation-Testing Our JavaScript SDKs (luk/get) | | 72 |
| javascript, testing |
| Improving the Screen Reader Experience for “Learn WCs” (and) | | 71 |
| accessibility, user-experience, screen-readers, assistive-tech, apple, voiceover |
| The Evolution of Attention (uxd) | | 70 |
| design |
| Growing a Design System Organically (hp) | | 69 |
| design-systems, scaling |
| Designing Design Systems: Constructing an Icon System (ado) | | 68 |
| design, design-systems, icons, images |
| Enhancing The New York Times Web Performance With React 18 (nyt) | | 67 |
| performance, react |
| uBlock Origin: Let’s Read the Code! (ant) | | 66 |
| videos |
| How We’re Building More Inclusive and Accessible Components at GitHub (eri/git) | | 65 |
| components, accessibility, dei, github |
| How Slack Automates Deploys (abi) | | 64 |
| deploying, automation |
| The Evolution of Figma’s Mobile Engine: Compiling Away Our Custom Programming Language (b_r/fig) | | 63 |
| figma, programming, typescript, migrating |
| Web Accessibility in the 2024 [U.S.] Presidential Campaigns (web) | | 62 |
| accessibility |
| Hello Bun: How Sveld Now Deploys 2× Faster on GitHub and Render (eri/ren) | | 61 |
| bun, deploying, performance |
| Purging Design System “Rot” From Our Checkboxes (chu/moo) | | 60 |
| design-systems, maintenance, quality, accessibility |
| Modern CSS Patterns in Campfire (jas/37s) | | 59 |
| css |
| Diving Into the Node.js Website Redesign (bri/nod) | | 58 |
| redesigning |
| Names Are Complex: Displaying Initials for an Avatar Component in a Design System (hey) | | 57 |
| naming, design |
| How We Reduced CSS Size and Improved Performance Across GOV.UK (gds) | | 56 |
| css, performance, optimization |
| CSS Scroll Snapping Aligned With Global Page Layout: A Full-Width Slider Case Study (uti/sma) | | 55 |
| css, scrolling, layout |
| How I Brought LCP Down to Under 350 ms for Google-Referred Users on My Website (paw) | | 54 |
| performance, web-vitals, optimization |
| Baseline’s Evolution on MDN (pep/mdn) | | 53 |
| browsers, support, web-platform |
| Jimdo’s Engineering Guidelines (pez/jim) | | 52 |
| guidelines, processes, collaboration, onboarding |
| Comparison of Accessibility of E-Government Websites in Europe (cer) | | 51 |
| accessibility, comparisons |
| 4 Web Devs, 1 App Idea (whi+/lwj) | | 50 |
| videos, web-apps |
| How Bear Does Analytics With CSS | | 49 |
| analytics, metrics, css |
| CSS Findings From Photoshop Web Version (sha) | | 48 |
| html, css, adobe, photoshop |
| How We Optimized Package Imports in Next.js (shu/ver) | | 47 |
| nextjs, dependencies, optimization |
| Skip Links on ikea.com (mat) | | 46 |
| accessibility, skip-links |
| Hashnode’s Overall Architecture (san/has) | | 45 |
| architecture |
| Greenwashing and the COP28 Website (mic/css) | | 44 |
| sustainability |
| CSS Findings From The Threads App II (sha) | | 43 |
| css |
| From Silos to Design Systems (sag) | | 42 |
| design-systems, processes |
| Case Study: Rebuilding TechCrunch Layout With Modern CSS (sha) | | 41 |
| refactoring, css |
| Optimizing Speed on ebay.com (add) | | 40 |
| performance, optimization, web-vitals |
| How We Optimized Performance to Serve a Global Audience (lap/sma) | | 39 |
| performance, optimization |
| CSS Findings From the Threads App (sha) | | 38 |
| css, facebook+meta |
| How We Created an Accessible, Scalable Color Palette | | 37 |
| colors, color-palettes, accessibility, scaling |
| Simple Things Make Things Simple (pjo) | | 36 |
| simplicity |
| Moving From Vue 1 to Vue 2 to Vue 3: A Case Study of Migrating a Headless CMS System (lis/sma) | | 35 |
| vuejs, migrating, headless, content-management |
| How We Built Our Multi-Platform Design System at Booking.com (nic/boo) | | 34 |
| design-systems, theming, scaling |
| Caching at DEV (rid) | | 33 |
| caching, performance |
| Our Future CSS Strategy (jac/vol) | | 32 |
| css, javascript, css-in-js, strategies |
| Early Learnings for Early Hints at Shopify (sia/per) | | 31 |
| videos, shopify, performance, hints |
| How We Improved React Loading Times by 70% With Next.js (cau) | | 30 |
| react, performance, nextjs |
| A Delightful Guide to Culture at Mamo (Inspired by Khalil Gibran) (asi) | | 29 |
| guides, culture |
| How We Designed an Accessible Color Palette From Scratch (wtt) | | 28 |
| accessibility, colors, color-palettes |
| How We Think About Browsers (kei/git) | | 27 |
| browsers |
| Accessibility Monitoring: How We Test (gov) | | 26 |
| accessibility, monitoring, testing |
| Improving the Performance of Wix Websites (Case Study) (dan/sma) | | 25 |
| performance, monitoring, culture |
| Design Systems at Replit: Better Tokens (war/rep) | | 24 |
| design-systems, design-tokens |
| How We Improved Our Design System Delivery (gil) | | 23 |
| design-systems, processes, optimization |
| Using Monorepos Is Not That Bad (med) | | 22 |
| monorepos |
| How We Reduced Next.js Page Size by 3.5× and Achieved a 98 Lighthouse Score (pap) | | 21 |
| performance, nextjs, lighthouse, google |
| How We Built React Components for Any Front End (try) | | 20 |
| react, components |
| Reducing HTML Payload With Next.js (Case Study) (lap/sma) | | 19 |
| nextjs, html, performance |
| Updating React at Etsy (san) | | 18 |
| react, preact, frameworks |
| A Netflix Web Performance Case Study (add/dev) | | 17 |
| performance |
| Removing jQuery From GitHub.com Frontend (git) | | 16 |
| github, jquery, javascript, processes, refactoring |
| Why We Didn’t Use a Framework (sma) | | 15 |
| frameworks |
| PWA Stats (clo) | | 14 |
| websites, web-apps, progressive-web-apps, metrics |
| How Mail.ru Reduced Email Storage From 50 to 32 PB (and/sma) | | 13 |
| storage, email, optimization |
| A Redesign With CSS Shapes (mey/ali) | | 12 |
| css, shapes, redesigning |
| Building Social: A Case Study on Progressive Enhancement (mar/sma) | | 11 |
| javascript, progressive-enhancement |
| How We Use Prototyping, and How It Made Us More Efficient (dem/sma) | | 10 |
| design, prototyping, processes, efficiency |
| Building the UI for the New “The Times” Website (ped/gro) | | 9 |
| design, collaboration, architecture, css, documentation |
| Getting Started With Pattern Libraries (ann/ali) | | 8 |
| introductions, design, documentation, pattern-libraries |
| Controlling Heavy Weight Websites (wel) | | 7 |
| performance, user-experience |
| HTML5 Quake to Shake Up Flash (ale/sit) | | 6 |
| html, canvas, websockets, webgl, flash |
| IKEA and the Font Fiasco (sit) | | 5 |
| typography, fonts |
| An SVG Case Study: Integrated, Dynamic Avalanche Forecasting | | 4 |
| perl, html, sql, databases, svg, images |
| Anil Dash Does Amazon (sim) | | 3 |
| html, conformance |
| Access for All | | 2 |
| accessibility, w3c |
| MSNBC Makes News by Making HTML Dynamic (zdn) | | 1 |
| microsoft, html, java, dhtml |
