I constructed BaseBuddy as a result of I saved seeing the similar downside: other people have already got just right Supabase/Postgres databases, but if they want a CMS, they typically must reshape their schema, construct a customized admin panel, or transfer content material into some other device.
BaseBuddy is a self-hosted Supabase CMS that works together with your current database at once. You attach your mission, map your tables, and get a blank WordPress-like editor for posts, media, information, search engine optimization fields, publishing, authors, and permissions.
The section I care maximum about: BaseBuddy does now not rename or reshape your tables. Commonplace saves simplest write modified fields, and post/unpublish/archive are particular movements.
It’s open supply and early, so I’d love comments from Supabase/Postgres developers:
– Is the mapping drift transparent?
– What content material workflows must we toughen subsequent?
– Would this suit your present Supabase mission?
Demo: https://demo.basebuddycms.com
GitHub: https://github.com/basebuddy-cms…
Doctors: https://basebuddycms.com/doctors
Glad to reply to anything else.
