Earlier this week I posted about rough edges I encountered using WebC. I wanted to follow up with specific technical details from the ones I documented in the process of converting my website to it.

https://chromamine.com/2025/07/webc-quirks/

I’ve rewritten my #11ty blog’s templates in #WebC. I've written up the things I've found that I like—and don't like—about it.

https://chromamine.com/2025/07/switching-to-webc/

#introduction

I make websites. Sometimes I toot about it.
#eleventy #webc #php #statamic #laravel #tailwindcss #alpinejs uhhh whatever #sql and I guess #nginx #docker and all that crap all the way down. #fullstack

I play RPGs with friends. Sometimes I toot about it.
#ttrpg #dnd #pathfinder #5e #pf2e

I am my group's sysadmin. Sometimes I toot about it.
#selfhosted #plex #lemmy #mastodon #pihole and throw some darts at https://selfh.st and you catch the rest.

Hot takes, bad jokes, etc.

I just launched https://catalog.muralarts.org for Mural Arts Philadelphia. (Design by https://CooperGraphicDesign.com.)

Built with @zachleat's #eleventy, #webc, and a bastardized version of the `eleventy-image` plugin that makes optimized CSS background images. I call it back-breaker.

Rendering very many AVIF images suuuuuucked on my potato PC, but it was absolutely necessary for such an image heavy design.

I really want to like #WebC for #11ty—there’s a lot of things I do like about it, both conceptually and in practice!—but I keep running into a lot of frustrating moments that are either limitations or bugs. The documentation is pretty underspecified so it’s not always clear to me which they are.

Oh man, just figured out what I was doing wrong `:@text="exif. Flash"` was _never_ going to work. I spent much too long looking at the data.

Fortunately `@text="exif. Flash"` totally does!

@zachleat I’m guessing `:@text` doesn’t mean `@text` so we can still `:@text="'hello'"`?

@zachleat What's the state of #WebC would you say?

It's a bit hard to say by looking at the repo alone, where no commits or release can be seen in the last 1.5 years: https://github.com/11ty/webc

I see that the #11ty WebC base has seen updates recently and I noticed you mentioned it to @brad_frost the other day https://fediverse.zachleat.com/@zachleat/113319126440275811

Maybe do what @ada did to her web component helper and do a commit to update the README with current state? https://github.com/AdaRoseCannon/html-element-plus/commit/9e6d4e5ad0966f205302a804f096aaf14c15e15c

I finally finished the blog post I started 3 months ago about rebuilding my website with WebC and going all minimal design.

https://fynn.be/blog/website-rebuilt-webc/

@luke I only got into #11ty recently and read the #WebC docs first, since it felt like the most modern iteration on templating: https://www.11ty.dev/docs/languages/webc/

I combined it with #TailwindCSS, wrote some glue code, and am quite happy at the moment.

demo @ https://webcbed.netlify.app
#11ty #Eleventy #WebC

So… I got side-tracked while writing a blog post about the WebC migration of my @eleventy powered website and long story short, I created a VS Code extension for WebC instead

It’s super basic for now, providing just the `.webc` to HTML file association and suggestions for WebC-specific HTML attributes including links on hover to the documentation.

I have more plans though, for example linking tags to their respective files so you can Ctrl+Click.

https://marketplace.visualstudio.com/items?itemName=fynn.vscode-webc

Finally merged and published the WebC rework and light redesign of my website.

I’m by no means a designer (anymore) so I kept things basic and pushed myself to hit that deploy button already after weeks and weeks of being uncertain about it

The site now runs on @eleventy v3 and is fully migrated to ESM, no CommonJS anymore.

https://fynn.be

I have just released version 3.0 of Eleventy Excellent, now fully on ESM and with many other changes, including my attempts to learn more about WebC and web components. Contributions very welcome!

https://eleventy-excellent.netlify.app/blog/eleventy-excellent-30/

I would like to share some thoughts about working with #WebC.
For some time now I have been using it on a component basis in #Eleventy sites that otherwise depend primarily on Nunjucks or Liquid. The "non-traditional WebC usage" (https://www.11ty.dev/docs/languages/webc/#non-traditional-webc-usage).

For components without major complexity, this is something that works well for me. However, I have also tried to rely entirely on WebC, which, as I understand it, is the intended approach.

Finally finished the rewrite of my personal website! This time its (almost) entirely WebC!

https://andy.bond

I simplified my site a lot - largely after being inspired by @cory and his "Now" page. Previously I was rendering a page for every book, show, movie, that I tracked - and it was too much to manage!

Maybe now I will actually write something every once in a while since I will hopefully be done with large overhauls :)

I've got a cool #eleventy site in the works. Well, the actual end result will not be that interesting, but it's going to be a fun one to build.

I've got a hopelessly out-of-date Drupal site with broken deployments that I'd rather not fix, so I wrote some fairly simple scrapers to grab most of the content and directly generate new #markdown files.

It's all going to be built with #webc and a few #webcomponents.