feega

free UI sections and components / Astro

free Astro sections and UI templates

By Andrea Buttarelli, founder of Feega

Astro components that ship no JavaScript unless an item needs behaviour, with scoped styles and shared tokens.

61 of 61 templates

sections →·components →·app UI →

what you get in Astro

Each item is one .astro component: markup on top, a style block at the bottom. Most items ship no JavaScript at all, which suits Astro. The four with behaviour, the tab list, the modal, the toast and the command palette, include a small TypeScript script that Astro bundles and runs once per page, even if you use the item twice.

Nothing needs a framework integration. You do not need React, Vue or Svelte installed to use these, and there are no islands to hydrate.

using them in a page

Place files in src/components and import them in a page or layout: import HeroSplit from "../components/HeroSplit.astro". Import the tokens file once in your base layout, and add the Google Fonts link in its head.

tokens and fonts

Every item reads its colours, radii, spacing and fonts from --feega-* custom properties. Add the shared tokens file once, in your base layout, 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 layout head, with the weights listed on each item page. Without it, the font tokens fall back to a system stack, so nothing breaks.

static output and scoped styles

Items work with Astro's static output and with server rendering alike. Styles are scoped by Astro, so nothing leaks into other components, and the tokens file is the only global CSS they need.

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 Astro 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 into the component's style block, or into the class 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

Do these add client JavaScript?

Only the four stateful items, with a few lines each. The rest are static HTML and CSS.

Do I need another framework for Astro?

No. They are plain .astro components with no framework integration.

more templates

sections →components →app UI → Svelte →React →Vue → 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 →