FEATURES
Screens that build themselves.
Quarkino Admin is generated from the core's own description of itself. Define a new content type and a working edit form and filterable list appear — with no interface code written for them.
5 of 27 catalogue features live on this page
- Settings & branding
- Global admin search
- Saved views
- Bulk actions
- Admin dashboard
What it solves
The admin panel is the part of every project that gets underestimated, then eats the timeline. It's unglamorous, it's enormous, and the client judges the entire build on it — because it's the only part they use every day.
What's in it
5 capabilities, in the order people ask about them.
Generated from metadata
- The core doesn't impose a user interface, but it does describe itself completely — the shape of every form, every filter, every list column, as data.
- So adding a content type immediately produces a working edit form and a functional list, with no separate UI build for it.
- Which means the admin panel stays in step with the data model automatically, instead of drifting behind it.
Working with lists
- Global admin search — one box across every section.
- Saved views: a combination of filters and columns saved and reused, per operator. The report someone runs every Monday becomes one click.
Bulk actions act on many records at once, with permission checks and an audit entry per record — power and accountability together.
The dashboard
- Configurable widgets, positioned by each administrator for themselves. The warehouse manager and the finance lead don't need the same home screen.
- New widget types are added through a registry, so a client-specific metric doesn't mean modifying the panel.
Settings and branding
- Colours, fonts, logo, text direction, and default language — all set from the panel, with no redeploy.
- The feature catalogue is toggled from here too. Switch a feature off and it vanishes from the menu, from search, from bulk actions, and from the dashboard.
Roles in the panel
- What an operator sees is determined by their permissions, read fresh from the database on every request. A demoted operator loses access immediately.
- A separate developer tier sits above the top administrator for installation-critical settings, so a client admin can't break their own installation.
Add a content type in the morning. Your client is editing it in the afternoon. Nobody built a screen.
Want to see the panel, not read about it?
The demo is mostly this. Bring the person who'd use it daily.
- We reply within one working day
- No sales sequence, no drip campaign
- NDA before the call if you'd prefer