The post asks how many CMS collections can be used on the pro plan. The comments discuss the limitations of the current CMS offerings, with some community members suggesting that a simple CMS layer built on top of the platform's database could be a useful addition. There is no explicitly marked answer, but the community members seem to be exploring ideas for improving the CMS capabilities of the platform.
even though I agree, I won't repost it because that would incentivice community attack competitors and that's something we try to avoid, if you say the same thing but in a nicer language, I would retweet
As WS runs on CF, maybe you can build a thin CMS layer on top of their D1 DB, simple but powerful with the possibility to run SQL queries. For self-hosted users, it's still a SQLite DB API compatible they could use.
