
@zachleat First time a screenshot has this huge impact on my plans ! Thanks !
@zachleat First time a screenshot has this huge impact on my plans ! Thanks !
@eQRoeil well now you have to reveal your plans
@zachleat I need to build a website with a lot of pages (thousands). I do not want to rebuild the entire site each time an update is needed on 1 page (regularly 1 or few pages will need an update). So the plans were to **start** with 11ty, keep a limited compatibility for site wide changes and dev a solution that allow to make edits from a dedicated app that can produce the same output.
11ty running in the browser will remove or simplify some of the challenges.
@zachleat I also think it will be easier to make previews and offer alternatives to git based CMS / workflows.
@eQRoeil I don’t think you’ll want to build clientside as the user experience for end users (unless I’m misunderstanding) but the rest of it makes a lot of sense!
@zachleat not building clientside for end user (I'd take the lambda / serverless functions route or use Nuxt)
Only on the "edit app" part