Collections
The list your client keeps asking you to change. Now they change it.
Menus, inventory, events, or any list you define. Start from a template, import a CSV, or describe it to your AI assistant. Your client edits it from a simple portal, even on their phone.
Templates
Start from a template, or from scratch.
Templates are starting points. Rename, add, or remove fields any time.
Menu
Dishes and drinks with prices, photos, categories, and dietary tags.
Inventory
Products or equipment with condition, category, photos, specs, and status.
Events
Courses, classes, or events with dates, location, format, and registration links.
Custom
Any list you define, with the fields you need.
More templates (team, careers, and more)Coming soon
Examples, not customers
- Restaurant menus
- Equipment inventory
- Class and event schedules
- Project galleries
- Team pages
- Job listings
- Rental fleets
- Specials and promotions
Fields
Fields your client understands.
Friendly labels and help text, because your client sees them in the portal.
- Short text
- Names, titles, and locations
- Long text
- Descriptions and specs, with simple formatting
- Number
- Quantities, years, and sizes
- Price
- Prices with currency
- Date
- A day, like a special's end date
- Date and time
- Class and event start times
- Toggle
- Sold out, featured, or available
- Single select
- One category or condition
- Multi-select / tags
- Tags, like dietary labels
- Image
- One photo, straight from the phone
- Images
- A photo set, drag to reorder
- Link
- Registration or booking links
CSV import
Already have the content? Bring it.
The menu is in a spreadsheet, the inventory is in an export from the old system. Import the CSV once and you're done hard-coding it. JSON goes through the API or your AI assistant.
- Map your spreadsheet's columns to fields
- Preview every row, with errors called out before anything is saved
- Export to CSV or JSON any time
Client portal
Your client edits it from their phone.
Each collection shows up by name in the client's portal. No dashboard to learn, no way to break the site.
- Edit items from their phone, with photos from their camera roll
- One-tap toggles like sold out or featured, right in the list
- Drag to reorder, save drafts, and publish when ready
- Items only: your fields and structure stay locked
API and MCP
Or let your assistant do all of it.
Connect the Dropl MCP server, paste this brief, and approve the plan. Your site reads published items from the public API.
Use the Dropl MCP tools to make this site's menu editable by my client. 1. Read the hard-coded menu in the codebase and propose a Dropl collection (fields, labels, help text) for it. Show me the plan and wait for my approval before creating anything. 2. Once I approve, create the collection, import the existing menu items, and replace the hard-coded menu with live Dropl data, with TypeScript types. 3. Run the project's build and tell me what changed.
// After: your client edits it in Dropl
const response = await fetch(`https://www.dropl.io/api/public/collections/${MENU_COLLECTION_ID}/items`, {
next: { revalidate: 60 },
});
const { items: menu } = await response.json();- GET /public/collections/:id/items
- Public, cached read of published items for your site.
- GET /v1/collections/:id/items
- Read every item, drafts included, with a collections:read key.
- POST /v1/collections/:id/items/bulk
- Import items in bulk, with per-row errors (collections:write).
- GET /v1/collections/:id/schema
- Current fields, plus generated TypeScript types (collections:read).
- POST /v1/sites/:siteId/collections/plan
- Dry run a schema plan and see the diff before anything changes.
- PUT /v1/collections/:id/schema
- Change fields; destructive changes need confirmation (collections:schema).
- GET /v1/collections/:id/export
- Export items as CSV or JSON.
On the way
What's coming next
- More templates (team, careers, and more)Coming soon
- Webhooks for revalidationComing soon
- No-code collection embedsComing soon
Hard-coded today. Your client's tomorrow.
Turn your next client site's lists into collections in one conversation.