The "two endpoints" concern assumes you're fetching fragments independently. If you're composing a full page server-side, the data is already there
The "two endpoints" concern assumes you're fetching fragments independently. If you're composing a full page server-side, the data is already there
There's an example on their website where the header of a table is defined in the frontend, and the body is returned by the backend. If I wanted something as simple as switching the order of the columns, I'd actually need to create a new version of my backend endpoint, release it, change the frontend to use the new endpoint, then delete the old one. That sounds crazy to me.
There are so many gains by not using a frontend. You've greatly reduced your site size, removed duplicated logic, a shitload of JS dependencies, and an unnecessary build step.
The "header frontend / body backend" split is a choice, not a requirement. I wouldn't make that choice.
I mention it because that's the first example on the official website, so I'd assume this is the right way.