| Commit message (Collapse) | Author | Age | Files | Lines | 
| | 
| 
| 
| 
| 
|  | 
* add logo to topics pages and links
* add Prism styles to articles
* and a few other adjustements
 | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
Since I'm using new components, I will also rewrite the GraphQL queries
so it is easier to start from scratch.
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
I'm not able to configure SWC plugins in Next.js so to make it works,
all translation must have an id.
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* refactor: replace script tags with next/script
Since next.js v12.1.0 some warnings was displayed because I was using
some script tags.
* build(deps): bump next-themes to v0.1.1
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
Squashed commit of the following:
commit 49c1b3b1556a0eb91c429a961fedd2bded8ffd47
Author: Armand Philippot <git@armandphilippot.com>
Date:   Wed Feb 16 15:17:52 2022 +0100
    chore: add headline field to blogPosting schema
commit 42214c6f032cc899ec252a9387be35dcad738546
Author: Armand Philippot <git@armandphilippot.com>
Date:   Wed Feb 16 15:09:11 2022 +0100
    chore: update the searchAction markup and add query-input
    Google was complaining about "query-input" which is not in Schema.org
    representation. So I added it.
commit 5f29226d937cbdcd262df2793f1588435d850f02
Author: Armand Philippot <git@armandphilippot.com>
Date:   Wed Feb 16 14:32:14 2022 +0100
    chore: remove breadcrumb from homepage
    The breadcrumb is not displayed on the homepage, so the breadcrumb
    field should not appear inside Schema markup.
 | 
| | 
| 
| 
| 
|  | 
The comments list was static before. If an user posted a comment, even
after it was approved, the comments list was keeping the old state.
 | 
| | 
| 
| 
|  | 
I forgot to change the selector to query all code blocks.
 | 
| | 
| 
| 
| 
| 
| 
|  | 
In French, "Utiliser le thème sombre" was a little too long, so instead
I decided to remove the "Toggle" word and add an icon to help user
understand the button purpose.
Same way, "Aucune étoile" was too long, so I replace it with "0 étoile"
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
The translation was not always loaded the first time. So I decided to
put the prism attributes manually instead.
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
I had errors with next build because of fallback. I need to return
early if the path does not exists, if not Next complains about
undefined variables.
I don't think it was related but I also fix the paths format in
getStaticPaths, I forgot the params object in some dynamic routes.
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
The previous method was not working so I tried a different approach.
Translation is loaded but I'm still getting warnings:
* Plurals for locale undefined aren't loaded
* Text content did not match
I can't figure how to fix them...
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
I change the name in graphql endpoint, so I decided to repercute this
change here.
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
I will need the country code, so I think it makes more sense to gather
them inside the same property.
 | 
| | 
| 
| 
|  | 
I also added the featured image on single article.
 | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
I'm now using a widget that can be expanded/collapsed. It also allows
me to handle more effectively widgets overflow and to avoid styles
repetitions.
However, with stylelint rule "no-descending-specificity", I'm not sure
if the stylesheets are really logical... Maybe I should deactivate this
rule.
 | 
| | 
| 
| 
| 
| 
|  | 
I also fix some overflow/sticky issues.
I have to set overflow auto only when there is no button-like
links otherwise, with translate, the button is cropped on hover.
 | 
| | 
| 
| 
|  | 
Only the Sharing widget needs the "min-content" width.
 | 
| | 
| 
| 
|  | 
I also adjust styles for all forms and primary buttons.
 | 
| | 
| 
| 
|  | 
This way I can use full width background for some blocks.
 | 
| |  | 
 | 
| | 
| 
| 
| 
|  | 
I will not use Prism elsewhere, so it makes more sense to call Prism
only inside articles.
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
|  | 
I was repeating myself a lot in services. So I rewrited the different
functions to improve readability and I extracted some formatting
functions to put them in utils. I also rewrited/reorganized some types
to keep consistent names.
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
|    | 
 |