Decide on the tech stack and data source

[heypoom]

• Proposal: Astro with MongoDB, deploying on deploys.app
• What should we use for the headless CMS?
• Do we pull data from GitHub or Notion?

[heypoom]

I propose Astro and Tailwind for frontend - as astro can be used dynamically now, frontend-agnostic (supports all frontend libraries), and very fast.

For backend, we can decide on a headless CMS to provide our data source (keystone? contentsgarten? using markdown files on GitHub with MongoDB caching? backstage? notion?) - I'll leave this up to everyone to suggest!

[bombnp]

Keystone 6 doesn't seem to support MongoDB at the moment, no? If we're going for MongoDB, I've been using PayloadCMS with great joy. Typescript-based CMS with great DX, powerful access controls and hooks, and bring-your-own React Components for custom admin UI components and pages. It also provides REST API out of the box, if we wish to use it (Keystone doesn't seem to provide it).

It's may not have been here as long as other big-name CMSes, but I'm loving it so far. Great maintainers too with 10.8k stars on GitHub.

[heypoom]

For reference - here are a couple of CMSes supported by Astro.

https://docs.astro.build/en/guides/cms

[heypoom]

@bombnp the website for Payload looks awesome! I'll try it out - looks so easy to use.

[dtinth]

I have never used Payload but heard good things about it too. Since @bombnp said that he has experience with Payload, it’s less scary to try, as we have someone with experience. IMO, can try it for now, keep if it works or migrate if it doesn’t.

[heypoom]

Ok! Setting up Payload in the payload-cms branch now - thx @bombnp @dtinth!

[bombnp]

@heypoom I just realized that our entities seem to have a lot of two-way relationships (i think? looking from Notion). Payload doesn't have an elegant way to handle that at the moment (or MongoDB, in general). Should we look into RDBMS-based CMS instead?

[0pdd]

@heypoom the puzzle #17 is still not solved.