UI KIT

Bento UI kit (code sections and a file for Figma)

Bento grid sections in HTML, Tailwind CSS v4 and Astro, light and dark, tested from 375 to 1,440 px wide, with a file for Figma built on the same design tokens.

€29
One-time payment

A free account is required before payment: email and password, then a code sent by email. You pay on the Stripe page.

Sold only in the 27 EU member states, excluding overseas and special tax territories (terms of sale, art. 2): billing address and payment method from this area.

Digital file delivered as soon as you pay: by ticking the box above, you waive your right of withdrawal (see the terms of sale).

Final price · VAT not applicable, art. 293 B of the French Tax Code

Commercial licence · Read the licence

BUYTRY

Overview

Description

This kit is for UI designers and front-end developers who build a landing page or a product page on a bento grid and want to start from sections that are already laid out. Each section comes in HTML with Tailwind CSS v4, as an Astro component with typed props and in a file for Figma, all on the same design tokens, in light and in dark. The grid of each section follows its own width: the sections were checked at 375, 768 and 1,440 px wide, with no horizontal scrolling, which is where a bento grid most often breaks.

Contents

  • 8 sections: hero, features, stats, gallery, testimonials, pricing, FAQ and call to action, 35 tiles in all.
  • 12 components, 28 variants: tile (6 variants), button (5), chip (5), notice (3), avatar (2), and one variant each for the input field, the segmented control, the icon badge, the keyboard key, the rating stars, the check list and the arrow link.
  • A states board: 12 button states and 4 field states, so you can see states such as hover, focus or disabled without writing any code.
  • 7 icons used by the sections.
  • 2 themes, light and dark: light by default, dark when the system asks for it, and a data-theme attribute on the html tag forces either one.
  • 9 HTML pages: a demo page that brings the whole kit together, and one page per section.
  • 8 Astro sections and 2 shared components (the section header and the icons), with a LISEZMOI-astro.txt file (French and English) that explains the setup.
  • 4 filler photos for the gallery, in WebP, each in two sizes.
  • A file for Figma (figures of the file itself, separate from those of the code): 150 variables (119 primitives and 31 semantic variables in light and dark modes), 19 text styles, 2 effect styles, 9 component sets with 41 variants, 12 single components, and 2 sample screens that carry the 8 sections, one in light and one in dark.

The text and values shown in the sections (headings, prices, ratings, testimonials) are English demo content: you replace them with your own, in the HTML or through the props of the Astro components.

Kit files:

html/index.html
html/sections/   (8 sections: hero, features, stats, gallery, testimonials, pricing, faq, cta)
html/css/kit.css
html/css/tokens.css
tailwind/theme.css
tailwind/bento.css
astro/           (8 sections, Icon.astro, SectionHead.astro, LISEZMOI-astro.txt)
assets/          (4 gallery photos, WebP)
figma/bento-ui-kit-1.0.0.fig

Production and AI

The kit’s code (HTML sections, Astro components, Tailwind theme) and the file for Figma were produced with an AI assistant, then reviewed and checked: no axe-core errors in light or dark mode, contrast checked on 24 pairs in each theme, and every spacing on the 4 px scale. The 4 demo gallery photos were generated with AI using Krea’s krea-2 model, then cropped.

Formats and compatibility

  • HTML and compiled CSS, no CDN: html/index.html and the pages in html/sections/ open in a browser, with no install and no build step. html/css/kit.css holds the compiled CSS of the kit.
  • CSS custom properties, light and dark: html/css/tokens.css carries colors, spacing, radii, shadows and text styles as CSS variables. These are the tokens of the Beryl Design DTCG starter, plus a few values specific to the kit.
  • Tailwind CSS v4 (theme and entry file): tailwind/theme.css replaces the default palette, spacing, radii and type scale with the kit tokens, and tailwind/bento.css is the entry file to import once. The kit uses no arbitrary values: a missing value is added as a token first.
  • Astro components with typed props (TypeScript): each section exports its Props interface, and every prop is optional. You need an Astro project with Tailwind CSS v4; the steps are in LISEZMOI-astro.txt.
  • .fig file (figma/bento-ui-kit-1.0.0.fig): a file for Figma with variables, styles, auto layout components with variants and sample screens, to import into your workspace.
  • Fonts: Geist and Geist Mono, under the SIL OFL 1.1 license, are loaded through a link and are not included in the kit.

What was checked on the demo: spacing on a 4 px scale, contrast of 24 color pairs in each theme, no accessibility error reported by axe-core in light or in dark.

Before you buy:

  • The file for Figma shows the sections at 1,440 px only, in light and in dark. It has no 375 or 768 px screen: those widths are covered by the code.
  • In the file for Figma, the rows of the bento grid have a fixed height. If you lengthen a text, enlarge the row by hand.
  • In an Astro project, copy the photos from assets/ into public/ to show them in the gallery, as LISEZMOI-astro.txt explains. Without a photo, the gallery shows a visual drawn in CSS.
  • The 4 gallery photos were generated with AI (krea-2 model) for this kit. They show no text, no logo and no face.

License

The kit is sold under the commercial license: you may use the sections, the components and the file in your personal and professional projects, including for your clients and in the websites or apps you sell, but you may not resell or redistribute the kit files, even modified, as a kit or a template.

Further reading

Version history

1.0.0 (November 10, 2026): first release.

About the author

Frequently asked questions

How does the kit keep a bento grid readable on mobile?
Each section is a container whose grid follows its own width, not the width of the window: a section placed in a narrow column still fits. When space runs out, the main tile comes first at full width, then the others follow in an order set for each section, at full width or two by two. The sections were checked at 375, 768 and 1,440 px, in light and in dark.
Do I need Tailwind CSS to use the kit?
Not for the HTML version: it relies on the CSS that is already compiled (kit.css) and on the variables of tokens.css, with no CDN. Yes for the Astro sections and to edit the kit with classes: they need Tailwind CSS v4, whose theme is included.
Does the file for Figma match the code exactly?
It has the same 8 sections, in the same order, with the same grid areas and the same color values, in light and in dark. It differs on these points: it only shows the 1,440 px width, its grid rows have a fixed height, and the gallery only exists with the photos, without the version drawn in CSS.