Dirstarter now emits domain events (tool submitted, tool published, tier upgraded, report created, and more) and can deliver them to an outbound webhook alongside the existing email notifications.

Set WEBHOOK_URL and every event starts POSTing a small JSON envelope to your endpoint. Wire it to n8n, Zapier, Make, or anything that speaks HTTP to automate whatever you like: share newly published tools on socials, ping Slack on a new report, sync to a CRM. It's off by default, and an optional WEBHOOK_TOKEN secures the receiver.

Or hand it to an AI agent

Because each event says plainly what happened and to whom, you can point the webhook straight at an AI agent node in n8n or Make and let it take it from there. Publish a tool and have the agent draft and post the social announcement. Get a report and let it triage the tool and write you a summary. Onboard a submitter with a personal follow-up. No glue code, just a prompt.

See the Webhooks documentation for the payload shape, the full event list, and how to add your own.

Directories accumulate tools faster than visitors can browse them. Collections are curated listings, saved filters over your tool query, that give people a shortcut to the slice they care about, and give you more pages to rank.

Each collection gets its own page with the full listing UI: search, filters, sorting, and pagination, all scoped to that collection.

Config-driven

A collection is one entry in config/collections.ts:

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
• 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