Database and content
Build a blog with owner-managed content
Div-idy can build a blog with a private owner editor and a public feed of published posts. Manage content through the built-in project database from your private preview. Save draft keeps work private or preserves the earlier public version; Publish explicitly makes the current record available to visitors.
Choose your blog’s structure
Ask for an article list, a reading view, search or category filters, and an owner editing interface. Define the post fields together: title, summary, body, category, author label, and publication date might be enough. An optional image URL can accompany the article.
New React and TypeScript output can combine these views with shared project records. All views must use the same collection and field names. A visually polished editor still needs real database saves behind its controls.
Separate Save draft from Publish
- Save draft: creates a private post or saves changes to an existing post.
- Publish: makes the current saved content available in the public feed.
- Save later edits: keeps the existing public copy unchanged until you publish again.
- Unpublish: removes the visitor-readable copy.
- Delete: removes both the owner record and any published copy.
Ask the editor to show unsaved changes and saved changes awaiting publication. Publishing the project’s code is separate from publishing a content record.
Example: an editorial blog
Build a responsive design blog with a searchable article list and readable article view. Add an owner editor in my private Div-idy preview. Store title, summary, body, category, and an optional image URL in the project database. Include Save draft, Publish, Unpublish, and Delete controls. Show draft status and unpublished edits. Public readers should see only explicitly published posts.
Test the complete editorial cycle
- Create a post and save it as a draft.
- Reload the private preview to confirm persistence.
- Publish the post and find it on the visitor page.
- Save a changed title without publishing and verify the public title stays the same.
- Republish, then test Unpublish with a sample post.
You can inspect owner records in Database. Edits there update drafts; that screen does not change visibility. Keep owner editing in the private preview.
Plan for compact content collections
Owner collections support up to 200 records and 256 KB total, with 48 KB per record and 40,000 characters per text field. Use compact text and image references. A database record does not automatically become a separately indexed page.
For the access model, see data permissions. The same workflow also suits announcements, FAQs, menus, and small catalogs.