Entities

Dynamic content types: define entities such as Product, Team Member or FAQ with a JSONB field schema and manage their records in the admin, without a migration per entity. Definitions and records are stored in two tables. It adds public forms, multi-language records, collaborative editing locks and sitemap integration.

Use it when

• You need editors to manage structured content types that change often
• You want a public form (contact, application) backed by a stored content type

What it gives you

• 16 field types including text, rich_text, number, select, file, image and video
• Admin UI for definitions and records under /admin/entities
• Multi-language records when 2+ languages are active
• Collaborative editing with FIFO locking and presence
• Public form builder with honeypot, timing checks and rate limiting
• Filesystem mirroring for export/import; sitemap integration

Nothing posted about Entities yet. Read its changelog or see all PhoenixKit news.