dashboardblocks blocks: 5 sections with preview

dashboardblocks publishes 5 blocks and 0 files in the catalogue: each entry points to an external registry, @dashboardblocks/dashboard-01 and so on. The five dashboards cover store, SaaS, analytics, CRM and DevOps.

Blocks with the most files

What this source contains

• Repository: LGLabGreg/dashboardblocks
• Site: https://www.dashboardblocks.com
• Licence: MIT (LICENSE file in the LGLabGreg/dashboardblocks repository)
• Categories: taken from the publisher manifest, not invented.

When to use it

It pays off when you want a complete dashboard and accept installing it from the publisher registry: the catalogue keeps no source. Useful for a fast prototype, less so for a security audit.

Five dashboards, zero local files

The oddest number in the catalogue is the file count: zero. The five blocks declare @dashboardblocks/dashboard-01 through dashboard-05 as registry dependencies, so the code stays on the publisher registry and is not harvested. The EneUI page shows the preview, not the source.

For anyone choosing a block this changes two things. First, verification: you cannot read the code before installing it, you have to trust the publisher domain. Second, updates: if the registry changes, your local copy never knows.

The five themes are cleanly separated, store, SaaS, web analytics, CRM, DevOps, and each brings its own data model. They are not variants of one layout: metrics, tables and hierarchy all differ. The repository is MIT and has twenty-five stars, so the code is readable after installation.

curl "https://ui.eneawork.it/api/blocks?source=lglabgreg-dashboardblocks&limit=8"

Three examples from the table: Store dashboard, SaaS dashboard, Web analytics dashboard; 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.