Commit Graph

3 Commits

Author SHA1 Message Date
Emmanuel Pelletier
087bc5a889 api/gaufre: stop using an iframe
iframe was great because we controlled our page context to style things
easily, handle assets easily.

But since it's not on the same domain as the services consuming it, it
implied configuration here and there. Also some behaviors were annoying
to implement (for example, keyboard navigation). I'm sure everything we
do is possible via iframe but I feel like I'll go from barrier to
barrier at every new thing we want to do…

I feel like, at the cost of handling style-conflicts, just rendering
everything in the real page context is more future-proof.
2024-05-07 21:59:58 +02:00
Emmanuel Pelletier
c041c77360 adding 'la suite territoriale' specific gaufre button/endpoint 2024-05-02 12:58:24 +02:00
Emmanuel Pelletier
d9859f1564 first commit:
- we have a static astro website under /website. It has the
implementation docs of the homepage/gaufre templates, and it handles the
few API endpoints (the gaufre js, backgrounds, logos)
- we have a vite app under /packages/integration. It has the react
components generating the homepage and the gaufre button, and their css.
Its used to generate an npm package
2024-05-02 00:35:38 +02:00