#webc behaviour question for @zachleat (or anyone else familiar with it) before I go adding another (duplicate) bug.

Trying to iterate `Map.entries()` using `webc:for` per https://www.11ty.dev/docs/languages/webc/#arrays-or-any-other-iterable but getting objects that don't look like what I'd expect: with `(data, key) of x.entries()` `data` contains `[key,data]` and `key` contains the index. Destructuring further — `([key,data], idx) of ...` — doesn't work. 0.11+0.12beta. Thoughts?

Gist that may describe it better: https://gist.github.com/peterjanes/68e1eee7c71d1233b4c34e4fdbe5aa59

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/

#WebC #11ty #IndieWeb #WebDev

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/

#WebDev #IndieWeb

#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.

#11ty #webc props question! which method do you prefer? bonus points for why ✨

Option 1
<foo-component :bar="baz" :bing="boop"></foo-component>

Option 2
<foo-component :props_object="({bar: 'baz', bing: 'boop'})"></foo-component>

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'"`?

#webc