What is better-content?

better-content is a small TypeScript library for adding inline editing to a website you already run. Instead of building a separate admin panel, you wrap parts of your page in special components, and visitors with edit rights can click directly on the text, type changes, and save them. Those changes are stored in your own database, either Postgres or Firestore, not in a service the project runs for you. The idea is that you keep full control of your content and your data. The core engine has no ties to any particular frontend framework. It exposes a simple pattern for reading and watching data, and then React, Vue, and Svelte each get a thin layer on top so any of them can use the same underlying engine. This means a single project mixing frameworks, such as an Astro site with islands built in more than one framework, can share one editing engine across all of them. Saving and loading data goes through two small interfaces you can implement yourself: a data adapter with seven methods for reading and writing records, and a transport for sending save, patch, and remove requests. The project ships working examples for Postgres, using Drizzle, and Firestore, plus a REST transport by default, but nothing stops you from writing your own if your setup is different. On the authentication side, the project includes an adapter for Firebase, checking both an admin flag and an email allowlist before granting edit access, and visitors can also try editing anonymously in a way that never actually writes anything until access is confirmed on the server. There is also an optional inspector tool that shows a live view of your stored content while you are building, so you can see your data change as you edit fields. The maintainers describe the project as pre-1.0, meaning the way it works could still change in minor updates before it settles. It is released under the MIT license and is not affiliated with other similarly named better-prefixed tools. Setup requires Node and npm, along with a database of your choosing if you want persistence beyond the in-browser demo.