Blocks
1st-pouf blocks: 28 sections with preview
All 28 blocks published by 1st-pouf, with categories, files and licence. The table lists the sections with the most files and links to the live preview.
Key points
- 28 application screens, almost no marketing blocks.
- MIT licence with three declared npm dependencies.
- Standalone blocks: shared state must be written by hand.
1st-pouf publishes 28 blocks in 28 files, all application screens: blog, booking, calendar, chat, CRM, dashboard. This is not a landing-page catalogue, it is a set of product views.
Blocks with the most files
| Block | Registry | File | Category |
|---|---|---|---|
| Blog | 1st-pouf | 1 | blog |
| Booking flow | 1st-pouf | 1 | booking |
| Calendar | 1st-pouf | 1 | calendar |
| Chat | 1st-pouf | 1 | chat |
| Contact section | 1st-pouf | 1 | contact |
| Course dashboard | 1st-pouf | 1 | course |
| Customer CRM | 1st-pouf | 1 | customer |
| Dashboard | 1st-pouf | 1 | dashboard |
What this source contains
- Repository: moji2002/1st-pouf
- Site: https://1st-pouf.worksonmy.dev
- Licence: MIT (LICENSE file in the moji2002/1st-pouf repository)
- Categories: taken from the publisher's manifest, not invented.
When to use it
It pays off when you are prototyping an admin tool or a booking app: screens arrive assembled and you can wire them together. The limit is depth: they are single views, not flows with shared state.
Application screens, not landing pages
The block list reads like an admin menu: Booking flow, Calendar, Chat, Course dashboard, Customer CRM, Dashboard. Almost all the marketing repertoire, hero, pricing, testimonials, is missing, which makes the catalogue more coherent.
Dependencies confirm the direction: @dnd-kit/core for dragging, react-hook-form for forms, clsx for classes. There is no Recharts or TanStack Table, so charts and tables must be built or taken elsewhere.
With one file per block, every screen is self-contained but shares no state with the others. A chat and a CRM in the same product must be wired by hand. The gain is that you can take just the calendar without adopting the rest of the catalogue.
curl "https://ui.eneawork.it/api/blocks?source=moji2002-1st-pouf&limit=8"Three examples from the table: Blog, Booking flow, Calendar; the full inventory is at /blocks. For the counting method read how the block catalogue is built, for the copy-versus-compose comparison read the economics of sections, and for heroes read the shadcn hero guide.
Frequently asked questions
How many blocks does 1st-pouf have?
Twenty-eight blocks in twenty-eight files, measured on 1 November 2026. Each block is a complete application screen, not a landing section.
What licence does 1st-pouf use?
MIT in the moji2002/1st-pouf repository. The catalogue shows see source, so the repository LICENSE file is the confirmation.
Are there marketing blocks?
Almost none: the catalogue covers blog, booking, calendar, chat, CRM and dashboard. Hero, pricing and testimonials are missing.
Which dependencies does it need?
clsx, @dnd-kit/core and react-hook-form. There are no chart or table libraries: those parts must be added by hand.
Do the screens share state?
No, every block stands alone. Wiring chat and CRM together means writing the state layer yourself, which the catalogue does not provide.