|  | Commit message (Collapse) | Author | Age | Files | Lines | 
|---|
| | 
| 
| 
| 
| | * merge Columns, Gallery and CardsList into Grid component
* add more options to control the grid | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * make the component more generic
* merge `<Summary />` and `<Comment />` styles into card component
to avoid repeating the same structure
* remove most of the props to use composition
However the CSS is a bit complex because of the two variants...
Also, the component should be refactored when the CSS pseudo-class
`:has` has enough support: the provider and the `cover` and `meta`
props should be removed. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * move Prism styles to Sass placeholders to avoid repeats
* let usePrism consumer define its plugins (remove default ones)
* remove `plugins` prop from Code component
* add new props to Code component to let consumer configure plugins
(and handle plugin list from the given options)
However there are some problems with Prism plugins: line-highlight and
treeview does not seems to be loaded. I don't want to use Babel instead
of SWC so I have no solution for now. | 
| | 
| 
| 
| 
| 
| | It removes items complexity by allowing consumers to use any label/value
association. Translations should also be defined by the consumer.
Each item can now be configured separately (borders, layout...). | 
| | 
| 
| 
| 
| 
| 
| 
| | The styles applied to ResponsiveImage are related to the figure and
figcaption elements. Those elements could be use with other contents
than images. So I extracted them in a Figure component. The
ResponsiveImage component is no longer useful: the consumer should use
the Image component from `next` and wrap it in a link if needed. | 
| | 
| 
| 
| 
| 
| | The component should only be responsible of the layout for the logo,
the name and the optional baseline. Also, the homepage url could
be different from `/` so the consumer should give the right url. | 
| | |  | 
| | 
| 
| 
| 
| 
| | The flipping animation is used at several places so it makes sense to
use a single component to handle the animation. It will avoid styles
duplication. | 
| | 
| 
| 
| 
| 
| | The HeadingButton component was only used inside Widget component and
it is not very useful on its own so I merge the two components in a
new Collapsible component. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | * rename `external` prop to `isExternal`
* rename `download` prop to `isDownload`
* rewrite CSS to reduce code length and complexity
* move link styles in Sass placeholders to avoid repeats because of WordPress
articles
* move NavLink component to molecules | 
| | 
| 
| 
| 
| 
| 
| | * Column is a simple div meant to be used inside Columns component so
they should live together.
* NoScript is only used in Layout component and its name does not
make sense since it needs to be used inside a `noscript` element. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * add a `spacing` prop
* replace `layout` prop with `isInline` prop
* remove `items` prop (and classNames props) in favor of new components:
Description, Group, Term
* remove `withSeparator` prop (CSS content is announced by screen readers
and Firefox/Safari have no support for alternative text so the consumer
should add itself an element with `aria-hidden` if it need a separator)
Be aware, Meta component and its consumers can be visually broken, they
should be refactored before using them in production. | 
| | 
| 
| 
| 
| | Some components have been renamed to be able to create Footer, Header
and Nav. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | * remove `alignment` and `withMargin` props (consumer should handle
that)
* move styles to Sass placeholders to avoid repeats with headings
coming from WordPress
* refactor some other components that depend on Heading to avoid ESlint
errors | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | Both:
* move styles to Sass placeholders
Button:
* add `isPressed` prop to Button
* add `isLoading` prop to Button (to differentiate state from
disabled)
ButtonLink:
* replace `external` prop with `isExternal` prop
* replace `href` prop with `to` prop | 
| | |  | 
| | 
| 
| 
| 
| 
| | Next expect a default export for pages so only those components should
use default exports. Everything else should use named exports to
reduce the number of import statements. | 
| | 
| 
| 
| 
| 
| | Using paths aliases starting with "@" can be confusing and can lead to
conflict with existings modules. I prefer to use relative paths to
avoid extra configuration in tools because of these aliases. | 
| | |  | 
| | 
| 
| 
| 
| | Prism is adding a tabindex to code blocks, so I think an aria label
can help screen reader users to identify the tabbed content. | 
| | |  | 
| | 
| 
| 
| | I also configure Jest to avoid conflicts between Cypress and Jest. | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| | There is a bug with next/image and Storybook. I was manually adding
`unoptimized` to images. Instead we can use a workaround by adding an
extra config in Storybook `preview.js` file. | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | It avoid some hydratation errors on project pages (not in article
however) and the hooks are now reusable. | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| | * add logo to topics pages and links
* add Prism styles to articles
* and a few other adjustements | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| | The meta can have different layout. The previous implementation was not
enough to easily change the layout. Also, I prefer to restrict the meta
types and it prevents me to repeat myself for the labels. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | Add more stories for each components and change some components
categories for better organization. | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| | I replaced the deprecated VFC type with FC type and made all children
explicits.
Formatjs is still not compatible with React 18 so I need to skip type
checking when comitting. There are some type errors because of
IntlProvider in Storybook stories. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| | I was using the FunctionComponent type for some component that do not
use children. So I change the type to VoidFunctionComponent to avoid
mistakes.
I also rename all the "classes" or "additionalClasses" props to
"className" to keep consistency between each components. |