It's assisted programming. Very much assistance needed.
Posts by gossi
two 'cards' inside two other elements. Each 'card' has an image and button. All elements have rounded corners. The sidebar has smaller rounded corners.
inherit() is now available to play with in Chrome Canary.
Here's some writing I did about it earlier:
How CSS inherit() Could Simplify Design Systems
www.alwaystwisted.com/articles/mak...
How inherit() Can Simplify Border‑Radius for Components
www.alwaystwisted.com/articles/mak...
🙏🖤
Sounds very much like content-tag idea? This as a TC39 standard and I see this for oxc/ox-transformer.
They are adopting popular libraries (ie. styled components) as plugins now. At least plugins and not hardcoded built-in.
JSX should move into a plugin, others can join, spec can emerge :)
Hot off the press!
6.8 released with some big features 🎉
⚡@vite.dev by default
🕚 Compatible with libraries from 8+ years ago*
✨ New APIs: renderComponent, additional reactive data structures
🤝 No more hbs by default (strict: true)
Read more here:
blog.emberjs.com/ember-releas...
that's donut scoping aka @scope - not baseline yet, but spec is ready. I checked FF is the last browser that needs to support it (much better than last time I checked, where no browser had support for it).
css-tricks.com/solved-by-cs...
Great idea and good place to expressing my wishes here - thanks @jakearchibald.com
Also: Didn't know I wished for so much - all CSS and HTML for design systems (+ Temporal)
Time to tell stories in a book ✌️
Better auth supports lots of these
Great talk from @ntim.me about CSS form styling. This sounds super exciting and I already want to use it!
www.youtube.com/watch?v=WgSi...
TIL (or maybe I did know once, forgot and relearned): You can use colspan="100%" on a <td> in HTML to span it across the entire table. Especially handy, if you don't know the amount of columns you deal with.
Ember is really spoiled with some of the greatest conferences and even if you don’t use Ember but just love Frontend and great people you should come, cause you’re missing out.
Using `@hokulea/ember-pahu` from `@hokulea/ember` itself, with its pretty API to have rules for typing and linked fields.
Of course it is designed to use it from your UI library/design system, as I do use it myself. Here is the pretty version of using the form in #emberjs
(All I wanted was the rules thingy)
Demo: hokulea.netlify.app?path=/story/...
Syntax for `@hokulea/ember-pahu` using helpers and modifiers to attach them to HTML
I also made an integration for #emberjs:
🪘@hokulea/ember-pahu
To be truly headless no components were harmed; it comes with pure helpers and modifiers.
Attach it to your form elements
Syntax to create a form in `@hokulea/pahu`
I made an agnostic headless form library:
🪘@hokulea/pahu
✨ HTML first. Use native form features through a pleasent API
✨ Validation & Revalidation
✨ Validators: Native, Custom, Standard Schema
✨ Nested & initial data
✨ Linked Fields
✨ Typescript support
➡️ github.com/hokulea/pahu
Shiki + twoslash. I use it in vitepress, gives really nice code samples.
Two funny facts about Headless things:
1. When people give you a headless something as components - instant redflag ⛳
2. The headless thing is usually the head 🧠
I was at your exact point in time. I posted on svelte asking for ember test authoring format: github.com/sveltejs/sve...
The newest anwser there has a package linked to do that 🙌 Also there is sveltest.dev that's the much better docs to svelte testing.
oh whoopsie, I mixed up zod and valibot 🙈. Happy to have it in valibot, too :)
Thanks for the solution of a problem I will be going to have 😅
Also let @fabianhiller.com know about this.
I think it's great and the type first approach matches more my mental model. Also likely they even exist before the schema is around.
Theemo plugin adds these transforms in Figma (hsl only for now). Meanwhile dtcg announced the color module, which will support more formats. Will figma support them, too?
I'm also in favor of oklch, would love to see good tooling support for all ofc.
I call them constrained rsp computed values. See for example here: theemo.io/design-token...
You can find example tokens for either on:
- theemo.io/theming/buil...
- theemo.io/theming/buil...
Check the "Input" (and also learn how they are turned into CSS).
Awesome. Love the spirit!
Thanks Sam, it started as a ~30loc javascript in 2020, then I researched tokens published as the "Inside Design Tokens" Series... I'm still implementing that research results, it's grown a "little" 😅
There you go: bsky.app/profile/gos....
Design Tokens in Figma
Generated CSS with `@property`, `light-dark()` and color functions
Releasing Theemo v1.0
the end-to-end design token workflow tool:
✨ Generates Modern CSS: @property, light-dark() and color functions
✨ Integrations with @vite.dev, @emberjs.com, @svelte.dev and @vuejs.org
➡️ theemo.io
Release posts (!) in the thread.
Yes, translating them into their final form (eg css) requires knowledge about all constraints (doing that atm with theemo). That knowledge is necessary for @property, color() or light-dark(), etc.
Watch the upcoming release (writing docs about this rn).
I'm trying to coordinate pnpm catalogs with automated releases (release-plan) and automated dependency updates (renovate): github.com/embroider-bu...
I've found more use cases to what Anthony lists in his blog post: antfu.me/posts/catego...
Maybe @antfu.me you wanna jump into the discussion?
I like the DDD approach, too.... both!