🎉 You can now use components and fragments in your Markdown pages in Kitten.
Following on from yesterday’s Markdown pages feature, you can now import components and fragments and use them in your Markdown pages to add dynamic functionality (similar to how it works in mdx but without using JSX).
(The “SCARY” text in the screencast is being randomly animated by a component.)
You can now create HTML and CSS fragments in Kitten.
This introduces two new file extensions (.fragment.html and .fragment.css) and you can import these fragments into your pages and into other components and fragments as if they were JavaScript modules*.
[Screenshot of terminal window showing hx (Helix Editor) with two panes. Left pane, selected, shows source of Markup.fragment.html: I’m some HTML from Markup.fragment.html.
${SLOT} I’m some other HTML Markup.fragment.html.
${SLOT.other} I’m yet more HTML Markup.fragment.html.
💜 Remix / Tailwind Infinite Scroll Masonry Grid 💜 So excited to have gotten this so smooth and beautiful. It might be my favorite component thus far. It is flawless from mobile to ultraHD, from 300px to 4000px!
If you are new to accessibility, it might be sometimes hard to guess how a component is supposed to work with a keyboard.
Here are 3 design system places to look for accessible components inspiration:
React Aria Components:
Resource: https://react-spectrum.adobe.com/react-aria/components.html
Adobe’s new React framework promises components with built-in top-tier accessibility, and internationalization out of the box. Examples are nice for designers to see what’s expected in terms of keyboard navigation.
For more resources to find inspiration articles on the topic of accessible components, don't forget to check this part of my article on "Accessibility for Designers, where do I start?"
I've placed half a dozen orders in the last month and a bit, and it seems that every single one hasn't even #shipped for 2 or 3 days after I place the order. Everything I've ordered was in #stock (and not marginally; "27,563 in stock" type of thing).
2/2 I want to build a #custom#cargobike suitable for these conditions, probably based on a #bullitt, #ginkgo or #bogbi#framekit and I'd like to ask you #bicycle people for advice regarding the choice of the least maintenance intensive #components for my circumstances. What would you choose?
if you were sorting a parameter by ascending numeric value (in some sort of parameteric search engine) and the values included positive, negative, and ± values all together, where would you want the ± ones to be placed?
context is electronics stuff, where you're searching for a part that fits your required specs.
if there are parameter values that don't fit any standard format when parsed (e.g. unusual multi-element formatting, typos, other outliers) where should they appear when sorted in ascending order?
"Lexicographically" here means that a weird value like "7AD4P" or "7.38?102" would appear after all the numbers starting with 7, but before the numbers starting with 8.
consider that this may affect range searches if they are implemented.