free UI sections and components / React
free React and Next.js sections and UI templates
By Andrea Buttarelli, founder of Feega
TSX components with a plain CSS file next to each one: no UI library, no runtime, works in Next.js and Vite.
61 of 61 templates
navbar, mega menu A product link that opens a wide panel of grouped links with icons; no JavaScript.sections →·components →·app UI →
what you get in React
Each item is a function component in a .tsx file with a sibling .css file imported at the top. There is no CSS-in-JS, no context provider and no dependency, so you can drop one into a Next.js app, a Vite project or React Router without changing your build.
Items without behaviour are server-friendly markup. The four that hold state, the tab list, the modal, the toast and the command palette, use useState, useRef and useId, and keep ids unique so you can render the same item twice.
Next.js app router
Hooks need a client component. Add "use client" at the top of Tabs, Modal, Toast and CommandPalette when you use them in the App Router; every other item renders as a server component. Import the CSS file next to the component, which the App Router supports from any component, and import the tokens file once in your root layout.
In the Pages Router, global CSS can only be imported from _app.tsx, so import the tokens file and each item stylesheet there.
tokens and fonts
Every item reads its colours, radii, spacing and fonts from --feega-* custom properties. Add the shared tokens file once, in your root layout or entry file, and override any token on :root (or on any ancestor) to retheme everything. Dark follows prefers-color-scheme, and data-theme="light" or data-theme="dark" on an element forces a theme for that subtree.
Items use two Google Fonts families, Inter Tight and Fragment Mono. Add one stylesheet link in the head, or with next/font if you prefer, with the weights listed on each item page. Without it, the font tokens fall back to a system stack, so nothing breaks.
changing the content and the look
Each file is short and readable. Copy, links and lists sit in the markup or at the top of the component, so replacing the placeholder content is a find and replace. Class names start with fl- and are plain selectors, so you can restyle one item by editing its CSS, or override a token to change all of them at once.
Placeholder content is marked as such: testimonials, team members and logos use obvious stand-ins, so nothing invented ships by accident. Replace them before you publish.
editing them with Feega
Once an item is in your project it is ordinary React code, so the Feega extension edits it like any other component: click it in your running app, change spacing, colour or radius in the panel, and the change is written to the CSS file next to the component, or to the className if the project uses Tailwind. Nothing is generated at runtime and no AI is involved. You review every edit as a diff.
tokens.css is the shared file every item reads.
questions
Does it work with Next.js?
Yes. Add "use client" to the four stateful items in the App Router. The others are plain markup.
Is there a TypeScript version?
Every React item is TSX. Rename to .jsx and drop the type annotations if you use plain JavaScript.
Does it use Tailwind or CSS modules?
Neither. Each item has a plain CSS file. Move it into a CSS module if you prefer.
more templates
sections →components →app UI → Svelte →Vue →Astro → all templates →
Feega edits these components in your running app and writes the change to your code. Free, with diffs and undo.
get Feega, it is free →