|  | Commit message (Collapse) | Author | Age | Files | Lines | 
|---|
| | 
| 
| 
| 
| 
| | 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. | 
| | |  | 
| | 
| 
| 
| 
| | With a private registry, the --with-registry-auth option can be
necessary. | 
| | |  | 
| | 
| 
| 
| 
| 
| | I also added a custom script to deploy the services with Docker Swarm.
Without it, Docker cannot read the `.env` file. Since I'm using a
variable to define the registry, the script is required. | 
| | |  | 
| | 
| 
| 
| 
| 
| | It will be useful with Docker. Instead of cloning the project with a
different configuration, I can manage two different configuration
thanks to dotenv and some checking inside the app. | 
| | 
| 
| 
| | In the context, "Vous abonner" is more accurated than "S'abonner". | 
| | 
| 
| 
| 
| | 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... | 
| | |  | 
| | |  | 
| |\  
| | 
| | 
| | 
| | | Improve maintenance (meta splitting) and try to
improve performance (dynamic imports). | 
| | | |  | 
| | | 
| | 
| | 
| | 
| | | 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. | 
| |\  
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | | I think it is better to keep styles close to the
corresponding components. So I splitted the unique
stylesheet.
I also combine select, textarea and input components
into a single one since they share the same logic and
the same styles. | 
| | | |  | 
| |/ |  | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * build: add experimental feature outputStandalone
With this option, Next.js can create a standalone folder with the
necessary files for a production deployment. It will be useful for
Docker deployment.
* chore: add Docker configuration
* docs: update README with Docker instructions | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * 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 | 
| | 
| 
| 
| | Some contents was outdated since the new version of my website. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| | * 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. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | Bumps [next](https://github.com/vercel/next.js) from 12.0.9 to 12.1.0.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](https://github.com/vercel/next.js/compare/v12.0.9...v12.1.0)
---
updated-dependencies:
- dependency-name: next
  dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com> | 
| | |  | 
| | 
| 
| 
| | Google doesn't like the id reference here. So, instead, I include the
variable directly. | 
| | 
| 
| 
| 
| | It seems Matomo need to be declared at least in connect-src in addition
to script-src.
See: https://fr.matomo.org/faq/general/faq_20904/ | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | 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. | 
| | 
| 
| 
| 
| 
| | Since v5.9, the gallery block does not use the same markup than the
previous one. So I need to duplicate the styles to make the older posts
and the new ones consistent. | 
| | |  | 
| | 
| 
| 
| 
| | I also renamed and changed the format of some environment variables so
I can reuse them inside the CSP security header. | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | 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. | 
| | |  |