Disclosure widget that toggles visibility of content with smooth animation.
<Collapsible> | Prop | Type | Default |
|---|---|---|
| class | — | required |
| children | Snippet<[CollapsibleTriggerState]> | required |
<Collapsible.Content> | Prop | Type | Default |
|---|---|---|
| class | — | required |
| children | Snippet<[CollapsibleTriggerState]> | required |
<Collapsible.Indicator> extends CollapsibleIndicatorPropsCollapsibleIndicatorProps.<Collapsible.Trigger> | Prop | Type | Default |
|---|---|---|
| children | Snippet<[CollapsibleTriggerState]> | required |
ploss is a Svelte UI component library built on Ark UI. The design philosophy is to get as close to a native app experience as possible — refined visuals, cohesive interactions, and attention to detail that give Svelte projects a polished foundation from day one.
This library is actively experimenting with new organizational patterns and internal architectures — as a result, the codebase is a bit chaotic under the hood right now. Things are being shuffled around, patterns are being tested, and not everything has settled into its final form. Expect some mess while the dust is still in the air.
All component styles are extracted into dedicated styles.ts modules using a streamlined variant-based API — dramatically reducing boilerplate and keeping maintenance cost
very low. You can override anything with className or swap entire style modules without touching
component internals. Redundant abstractions have been streamlined throughout.
On the platform side, touch interactions have been fixed across many components and Android back-button handling is built in. Upcoming releases will bring mobile-native experiences — haptic feedback, sound cues, and deeper platform integration. Accessibility is treated as a long-term commitment: keyboard navigation, screen reader support, and ARIA patterns are baked into every component from the start. There is still a long way to go, but each component that gets refined brings it one step closer.
ploss is also designed with computer use in mind — AI agents are becoming a new category of UI consumers, and components need to be machine-readable as much as they are human-usable. Clear semantics, predictable interaction patterns, and well-defined state surfaces make it possible for models to understand and operate the interface — whether that means recognizing a button's disabled state, navigating a dialog tree, or filling out a form. The same foundations that make the library accessible to humans also make it legible to machines.