# web-standards Specifications and guidelines that define interoperable technologies for the World Wide Web. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Are Browser-Based Apps Enough for Web Designers? DevFeed: [Are Browser-Based Apps Enough for Web Designers?]() Original publisher: [Read original article]() Author: Eric Karkovack Published: 2026-09-13T19:09:47Z Content type: opinion Language: en Sources: [Speckyboy Design Magazine]() Topics: [web applications](), [Web platform](), [web-standards](), [Figma](), [Google]() Tags: [apps](), [browser](), [collaboration](), [design](), [design-business](), [freelance-career](), [freelance-design](), [privacy](), [software](), [tools](), [web](), [web-apps](), [web-design](), [web-designers](), [workflows]() ### AI overview Browser-based apps have matured enough to handle serious design, editing, and productivity work. The article considers their convenience and collaboration benefits, while also examining privacy concerns and cases where desktop tools remain preferable. ### Source excerpt Browser-based apps can now handle serious design, editing, and productivity work. We take a look at their convenience, collaboration benefits, privacy risks, and where desktop tools still make sense. The post Are Browser-Based Apps Enough for Web Designers? appeared first on Speckyboy Design Magazine. ## AI, Disruption, and Standards DevFeed: [AI, Disruption, and Standards]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-09-10T16:12:17Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [Artificial Intelligence](), [ai-governance](), [web-standards](), [Generative AI](), [MCP](), [a2ui](), [Accessibility]() Tags: [a2ui](), [accessibility](), [ai](), [ai-governance](), [appearances](), [architecture](), [best-practices](), [design](), [designers](), [ethics](), [formats](), [generative-ai](), [governance](), [mcp](), [open-source](), [standards](), [ux](), [video](), [web-standards](), [webstandards]() ### AI overview This article introduces a video panel on AI and standards featuring Jeffrey Zeldman and Patrick Neeman. The discussion connects lessons from the web standards movement to AI interfaces, focusing on fragmented user experiences, accessibility, interoperability, provenance, and the role of open-source and community efforts. ### Source excerpt Individually, we have very little power, but together we have a great deal of power. In response to a series of Medium articles by Patrick Neeman--like this one that addressed issues of AI governance, fairness, and standardization--publisher Louis Rosenfeld invited Patrick and me to come on his show and talk about AI and standards. A [...] The post AI, Disruption, and Standards appeared first on Jeffrey Zeldman Presents. ## Calling for Interop 2027 proposals DevFeed: [Calling for Interop 2027 proposals]() Original publisher: [Read original article]() Author: Patrick Brosset Published: 2026-09-03T16:09:17Z Content type: article Language: en Sources: [Microsoft Edge Blog]() Topics: [Interop2027](), [interoperability](), [Web platform](), [web-standards](), [Web Development]() Tags: [browsers](), [developer](), [interop](), [interop2027](), [interoperability](), [uncategorized](), [web-platform]() ### AI overview The article opens the proposal process for Interop 2027, inviting submissions that address inconsistent implementation of standards-based web-platform features across browsers. ### Source excerpt The Interop 2027 call for proposals is open, submit your ideas now! Over the past six years, the I The post Calling for Interop 2027 proposals appeared first on Microsoft Edge Blog. ## Ebb, Meet Flow: Intrinsic Design in a Nutshell DevFeed: [Ebb, Meet Flow: Intrinsic Design in a Nutshell]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-08-18T17:24:50Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [Responsive Design](), [web design](), [Front end](), [web-standards]() Tags: [authoring](), [best-practices](), [css](), [design](), [essentials](), [responsive](), [responsive-design](), [responsive-web-design](), [rwd](), [standards](), [state-of-the-web](), [the-essentials](), [the-profession](), [type](), [typography](), [usability](), [user-experience](), [ux](), [w3c](), [web-design](), [web-design-history](), [web-standards](), [webdesign](), [webtype]() ### AI overview This article explains intrinsic or fluid responsive design: define type scales for small and large screens, then let the browser interpolate between them according to viewport width. It connects the approach to earlier ideas about designing for the web's natural ebb and flow and to the development of Responsive Web Design through improved web standards and browser support. ### Source excerpt In 2020, the gifted makers of websites at Clearleft shared methods to achieve fluid responsive design. "Utopian" web design was (and still is) their half-kidding name for this approach, which Apple's Jen Simmons, working indendently, called "intrinsic design." Instead of chasing an ever-changing number of fixed breakpoints, utopian or intrinsic design follows the web's intrinsic [...] The post Ebb, Meet Flow: Intrinsic Design in a Nutshell appeared first on Jeffrey Zeldman Presents. ## April 2026 Baseline monthly digest DevFeed: [April 2026 Baseline monthly digest]() Original publisher: [Read original article]() Author: Jeremy Wagner GitHub LinkedIn Homepage Published: 2026-05-27T07:00:00Z Content type: news Language: en Sources: [web.dev: Blog]() Topics: [web-standards](), [Accessibility](), [Web platform](), [CSS](), [interoperability](), [Web Development]() Tags: [accessibility](), [article](), [css](), [developer](), [interoperability](), [web](), [web-platform](), [web-standards]() ### AI overview April 2026 Baseline digest covering newly available CSS capabilities, precision math utilities, structural semantic elements, Web API additions, and developer-community developments. It also explains how mature web-platform features and cross-browser interoperability can support more accessible web experiences. ### Source excerpt Read about various happenings with Baseline during April 2026. ## One Decade Later: Revisiting Five Front-End Kung Fu Moves DevFeed: [One Decade Later: Revisiting Five Front-End Kung Fu Moves]() Original publisher: [Read original article]() Published: 2026-04-30T23:26:34Z Content type: opinion Language: en Sources: [Ariya Hidayat]() Topics: [Front end](), [Web Development](), [JavaScript](), [Testing](), [test-coverage](), [ci](), [Instrumentation](), [ESLint](), [Git](), [web-standards]() Tags: [browser](), [code-coverage](), [continuous-integration](), [coverage](), [engineering](), [eslint](), [firefox](), [front-end](), [git-hooks](), [javascript](), [testing](), [web-standards]() ### AI overview A retrospective revisits front-end engineering techniques presented at a JavaScript meetup ten years earlier. It discusses git hooks, code complexity, code coverage, and cross-browser testing, explaining how common tools and modern workflows have changed their practical use. ### Source excerpt Exactly ten years ago, I gave a talk at the SF JavaScript meetup titled 5 Kung Fu Moves for Front-End Heroes. A full decade later, I found myself wondering: are these techniques still the secret sauce for modern front-end engineering, or have they been rendered obsolete by time? ## How To Use Standard HTML Video & Audio Lazy-Loading on the Web Today DevFeed: [How To Use Standard HTML Video & Audio Lazy-Loading on the Web Today]() Original publisher: [Read original article]() Author: Scott Jehl Published: 2026-04-07T14:30:00Z Content type: tutorial Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [HTML](), [lazy loading](), [web-standards](), [browsers](), [Web Development]() Tags: [audio](), [best-practices](), [browsers](), [gotchas](), [how-to](), [html](), [lazy-loading](), [video]() ### AI overview This tutorial explains how to use standard HTML video and audio lazy loading on websites. It covers recommended practices and common implementation pitfalls, noting that the feature is gaining support in major browsers. ### Source excerpt HTML video and audio lazy loading is now a web standard and quickly gaining support in all major browsers. Given Squarespace's role in proposing and implementing it, we're very excited to see how developers use it on the web. Let's cover some best practices for using video and audio lazy loading in any website, as well as some gotchas to avoid. ## Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers DevFeed: [Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers]() Original publisher: [Read original article]() Author: Scott Jehl Published: 2026-03-30T21:00:00Z Content type: article Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [web-standards](), [lazy loading](), [HTML](), [Web platform](), [WebKit](), [Chromium](), [Google Chrome](), [Firefox]() Tags: [browsers](), [chrome](), [chromium](), [firefox](), [html](), [lazy-loading](), [standards](), [web-standards]() ### AI overview Squarespace engineers describe how they helped add lazy loading for HTML video and audio to the HTML Standard. They contributed proposed implementations for Firefox and WebKit, worked with Chromium developers on a Google Chrome implementation, and added automated testing. ### Source excerpt At Squarespace, many of our core products are built on web standards, and our engineers are constantly pushing the boundaries of the web's capabilities. Occasionally, those boundaries reveal a limitation: an opportunity for the web's native capabilities to grow. This post is the story of how we found such an opportunity to work with the standards community to improve the web in a way that we - and everyone who uses it - can benefit. ## February 2026 Baseline monthly digest DevFeed: [February 2026 Baseline monthly digest]() Original publisher: [Read original article]() Author: Jeremy Wagner GitHub LinkedIn Homepage Published: 2026-03-30T07:00:00Z Content type: article Language: en Sources: [web.dev: Blog]() Topics: [Web platform](), [web-standards](), [Web Development](), [CSS](), [Security](), [API](), [Document Object Model (DOM)](), [vulnerability](), [SVG](), [JavaScript]() Tags: [api](), [css](), [interop](), [interoperability](), [javascript](), [security](), [svg](), [vulnerability](), [web-platform]() ### AI overview This February 2026 Baseline digest covers web platform features newly supported across major browser engines. It highlights Interop 2026, a CSS function for defining complex responsive shapes, and Trusted Types for protecting web applications against DOM-based cross-site scripting attacks. ### Source excerpt Read about various happenings with Baseline during February 2026. ## Announcing TypeScript 6.0 DevFeed: [Announcing TypeScript 6.0]() Original publisher: [Read original article]() Author: Daniel Rosenwasser Published: 2026-03-23T16:34:10Z Content type: release Language: en Sources: [TypeScript]() Topics: [TypeScript](), [JavaScript](), [Compiler](), [Go](), [Tooling](), [web-standards](), [npm](), [Visual Studio Code]() Tags: [code](), [features](), [javascript](), [release](), [tooling](), [types](), [typescript](), [updates](), [web-standards]() ### AI overview TypeScript 6.0 is announced as a bridge release between TypeScript 5.9 and the upcoming TypeScript 7.0. The article highlights alignment work, type-checking changes, import assertion deprecations, updated DOM types, and the transition toward a Go-based compiler and language-service codebase. ### Source excerpt Today we are excited to announce the availability of TypeScript 6.0! If you are not familiar with TypeScript, it's a language that builds on JavaScript by adding syntax for types, which enables type-checking to catch errors, and provide rich editor tooling. You can learn more about TypeScript and how to get started on the TypeScript [...] The post Announcing TypeScript 6.0 appeared first on TypeScript. ## Announcing TypeScript 6.0 RC DevFeed: [Announcing TypeScript 6.0 RC]() Original publisher: [Read original article]() Author: Daniel Rosenwasser Published: 2026-03-06T19:13:14Z Content type: release Language: en Sources: [TypeScript]() Topics: [TypeScript](), [Compiler](), [npm](), [Go](), [Document Object Model (DOM)](), [web-standards]() Tags: [features](), [javascript](), [post](), [release](), [typescript](), [updates]() ### AI overview TypeScript 6.0 Release Candidate is presented as the final release based on the current JavaScript codebase and a bridge toward TypeScript 7.0. The article covers changes since the beta, including type-checking adjustments, import assertion deprecation updates, refreshed DOM types, and improved type inference for method syntax. ### Source excerpt Today we are excited to announce the Release Candidate (RC) of TypeScript 6.0! To get started using the RC, you can get it through npm with the following command: npm install -D typescript@rc TypeScript 6.0 is a unique release in that we intend for it to be the last release based on the current JavaScript [...] The post Announcing TypeScript 6.0 RC appeared first on TypeScript. ## Launching Interop 2026 DevFeed: [Launching Interop 2026]() Original publisher: [Read original article]() Author: Jake Archibald Published: 2026-02-12T17:07:24Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [Web](), [Web platform](), [web-standards](), [browsers](), [Test coverage](), [dashboards](), [WebRTC](), [view transitions](), [CSS]() Tags: [apple](), [browser](), [css](), [featured-article](), [firefox](), [google](), [interop](), [microsoft](), [mozilla](), [uncategorized](), [view-transitions](), [web](), [web-developers](), [web-platform](), [webrtc]() ### AI overview Mozilla's Interop Project is launching Interop 2026, continuing its cross-browser effort to improve web compatibility through shared priorities and Web Platform Tests. The article reviews Interop 2025's progress, including higher overall scores, broader cross-browser support for major web platform features, and improved reliability for existing features such as WebRTC, CSS Flexbox, and CSS Grid. ### Source excerpt The Interop Project is a cross-browser initiative to improve web compatibility in areas that offer the most benefit to both users and developers. The group, including Apple, Google, Igalia, Microsoft, and Mozilla, takes proposals of features that are well defined in a sufficiently stable web standard, and have good test suite coverage. Then, we come [...] The post Launching Interop 2026 appeared first on Mozilla Hacks - the Web developer blog. ## Interop 2026: Continuing to improve the web for developers DevFeed: [Interop 2026: Continuing to improve the web for developers]() Original publisher: [Read original article]() Author: Rachel Andrew GitHub LinkedIn Mastodon Bluesky Homepage Published: 2026-02-12T08:00:00Z Content type: article Language: en Sources: [web.dev: Blog]() Topics: [Web platform](), [interoperability](), [web-standards](), [CSS](), [dialog](), [view transitions](), [browsers](), [dashboards]() Tags: [browsers](), [css](), [developers](), [dialog](), [interop](), [interoperability](), [view-transitions](), [web](), [web-platform]() ### AI overview Interop 2026 is an effort by browser-engine contributors to improve web-platform interoperability. It focuses on high-priority issues for web developers and users, including anchor positioning, container style queries, dialogs and popovers, scroll-driven animations, and view transitions. ### Source excerpt Learn about the features included in Interop 2026. ## Web Standards and the Fall of the House of Iamus DevFeed: [Web Standards and the Fall of the House of Iamus]() Original publisher: [Read original article]() Author: Alex Russell Published: 2025-09-21T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [web-standards](), [browsers](), [interoperability](), [Chromium]() Tags: [apple](), [browsers](), [chromium](), [interoperability](), [standards](), [web](), [web-standards](), [webdev]() ### AI overview This commentary argues that web standards and Working Groups generally document, refine, and spread designs that have already demonstrated value rather than determining what browsers may ship. It concludes that responsible feature development depends on thoughtful launch processes, not prior consensus. ### Source excerpt Photo by Photo by Artan Sadiku Commentary about browsers and the features they support is sometimes pejorative towards pre-standardisation features. Given Apple's constriction of Mozilla's revenue stream and its own strategic under-funding of WebKit, this usually takes the form "Chromium just ships whatever it wants." This is true, of course, but not in the way commenters intend; and not only because Blink's rigorous launch process frequently prevents unvalidated designs from shipping. Except for iOS, where Apple attempts to hide its role in undermining the competitive foundation of web standards, every vendor always ships "whatever it wants." That is the point of voluntary standards, and competition is the wind in those sails. Working Groups don't gate what browsers ship, nor do they define what's useful or worthy. There are no seers; no Delphic oracles that fleetingly glimpse a true logos. Working Groups do not invent the future, nor do they hand down revealed truths like prophets of the House of Iamus. In practice, they are thoughtful historians of recent design expeditions, critiquing, tweaking, then spreading the good news of proposals that already work through Web Standards ratified years after features first ship, serving to licence designs liberally to increase their spread. In the end, this is the role of standards and the Working Groups that develop them: to license patents that read on existing designs, reducing risks to implementers who adopt them. Anyone who tries to convince you otherwise, or invites you to try your hand at invention within a chartered Working Group, does not understand what those groups are designed to do. Sadly, this includes some folks who spend a lot of time in them. Contents Terminology Traps Standardisation != Interoperability Standardisation != Responsibility What Working Groups Really Do Chartered Working Groups Are Not Design Venues The Role of Incubation No Prophecies, Only Engineering Complaints about certain engines leading ## What is popover=hint? DevFeed: [What is popover=hint?]() Original publisher: [Read original article]() Published: 2025-07-07T00:00:00Z Content type: article Language: en Sources: [Una Kravets]() Topics: [HTML](), [Web platform](), [web-standards](), [interactive web experiences](), [JavaScript](), [ui]() Tags: [feature](), [html](), [javascript](), [learn](), [ui](), [web]() ### AI overview This article explains the popover=hint type introduced in Chrome 133. It describes how hint popovers can appear without closing unrelated popovers, including hover-based examples such as tooltips, link previews, profile cards, and comment previews. It also discusses JavaScript event listeners and experimental interest invokers for more declarative behavior. ### Source excerpt Learn about what exactly this new popover feature does and how it relates to interest invokers. ## Remixing Shopify's Admin: How We Made It 30% Faster and AI-Ready DevFeed: [Remixing Shopify's Admin: How We Made It 30% Faster and AI-Ready]() Original publisher: [Read original article]() Author: Craig Brunner Published: 2025-06-30T18:09:52Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [App](), [web-standards]() Tags: [ai](), [architecture](), [remix](), [routing](), [scale](), [shopify](), [typescript](), [web-standards]() ### AI overview Shopify describes rebuilding its Admin application with Remix to improve page-load performance, unify route information, and support large-scale collaboration across many teams. ### Source excerpt Learn how we just made Shopify's Admin 30% faster while setting it up for AI superpowers. We overhauled admin.shopify.com, transforming the system that supports 67 million daily page views and empowers merchants in managing their businesses. ## Evaluating the Value of llms.txt for AI Retrieval DevFeed: [Evaluating the Value of llms.txt for AI Retrieval]() Original publisher: [Read original article]() Author: Tiffany Chen Published: 2025-05-09T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [LLMs](), [web-standards](), [AI Trends]() Tags: [a2a-protocol](), [ai-trends](), [anthropic](), [generative-engine-optimization](), [google](), [llms]() ### AI overview The article evaluates whether llms.txt provides practical value for AI-driven discovery and retrieval. It argues that structured, simplified text files can help large language models process web content more efficiently, citing reported adoption and observations from Vercel, Google, Anthropic, and Windsurf. ### Source excerpt If you've been following AI trends, you've probably heard of llms.txt. ## The Static Website Manifesto DevFeed: [The Static Website Manifesto]() Original publisher: [Read original article]() Author: Justin Hunter Published: 2025-03-06T00:00:00Z Content type: opinion Language: en Sources: [IPFS]() Topics: [IPFS](), [Website](), [P2P](), [Web Development](), [web-standards]() Tags: [css](), [html](), [ipfs](), [javascript](), [modern-web-development](), [object-object](), [open-web](), [peer-to-peer](), [website]() ### AI overview The article presents a manifesto for making website publishing simpler and more enjoyable. It argues that IPFS is a natural fit for open websites because content addressing can provide peer-to-peer access, availability when a node serves the data, and built-in versioning for site content. It also criticizes the complexity of modern web development and advocates the continued usefulness of HTML, CSS, and JavaScript. ### Source excerpt Building websites used to be fun. Let's bring back the joy of putting your work online by using open protocols like IPFS. ## Updates to the customizable select API DevFeed: [Updates to the customizable select API]() Original publisher: [Read original article]() Published: 2025-01-10T00:00:00Z Content type: release Language: en Sources: [Una Kravets]() Topics: [browser](), [API](), [Web platform](), [web-standards](), [Web Development]() Tags: [api](), [browser](), [customizable](), [developer](), [flexbox](), [updates]() ### AI overview An update on the customizable select API describes changes since its RFC, including renamed elements, revised pseudo-elements, a less intrusive user-agent stylesheet, flexbox-based option styling, and the opt-in usage model. ### Source excerpt Everything that has changed since the RFC post for this feature. ## Shipping support for module script integrity in Chrome & Safari DevFeed: [Shipping support for module script integrity in Chrome & Safari]() Original publisher: [Read original article]() Author: Yoav Weiss Published: 2024-08-02T17:17:47Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Web platform](), [web-standards](), [Web Development]() Tags: [browsers](), [chrome](), [chromium](), [html](), [javascript](), [shopify](), [web-platform]() ### AI overview Shopify describes adding Subresource Integrity support for imported JavaScript modules in Chromium- and WebKit-based browsers. The work uses import maps to associate module URLs with integrity hashes, enabling verified dynamic imports before execution. ### Source excerpt How we shipped ES module integrity in browsers and made commerce and the web better for everyone! ## WebAssembly JSPI has a new API DevFeed: [WebAssembly JSPI has a new API]() Original publisher: [Read original article]() Author: Francis McCabe, Thibaud Michaud, Ilya Rezvov, Brendan Dahl Published: 2024-06-04T00:00:00Z Content type: release Language: en Sources: [V8]() Topics: [Web platform](), [web-standards](), [C++]() Tags: [api](), [c-plus-plus](), [integration](), [javascript](), [release](), [web-apis](), [webassembly]() ### AI overview WebAssembly JSPI has a new API in Chrome M126. The update removes explicit Suspender objects, replaces WebAssembly.Function-based wrappers with dedicated functions and constructors, and suspends calls only when a JavaScript function returns a Promise. ### Source excerpt WebAssembly's JavaScript Promise Integration (JSPI) API has a new API, available in Chrome release M126. We talk about what has changed, how to use it with Emscripten, and what is the roadmap for JSPI. JSPI is an API that allows WebAssembly applications that use sequential APIs to access Web APIs that are asynchronous. Many Web APIs are crafted in terms of JavaScript Promise objects: instead of immediately performing the requested operation, they return a Promise to do so. On the other hand, many applications compiled to WebAssembly come from the C/C++ universe, which is dominated by APIs that block the caller until they are completed. JSPI hooks into the Web architecture to allow a WebAssembly application to be suspended when the Promise is returned and resumed when the Promise is resolved. You can find out more about JSPI and how to use it in this blog post and in the specification. What is new? # The end of Suspender objects # In January 2024, the Stacks sub-group of the Wasm CG voted to amend the API for JSPI. Specifically, instead of an explicit Suspender object, we will use the JavaScript/WebAssembly boundary as the delimiter for determining what computations are suspended. The difference is fairly small but potentially significant: when a computation is to be suspended, it is the most recent call into a wrapped WebAssembly export that determines the 'cut point' for what is suspended. The implication of this is that a developer using JSPI has a little less control over that cut point. On the other hand, not having to explicitly manage Suspender objects makes the API significantly easier to use. No more WebAssembly.Function # Another change is to the style of the API. Instead of characterizing JSPI wrappers in terms of the WebAssembly.Function constructor, we provide specific functions and constructors. This has a number of benefits: It removes dependency on the Type Reflection Proposal. It makes tooling for JSPI simpler: the new API functions no longer need to ## Border images in CSS: A key focus area for Interop 2023 DevFeed: [Border images in CSS: A key focus area for Interop 2023]() Original publisher: [Read original article]() Author: dipika-bhattacharya Published: 2023-12-19T00:00:00Z Content type: tutorial Language: en Sources: [MDN Blog]() Topics: [Web platform](), [web-standards](), [Web Development]() Tags: [border-image](), [browsers](), [css](), [how-to](), [images](), [interop](), [interoperability]() ### AI overview A tutorial on CSS border images, covering the longhand properties used to source, slice, size, outset, and repeat an image around an element's border. It also places the feature in Interop 2023's effort to make browser behavior consistent. ### Source excerpt Aligning with Interop 2023's emphasis on cross-browser consistency, this post walks you through various `border-image` properties that you can control to create captivating web designs. Learn how to use custom graphics for enhancing the look of your websites that appear consistent across different browsers. ## A Chain Reaction DevFeed: [A Chain Reaction]() Original publisher: [Read original article]() Published: 2023-12-11T00:00:00Z Content type: article Language: en Sources: [Dan Abramov]() Topics: [Web Development](), [web-standards](), [CSS](), [Tailwind CSS](), [Code](), [browser]() Tags: [browser](), [code](), [css](), [tailwind](), [web-development](), [web-standards]() ### AI overview The article explains how shared names and layered abstractions make complex web behavior understandable. It connects JSX, HTML-like concepts, CSS, Tailwind classes, browser implementations, operating systems, and web standards to the process of displaying content on a screen. ### Source excerpt The limits of my language mean the limits of my world. ## Shopify's platform is the Web platform DevFeed: [Shopify's platform is the Web platform]() Original publisher: [Read original article]() Author: Surma Published: 2023-07-26T15:51:33Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Remix](), [Web platform](), [web applications](), [web-standards](), [browser](), [LocalStorage]() Tags: [applications](), [browser](), [remix](), [shopify](), [standards](), [web](), [web-development](), [web-platform]() ### AI overview Shopify recommends Remix for building Admin apps, emphasizing developer experience, performance, and alignment with the web platform and web standards. The article explains how Admin Apps operate as web apps inside cross-origin iframes and discusses browser sandboxing and storage restrictions that affect app development. ### Source excerpt Remix is now the recommended way to build Admin apps on Shopify. With Remix, you get a best-in-class developer experience while ensuring exceptional out-of-the-box performance for your app. Remix embraces the web platform and web standards, allowing web developers to use more of their existing knowledge and skills. [Next page]()