|  | Commit message (Collapse) | Author | Age | Files | Lines | 
|---|
| ... |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | I'm not able to configure SWC plugins in Next.js so to make it works,
all translation must have an id. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * refactor: replace postBy query
postBy is now deprecated in WPGraphQL v1.7
* refactor: update post comments query
PostBy is deprecated and it is now possible to use the post ID to query
comments.
* refactor: update get topic by slug query
topicBy is deprecated
* refactor: update get thematic by slug query
thematicBy is deprecated | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | * chore: add a Pagination component
* chore: add blog pages
* chore: fallback to page number based navigation if JS disabled
* chore: update translation | 
| | |  | 
| | 
| 
| 
| 
| | When posts count equal zero (search page for example), only O was
printed instead of "Total: No articles". | 
| | 
| 
| 
| 
| 
| | Due to translateX transform and overflow, on small screens a zoom in /
zoom out effect happened. So I adjust the animations for branding and
job. | 
| | 
| 
| 
| 
| | Instead of align them to left on small screens, I decided to centered
them. | 
| | 
| 
| 
| 
| | Since I translated to French, the text did not fit into container on
small screens. It is not perfect, but I plan to replace Ackee so... | 
| | |  | 
| | 
| 
| 
| 
| | The comment form is displayed only if an user click on the reply button
so importing it dynamically should improve performances. | 
| | 
| 
| 
| 
| | These components are only available after a click from the user, so
using dynamic import should improve performances. | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * build(deps): add use-ackee hook package
* chore: create a context provider for Ackee
The provider allows users to change the 'detailed' settings.
* chore: add a select menu to choose which info to share with Ackee
* chore: add a tooltip for askee settings
* chore: replace default select styles with custom styles
* chore: register user choice in localstorage
* chore: replace Matomo with Ackee in legal notice | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| | * 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 | 
| | 
| 
| 
| 
| | I do not use all Matomo features so I was searching a lightweight
analytics tools. I will give a try to Ackee. | 
| | 
| 
| 
| 
| 
| | Animations based on width or height can be expensive and can cause
lower performances. So, instead I use transform to obtain the same
effect. | 
| | 
| 
| 
| | Because of the default padding on button element, in some browsers
the plus/minus icon on widgets was cropped. | 
| | 
| 
| 
| | Google doesn't like the id reference here. So, instead, I include the
variable directly. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | 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. | 
| | |  | 
| | 
| 
| 
| 
| | By fetching the data in getStaticProps, I can display the data even
for users with Javascript disabled. | 
| | 
| 
| 
| | This way, even whithout JS, user can see the latest posts. | 
| | 
| 
| 
| 
| 
| | When the main nav was opened, a double click on the search button or
the settings button was necessary to open a new menu. Now, it works as
expected: the main nav is closed and the menu is opened in one click. | 
| | |  | 
| | 
| 
| 
| 
| | 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. | 
| | 
| 
| 
| 
| 
| | The "Mentions légales" link was not enough visible on small viewports
because of the back to top link. So I change the disposition to improve
that. | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| | 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" | 
| | 
| 
| 
| 
| 
| | On small screen, they was too small I think. I also change some
styles like focus state to keep consistency between all elements in
toolbar. Also, I was not fan of the rotate effect. | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| | With `overflow-y: hidden`, the content was printed before the max
height transition end. Switching to `overflow: hidden` fixed this
issue. | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| | * Make all widgets expanded by default. This way, without Javascript,
thematics and topics are still available.
* Improve collapse/expand transition.
* Remove widget scrollbar: the height was sometimes weird because of
that. Except for ToC on large devices. |