Search Results for "fb2k-component"

...Melt UI introduces a builder-based architecture where component logic is encapsulated in reusable primitives that can be attached to any HTML element or custom component. The project strongly emphasizes accessibility and follows WAI-ARIA standards to ensure consistent keyboard navigation and screen reader compatibility. It also integrates seamlessly with SvelteKit and TypeScript, making it suitable for modern web development workflows.

Kuma UI is an open-source styling and component library that focuses on providing a headless, utility-first approach to building modern web interfaces. The framework emphasizes performance by extracting CSS at build time, allowing developers to create fast websites without requiring runtime styling engines in the browser. By combining utility-first styling with headless component patterns, Kuma UI allows developers to fully customize visual appearance while relying on reusable component logic. ...

...The project evolved from the Radix Vue initiative and aims to bring the same accessibility-focused component patterns to the Vue ecosystem. By providing low-level building blocks instead of finished components, Reka UI allows developers to design complex interface elements while maintaining full control over styling and behavior.

...The project builds on concepts inspired by libraries such as Radix UI and React Spectrum and integrates builder patterns influenced by Melt UI to deliver powerful component abstractions. Developers can use Bits UI to implement complex interface patterns such as dropdowns, modals, and calendars while preserving accessibility standards and predictable interaction behaviors.

The zeta.js library provides the facilities to run an instance of ZetaOffice integrated into your web site, allowing you to control it with JavaScript code via the LibreOffice UNO technology. Use cases range from an in-browser office suite that looks and feels just like its desktop counterpart, to fine-tuned custom text editing and spreadsheet capabilities embedded in your website, to a headless zetajs instance that does document conversion in the background.

...Check on your node stats, explore the IPLD powered merkle forest, see peers around the world and manage your files, without needing to touch the CLI. When working on the code, run an ipfs daemon, the local dev server, the unit tests, and the storybook component viewer and see the results of your changes as you save files. If you need to run IPFS in a Docker container, you can still have Web UI available by exposing both the Gateway and Web UI ports. The end-to-end tests (E2E) test the full app in a headless Chromium browser. They spawn real IPFS node for HTTP API and a static HTTP server to serve the app. ...

...There are two main modes for using Wraith, 'capture' mode and 'history' mode. Wraith has some built-in JavaScript and configuration file templates for you to get started with right away. If you wish to take screenshots of a component rather than the entire page, use casperjs and pass a selector along with your paths. In the 'component' example config, you can see how we specify a component name, domain path and selector we want to capture. All config options will be placed in a YAML config file. You set the headless browser, diff mode, threshold, fuzz amount and screen widths.