- Fixed the logic for the "show more" button text to correctly reflect
the current state.
- Updated button color for better visibility and adjusted styles by
removing the minimum width constraint.
- add aria attributes on load with the gaufre api script so that people
already using la gaufre don't necessarely *have* to update their code
- add the aria patterns in given code examples/react components. In some
cases, our small page load JS code isn't enough: for example on SPAs
where gaufre buttons might be loaded after page load.
thanks @inseo
not found of the lesser border contrast color but the DSFR does it, and
we can argue the color of the icon itself is contrasted
enough/positioned correctly to understand it's clickable
small test that anchors the popup to the left of the viewport, this
quickly fixes the popup going out of viewport if the Gaufre button is
used on the left of a header bar
- allows us to easily differentiate the exposed components of the npm
package vs the dev-only ones
- allows the postcss config to purgecss correctly for production build,
we do not include the classes seen in the dev components
- buttons are now back to their default display mode (the one from
.fr-btn), we just change a bit the proconnect style to match figma
design while fixing the spacing issue at the bottom of the button there
was
utility classes are great but since these are meant to be reused easily
by copy/pasting the code I feel like having less clutter in the
classnames is better
- the tagline now has a wrapper in case we want to add other content
inside the white box
- we ditch the 50/50 column logic so that the tagline takes the space it
needs
- the CSS that included the DSFR excerpt we needed styled some base html
tags directly. It might collide with a service CSS already there. Now a
postcss plugin applies a CSS prefix to everything
- we output in the lib two DSFR file versions: one with prefixed
selectors, one raw.
- 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
