Xano is one of those platforms for once you learn it you feel like you can build anything. While that's mostly true, the more important thing to recognize is SHOULD you?
Let's take Headless CMS platforms, for example.
Currently, I use WeWeb for my front-end and want to build in my own custom blog. What most people do is go with a solution like Wordpress, Webflow or Framer to handle the blog. My two big issues with that is I want both my "main" site and the blog to be in a single domain (no sub-domains) and a unified navigation.
That brings us to Headless CMS solutions.
If I understand correctly, a headless CMS is a pretty straightforward solution where they have already built the dashboard where you can manage and write your articles, format them via a WYSIWYG editor, and then save all that fancy HTML into a DB and send it wherever you want via an API.
Seems like I can just build that my dashboard in WeWeb and then save my articles to Xano, which is already powering my site. But SHOULD I?
I suppose the ideal situation would be a Headless CMS solution where you can bring your own database (like Xano) and not have to pay for two DB's. Does this exist?