Hygular is an open-source frontend UI engine I built for static HTML, React,Vue or any stack you use. Its stylesheet gives me layout utilities, theme tokens, and components I can use straight from HTML. When a page needs a dropdown, a validated form, or an interactive slider, I can add the JavaScript for that behavior from the same package.
What I get from the stylesheet alone
Take a pricing page. I want two plans side by side on desktop, stacked on mobile, with the same button styles I use in the rest of the product. I use a two-column grid for the plan cards.
<div class="is-grid grid-cols-1 md:grid-cols-2 gap-4"> <section> <h2>Personal</h2> <p>One workspace for your own projects.</p> <a class="button" href="/plans/personal">View personal plan</a> </section> <section> <h2>Team</h2> <p>A shared workspace for your team.</p> <a class="button is-primary" href="/plans/team">View team plan</a> </section> </div> md:grid-cols-2 switches the grid to two columns at Hygular's default md breakpoint of 864px. button supplies the component style, and is-primary gives the team link the theme's primary color. There’s no JavaScript in this part of the page. The CSS ships with shared design tokens, light and dark theme values, and separate cascade layers for the theme, base rules, components, and utilities.
For an account page, I can use the same stylesheet for inputs, validation feedback, and loading skeletons. When I need a tab view, dropdown, or modal, the package also supplies the interaction. The browser runtime has no third-party JavaScript dependencies.
The same seat selector in three stacks
Suppose the team plan costs $12 per seat. I want visitors to drag a slider and see the monthly price. Hygular's range component draws the filled track and positions a tooltip over the thumb. The price calculation belongs to the page. Here’s how I’d put those two pieces together in each stack.
Static HTML
With a plain HTML file, I load the published CSS and JavaScript from a CDN. Save this as index.html and open it in a browser.
<!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Team pricing</title> <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@hygular/core@1.0.0-beta.2/dist/css/hygular.min.css"> </head> <body> <label for="seats">Team seats</label> <div class="group-range" data-hygular="range"> <input id="seats" class="form-range" type="range" min="1" max="20" step="1" value="5"> </div> <output id="total" for="seats">$60/month</output> <script src="https://cdn.jsdelivr.net/npm/@hygular/core@1.0.0-beta.2/dist/js/hygular.min.js"></script> <script> new Hygular(); const seats = document.getElementById("seats"); const total = document.getElementById("total"); seats.addEventListener("input", () => { total.value = `$${seats.valueAsNumber * 12}/month`; }); </script> </body> </html> The data-hygular="range" attribute tells the runtime which element to enhance. The control is still a native range input, so my pricing code can listen to its ordinary input event. For the plan cards above, the stylesheet link is all I need.
React
For either React or Vue, install the core package and import the stylesheet once in the app entry point. In Next.js App Router, I put the CSS import in the root layout.
npm install @hygular/core@1.0.0-beta.2 import "@hygular/core/css"; In React I use useRange(). The hook gives me a ref for the wrapper and the current value for the price. It also handles cleanup when the component unmounts.
"use client"; import { useRange } from "@hygular/core/react"; export default function TeamPricing() { const { ref, value } = useRange(); return ( <> <label htmlFor="seats">Team seats</label> <div ref={ref} className="group-range"> <input id="seats" className="form-range" type="range" min="1" max="20" step="1" defaultValue="5" /> </div> <output htmlFor="seats">${(value ?? 5) * 12}/month</output> </> ); } Vue 3
In Vue, I use v-model.number for the price calculation. The template uses the same classes and data attribute as the static page. For this standalone example, the root App.vue owns the runtime.
<script setup> import { onMounted, onUnmounted, ref } from "vue"; import { Hygular } from "@hygular/core"; const seats = ref(5); let ui; onMounted(() => { ui = new Hygular(); }); onUnmounted(() => { ui?.dispose(); }); </script> <template> <label for="seats">Team seats</label> <div class="group-range" data-hygular="range"> <input id="seats" v-model.number="seats" class="form-range" type="range" min="1" max="20" step="1"> </div> <output for="seats">${{ seats * 12 }}/month</output> </template> On a larger Vue site I keep those lifecycle calls in the root and put the slider template wherever I need it. A second slider on another route doesn’t need a second runtime or a Vue-specific Hygular package.
When I’d choose Hygular
I’d use it for a product with a static marketing site and a React dashboard, or for an agency maintaining Vue apps alongside server-rendered sites. A designer can change the primary color once in the shared theme. The developer handling the static site can reuse the dashboard’s form and menu markup without adding React to the page.
Tailwind CSS gives me fine-grained utilities when I want to design a component myself. With Hygular, I can still use utilities for the grid and spacing, then reach for an existing styled range, dropdown, or modal with its behavior included. Bootstrap also combines component CSS and JavaScript. The practical difference for my projects is the React integration. Bootstrap points React users toward a framework-specific package for interactive components. Hygular ships its React hooks alongside the vanilla runtime, in the same core package. Tailwind CSS utilities · Bootstrap and JavaScript frameworks
The examples use the full stylesheet. If I want to ship CSS tailored to one site, I can add the optional @hygular/cli compiler later. It scans the project's source files and builds a stylesheet from the classes they use and the rules those classes depend on.
Hygular is MIT-licensed. If you want to see how it fits a project you already have, the component demos are a good place to start. You can try the controls in the browser and inspect the markup before installing the beta. Component documentation · Range demo · GitHub
