Hmm I built something like this on top of Svelte Cloudflare workers API, and the configs controller for the site itself is using a Notion table.
The reason I built this to replace a Wordpress site is because the rest of our ecosystem is a bunch of Svelte apps, and with this we could just drop content from Notion straight into our site.
We can even use fancy pants things like synced blocks for site-wide announcements, etc. etc.
One caveat with using Notion though is that without a good caching strategy (which we don't have), the site's going to be pretty slow, because Notion's API just fetches block by block. You have to have a "cache mode" for production - something that fetches and caches every X amount of time, and have users hit the cache rather than straight from Notion, since it sometimes can take 10+ seconds, which will time out your worker.
The reason I built this to replace a Wordpress site is because the rest of our ecosystem is a bunch of Svelte apps, and with this we could just drop content from Notion straight into our site.
We can even use fancy pants things like synced blocks for site-wide announcements, etc. etc.
One caveat with using Notion though is that without a good caching strategy (which we don't have), the site's going to be pretty slow, because Notion's API just fetches block by block. You have to have a "cache mode" for production - something that fetches and caches every X amount of time, and have users hit the cache rather than straight from Notion, since it sometimes can take 10+ seconds, which will time out your worker.