The admin panel and the user dashboard have merged into a single /app workspace. Instead of two separate areas, everyone signs in to one dashboard that adapts to their role: admins manage content, while every signed-in user gets their own submissions and bookmarks.

What's changed?

• One workspace at /app: Content management, settings, and personal pages live under a single shell, and the sidebar shows only what your role can access
• Permission-gated navigation: A declarative role model (can(user, permission)) decides what each user sees, replacing the hard split between the admin and dashboard areas
• API keys page: Manage your API keys at /app/api-keys (admin only)
• Old links keep working: /admin/* and /dashboard/* 308-redirect to their /app/* equivalents, so existing bookmarks and external links stay valid

Existing routes redirect automatically, so there's nothing to change in your deployment. Just sign in at /app.

We've migrated all UI components from Radix UI to Base UI — a lower-level, unstyled component library that gives you more control over rendering and styling.

What's changed?

• Base UI primitives — All interactive components (Dialog, Dropdown Menu, Popover, Tooltip, Select, etc.) now use Base UI under the hood
• Render prop pattern — The asChild prop has been replaced with Base UI's render prop and useRender hook for polymorphic rendering
• Tailwind Variants — Component variants are now powered by tailwind-variants instead of cva, with support for multi-element slot styling
• Updated data attributes — CSS selectors use Base UI conventions (data-open, data-horizontal, etc.) instead of Radix's data-state attributes

Breaking changes

If you've customized any UI components, you'll need to update:

• asChild → render prop — Components no longer accept asChild. Use the render prop with a callback instead
• CSS selectors — Replace data-state="open" with data-open, and similar Base UI attribute conventions
• CVA → Tailwind Variants — Variant definitions now use tailwind-variants syntax. Check for updated patterns

Blog posts are no longer stored as static MDX files. They now live in your database with a full admin interface for creating, editing, and publishing – giving you complete control over your content without touching code.

What's new?

• Rich text editor – Write posts with a Tiptap-powered editor that supports markdown formatting, media embeds, and live preview
• Post scheduling – Set posts as Draft, Scheduled, or Published with date and time controls
• Database storage – Posts are stored in PostgreSQL with automatic read time calculation
• Media uploads – Upload featured images directly through the media manager
• Duplicate posts – Clone existing posts for quick variations with a single click
• Bulk actions – Select and delete multiple posts at once from the data table

Migrating from MDX

If you're upgrading from a previous version that used file-based MDX blog posts, a migration script is included to automatically move your content to the database:

We've added tool bookmarks so your users can save tools they find interesting and come back to them later — all from a dedicated tab in their dashboard.

What's new?

• Save button on tool pages — A new "Save" button lets signed-in users bookmark any tool with a single click
• Dashboard bookmarks tab — A dedicated "Bookmarks" tab in the user dashboard shows all saved tools in a searchable, sortable table
• Quick remove — Users can remove bookmarks directly from the dashboard table

How it works

Bookmarks are stored as a simple relation between users and tools, with a unique constraint ensuring each tool can only be bookmarked once per user. When a user or tool is deleted, associated bookmarks are automatically cleaned up via cascading deletes.

The bookmark button appears alongside existing tool actions (report, embed, visit) and visually indicates whether a tool is already saved.