<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #webcomponents</title>
    <link>/tags/webcomponents/</link>
    <description>Recent bookmarks tagged #webcomponents</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:48 +0000</lastBuildDate>
    <item>
      <title>Do web components have a future if nobody is writing them? | Read the Tea Leaves</title>
      <link>https://nolanlawson.com/2026/10/19/do-web-components-have-a-future-if-nobody-is-writing-them/</link>
      <description>So whatever happens to web components in the future, and regardless of whether web developers ignore them, forget them, celebrate their demise, or write them off entirely, nothing can take this victory away from them. They are woven into the texture of the web platform in a way that can never be undone. For me, this makes me happy even if I never write another web component again.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 20 Oct 2026 18:04:49 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38812</guid>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/2870208ec4168f9a507c409d67c76446.webp" type="image/webp"></enclosure>
    </item>
    <item>
      <title>How building an HTML-first site doubled our users overnight</title>
      <link>https://mohkohn.co.uk/writing/html-first/</link>
      <description>It is not acceptable to bounce users on old browsers, users with bad network connections, users using assistive technologies. Certainly not from a monopoly public service. A lot of hype and noise is pressing us to extend the cowboy, wild-west phase of the software industry’s expansion. We should set that aside, and take ourselves seriously as a mature industry. Build a web application that works on a playstation portable on a 3G connection - if you do, it will work for all your users, and it will still work 30 years from now.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #accessibility #html #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 18 Jun 2026 19:52:25 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38585</guid>
      <category>accessibility</category>
      <category>html</category>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/ab3cdae09a84d8b8a9e724cdafadd8c6.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>Elena | Progressive Web Components</title>
      <link>https://elenajs.com/</link>
      <description>Elena is a simple, tiny library for building Progressive Web Components. Unlike most web component libraries, Elena doesn’t force JavaScript for everything. You can load HTML and CSS first, then use JavaScript to progressively add interactivity.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Sat, 02 May 2026 17:46:40 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38501</guid>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/da871de56896cf272d6a1e8ecbac942f.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Progressive Web Components | Ariel Salminen</title>
      <link>https://arielsalminen.com/2026/progressive-web-components/</link>
      <description>A Progressive Web Component is a native Custom Element designed in two layers: a base layer of HTML and CSS that renders immediately, without JavaScript, and an enhancement layer of JavaScript that adds reactivity, event handling, and more advanced templating.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #css #html #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Sat, 02 May 2026 17:44:34 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38500</guid>
      <category>css</category>
      <category>html</category>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/4faf146ab0703fea6f55e5d9cbc00c7b.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>Under the hood of MDN&#39;s new frontend</title>
      <link>https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/</link>
      <description>Last year, we launched a new frontend for MDN. The most noticeable changes were adjustments to our styles; we simplified and unified the MDN design across all of our pages. In truth, the biggest changes were not reader-visible, but rather in the overhauled code that powers our frontend. This post describes what we&#39;ve done, the technologies we chose, and why we did it at all.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #mdn #mozilla #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 15 Apr 2026 16:50:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38461</guid>
      <category>mdn</category>
      <category>mozilla</category>
      <category>webcomponents</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Fully Local Code Embeds | Aleksandr Hovhannisyan</title>
      <link>https://www.aleksandrhovhannisyan.com/blog/local-code-embeds/</link>
      <description>A few years ago, I was looking for a way to add interactive code sandboxes to my Markdown files without embedding third-party iframes, like the ones from Codepen or Codesandbox. Those services are great and I use them all the time to share demos, but I’ve never been a fan of using them on a blog since you have to jump back and forth between your local Markdown file and an external site to make changes to the demos. Plus, they typically load lots of JavaScript.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #metablogging #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 31 Mar 2026 01:15:24 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38442</guid>
      <category>metablogging</category>
      <category>webcomponents</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How To Dynamically Install Custom Elements: HeydonWorks</title>
      <link>https://heydonworks.com/article/dynamically-loading-custom-elements/</link>
      <description>Today, I want to look into one very specific topic in excruciating technical detail: how to dynamically load custom elements.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #customelements #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 30 Dec 2025 03:23:45 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38160</guid>
      <category>customelements</category>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/c250b9c67fdf86a41ac4eaf0ff7b56dd.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>The handleEvent() method is the absolute best way to handle events in Web Components | Go Make Things</title>
      <link>https://gomakethings.com/the-handleevent-method-is-the-absolute-best-way-to-handle-events-in-web-components/</link>
      <description>A bunch of people shared their own approaches, but the one that absolutely blew my mind was the handleEvent() method, a platform-native method for managing all of the events on your Web Component.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #customelements #js #web #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 19 Dec 2025 01:04:04 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38129</guid>
      <category>customelements</category>
      <category>js</category>
      <category>web</category>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/bd4be4654582fd450804cdeb64319352.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Custom Asidenotes  –  Eric’s Archived Thoughts</title>
      <link>https://meyerweb.com/eric/thoughts/2025/10/29/custom-asidenotes/</link>
      <description>Previously on meyerweb, I crawled through a way to turn parenthetical comments into sidenotes, which I called “asidenotes”.  As a recap, these are inline asides in parentheses, which is something I like to do.  The constraints are that the text has to start inline, with its enclosing parentheses as part of the static content, so that the parentheses are present if CSS isn’t applied, but should lose those parentheses when turned into asidenotes, while also adding a sentence-terminating period when needed.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #customelements #metablogging #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Tue, 02 Dec 2025 01:57:37 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38047</guid>
      <category>customelements</category>
      <category>metablogging</category>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/947f8b9934f8cdf2fc08a01873822418.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>Syntax Highlighting in Web Component Templates</title>
      <link>https://remysharp.com/2025/11/12/syntax-highlighting-in-web-component-templates</link>
      <description>The extremely quick read is, add /* HTML */ to the front of the template. Case sensitive and space sensitive (though hopefully one day it won&#39;t be so strict). Now highlighting and prettier (with save and fix) works.&#xA;&#xA;Note that you need the es6-string-html VS Code extension for this to highlight correct (something I had forgotten I had installed).&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #html #vscode #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 12 Nov 2025 20:07:33 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37947</guid>
      <category>html</category>
      <category>vscode</category>
      <category>webcomponents</category>
      <category>webdev</category>
    </item>
    <item>
      <title>HTML is for lovers | Go Make Things</title>
      <link>https://gomakethings.com/html-is-for-lovers/</link>
      <description>I’ve had the opportunity to use Kelp on a big client project for the last few weeks, and it’s been so awesome to work with!&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #html #kelp #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 12 Nov 2025 20:06:20 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37946</guid>
      <category>html</category>
      <category>kelp</category>
      <category>webcomponents</category>
      <category>webdev</category>
    </item>
    <item>
      <title>The killer feature of Web Components - daverupert.com</title>
      <link>https://daverupert.com/2025/10/custom-elements-manifest-killer-feature/</link>
      <description>One unsung feature in the web components space that I don’t think gets enough attention is the Custom Elements Manifest initiative. I think it’s the killer feature of web components.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #customelements #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 15 Oct 2025 17:10:46 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37809</guid>
      <category>customelements</category>
      <category>webcomponents</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Split Flap</title>
      <link>https://fx.hot.page/split-flap?ref=sidebar</link>
      <description>As an ode to the train stations of my childhood, I bring you a skeuomorph split-flap web component&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #css #js #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Mon, 28 Jul 2025 16:24:13 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29409</guid>
      <category>css</category>
      <category>js</category>
      <category>webcomponents</category>
      <category>webdev</category>
      <enclosure url="https://links.lmorchard.com/static/29b4077eb9462985e80dede13833be55.webp" type="image/webp"></enclosure>
    </item>
    <item>
      <title>Building a QR Code HTML Web Component | Scott Jehl, Web Designer/Developer</title>
      <link>https://scottjehl.com/posts/q-r/</link>
      <description>Recently, a friend asked if I knew of a Web Component that generates a QR Code from meaningful HTML. She said that there seemed to be plenty of options for creating QR codes in general, but none that worked by extending already-useful HTML instead of just configuring it all with JavaScript. I couldn&#39;t find any either, but thinking through these kinds of patterns is probably what I enjoy most about working on the web, so I thought I&#39;d write up how I&#39;d make one.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #qrcodes #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 31 Jan 2025 23:29:21 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29682</guid>
      <category>qrcodes</category>
      <category>webcomponents</category>
      <category>webdev</category>
    </item>
    <item>
      <title>A Web Component to expand or collapse all details elements | Go Make Things</title>
      <link>https://gomakethings.com/a-web-component-to-expand-or-collapse-all-details-elements/</link>
      <description>Today, I wanted to share a little Web Component I made for expanding or collapsing all of the &lt;details&gt; elements on a page.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #webcomponents #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 27 Nov 2024 23:46:47 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29807</guid>
      <category>dev</category>
      <category>webcomponents</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
