Rethinking how @silex generates a @11ty website
Today, a user designs a page with data from a CMS → publish ⇒ page1.11tydata.js + page1.liquid (one data file + one template per page)
Problem: Eleventy can’t detect CMS changes → no `eleventy --serve` nor incremental build
It also feels off, not JAMstacky right?
What about: user designs a page → publish ⇒ _graphql/data-source1.graphql + page1.liquid
Then before eleventy we run the queries → _data/generated/data-source1.json (think wordpress.json and supabase.json )
This would be closer to Eleventy/JAMstack patterns right?
Also cacheable, works with local dev (eleventy --serve) and somewhat incremental friendly (probably not as wordpress is too broad)
Ideally I woul love it to be just markdown files generated from the CMS
Alex Hoyau