Database and content
Use the built-in database in Div-idy
Div-idy includes a project database for visitor submissions and owner-managed content. Describe what should be saved and who should use it. New React and TypeScript projects connect through the built-in runtime, so you do not need to configure a separate database for these supported workflows.
What can you build with the database?
Use visitor submissions for contact forms, feedback, waitlists, and event RSVPs. Use owner-managed records for blog posts, service catalogs, menus, announcements, or location directories. Visitors can read content you deliberately publish; you manage drafts through your private Div-idy preview.
A preference such as dark mode or a personal favorites list can instead stay in the current browser. Ask for that behavior explicitly and label it “saved on this device.” It will not synchronize across devices.
Describe the data and its audience
- Name the information your app needs, such as a product title, description, category, and image URL.
- Say whether visitors submit information or browse content you manage.
- Explain which pages share those records and which filters or detail views they need.
- Specify separate Save draft and Publish controls for managed content.
In React output, Div-idy uses data.submit for forms, data.records for owner management, and data.public for published content. These are distinct permissions, even when they appear in one project.
Example: a service catalog
Build a responsive service catalog. Let me create and edit services from my private preview, with name, summary, category, and starting price as display text. Save new services as drafts. Add separate Publish and Unpublish buttons. Visitors should see only published services, filter by category, and submit an inquiry through a contact form.
Check that records really persist
Create a small sample, reload the private preview, and reopen the record. Open the Database tool to inspect saved values. Publish one record, then verify it on the visitor page. Save a later edit and confirm the public copy stays unchanged until you explicitly republish the record.
Pages sharing data must use the same collection and field names. An empty list can mean no records are published yet, rather than a failed database connection.
Choose a supported data workflow
Owner collections support up to 200 records and 256 KB total, with a maximum of 48 KB per record. These limits suit compact content collections. The built-in database does not provide private visitor accounts or each visitor’s own cloud dashboard.
Continue with content management or saving visitor forms.