Dynamic Content forStatic Websites

A spreadsheet-style content store built into your Dplooy dashboard. You create a collection — a menu, a team list, an FAQ — and it gets a public URL that serves the rows as JSON. Your website fetches that URL and renders the content, so editing a row in the dashboard changes what every visitor sees, without touching your site's files.

Within about a minute. The published data is cached briefly so busy sites stay fast; every save republishes it, and visitors pick up the new version on their next page load after the cache window passes.

Once. Your page needs one fetch() call to the collection's URL — we give you a copy-paste snippet, or an AI prompt containing your URL and exact field names that you can paste into ChatGPT, Claude, or any AI builder so the generated page is wired up from the start. After that, all changes happen in the dashboard.

No — and that's by design. The data renders on your public website, so the endpoint is public: anyone with the URL can read it. Use it for content you'd happily put on a web page, and never for passwords, customer details, or anything sensitive.

A collection serves its rows once it's assigned to one of your Dplooy-hosted projects. You can create it earlier — the URL exists immediately and returns an empty list until assignment, which is handy when an AI is building the page before you've deployed. Need the same content on a second site? Duplicate the collection; each copy has its own URL.

Seven: text, long text, number, image, link, date, and yes/no. Images come from your account's Media Library — you pick from what you've uploaded, and the published data carries a permanent image URL.

All of them. The endpoint is a plain JSON URL with open CORS — your own code does the fetching and rendering, so it works identically in any framework, on any page, including AI-generated single-file sites.

No. Edits take up to a minute to reach visitors because the data is cached for speed. It's built for content that changes daily at most — menus, prices, team pages, FAQs, event lists — not live availability.

Nothing happens to your collections. They belong to your account, not the project — deleting a site just un-assigns them, and they keep your rows until you assign them to another project or delete them yourself.

This is exactly what Dplooy Data is for. AI tools generate a finished page with your content baked in — so changing a price normally means regenerating the whole page. Instead, create a collection, copy our ready-made AI prompt, and paste it into ChatGPT, Claude, v0, Lovable or any AI builder. The page it generates fetches your content from your collection's URL, so from then on you update the site by editing rows in your dashboard — no more regenerating.

Yes — it's one of the built-in presets. Create a Menu collection (name, price, description, image, available) and your site renders it from the live data. Change a price or mark a dish unavailable from your phone, and the menu on your website updates within a minute. No calling your web person, no re-uploading anything.