Posts category's feed

[Post] New year, new version

Fri, 02 Jan 2026 00:47:00 GMT

It’s been a year since I put online this website and I must admit, I haven’t published much since then. I quickly embarked on technical changes and then let things drag on. As I had some changes pending, the editorial aspect was completely neglected.

So, what’s new in this version?

Mainly technical improvements

From a technical point of view, nothing changes; this website still uses Astro! However, I brought some changes to reduce code duplication and improve my developer experience.

Simplified routing

I refactored my way of using Astro’s built-in routing. Previously, templates were duplicated both per content categories and per language.

Now I have a single page template responsible for choosing the layout without worrying about the language and I no longer translate any routes in the source code. This means that if tomorrow I want to reuse my code for another website and I prefer to use “articles” instead of “posts” in the URL, this is now possible!

Use of view transitions

Now that Firefox also supports view transitions, I decided to test them on this website. I’m not using any fancy animations. However, navigation between pages now seems smoother, which should please those used to single-page applications (SPA).

Bug fixes

I noticed a performance issue on mobile due to the SVG used for the background. It seems the best way to fix this is to use a static image instead of my previous method. Doing so led me to adjust other things, such as the website’s colors.

I also cleaned up the source code after noticing it contained extra, unwanted attributes. It seems that when using spread syntax with slots, Astro automatically adds slot as an attribute instead of removing it after use.

Graphical changes

The most noticeable change is probably the logo. I wasn’t satisfied with the previous version and the rendering was good in Firefox quick links or in Google search results. The first point is now fixed. All that remains is to wait and see how the rendering on Google improves.

Then, I also updated how the site settings are displayed. While changing the theme might be considered a secondary feature, switching between languages should be immediately visible to website users. So I removed the modal — only for large viewports, like a computer screen — and everything is now configurable directly from the navigation bar.

Refined dark theme

The dark theme has been improved. At least, I hope so. I mostly use the websites light mode and only switch to dark mode in the evening or at night. When I switch over, I also automatically activate Redshift. This was an important point I hadn’t considered a year ago, and the color choices were therefore rather disappointing.

This new dark theme is… darker, and the blue-grey tone is now respected by Redshift. At least, with my settings. I took the opportunity to update the shadows and border colors. I think, overall, this looks better than before.

Minor layout changes

This new version includes:

larger blank spaces in various parts of the site, which I think improves readability;
a different layout for page titles and cover images;
a more reasonable size for the buttons available in code blocks.

What’s next?

I think what I wrote a year ago in “A New Site” still applies. I have improved my development experience but I already see other improvements that are maybe more focused on the editorial side than development this time.

I will also try to post a bit more often. In particular, I plan to write an article on how I create my routes because I have been asked to do so and because route translation management is a question that comes up often. That said, I make no promises regarding its publication date…

In the meantime, I wish you a happy new year!

[Post] Contribute to the Astro's project

Sat, 08 Feb 2025 23:53:00 GMT

I’ve been using open-source projects for a long time, but I’ve never really contributed to an existing project. I’ve created a few issues or fixed one or two minor bugs or typo in the documentation, but I’ve never tried to get involved.

Then, in 2024, I finally found a project that made me want to participate. This project is called Astro! A year later, I share with you my journey and some ideas if you also want to get started.

What is a contribution?

Before I venture further, I think it’s important to define what I mean by contribution. For many, participating in an open-source project is synonymous with coding. Sure, coding is a valuable skill that’s applicable to all projects, but there are other ways to contribute.

In my opinion, any act that helps to evolve a project can be called a contribution:

Are you experiencing a bug? Create a detailed ticket with a minimal reproduction so that it can be fixed and does not happen to other people!
Do you know how to fix a bug? Feel free to create a “pull request” (or “merge request” depending on the platform)!
Are you more comfortable with words? Consider looking at what can be done on the documentation!
Are you fluent in English and another language? Feel free to see if you can help translate the documentation!
Not comfortable enough in English to translate? You can always review the translations submitted in your language and approve or suggest improvements!
Have you always enjoyed getting answers to your help requests? You can do the same by providing technical support to other users!

Well, you get the idea! There are many ways to contribute to a project. All kinds of skills can be useful.

My journey as an Astro contributor

A year ago, I decided to test Astro. I’m experiencing a problem but can’t find the information in the documentation. Rather than opening an issue in the main repository of Astro, I’m looking to see if a similar issue has been reported before. It turns out that it has and that it’s not a bug. Since it seems that I’m not the only one experiencing this issue, I figure the documentation should make that clear.

Issues opening

I thus create my first issue in the Astro Docs repository. This issue didn’t get a response right away, but that didn’t stop me from creating other issues in the other repositories when I encountered an issue that looked like a bug to me.

It’s not always obvious at first which repository to report the issue to. It’s possible to do it in the main repository… but I prefer it when I post in the right place the first time. These issues allowed me to get familiar with different repositories of the project: the core, the docs, the compiler and the language tools.

I was surprised by the reception; it’s pretty rare that someone thanks me for creating an issue! In itself, it’s not important. As long as the problem is fixed, that’s all that matters. That said, I recognize that this kind of reception makes a difference, especially when you’re not sure if it’s a bug or the expected behavior.

Followed by pull requests

I then took the opportunity of an issue labeled “Good first issue” (meaning: newcomers are welcome) to make my first PR in Astro’s main repo! The goal was to convert a remark plugin to a rehype plugin.

In June, my first ticket (related to documentation) was close to being solved, all that was missing was a PR. So I took that opportunity to do it myself.

The various interactions with the Astro team and contributors made me want to continue contributing. So I looked at what could be within my capabilities.

Involved in Astro Docs

Since I was learning how to use Astro, I decided to linger in the Astro Docs repository.

French translations

The documentation wasn’t completely translated in French. So I tell myself that participating in the translation would be a great way to be more familiar with Astro concepts!

I started by updating some translations and creating some missing translations. I also reviewed translations submitted by other contributors.

Participating in translation made me discover a new tool: Lunaria. If you’re maintaining a multilingual documentation, I recommend you to take a look!

Reviewing the English documentation

I was curious to see the process of building the documentation as a whole. At the same time, Astro version 5 was appearing as a beta. So I started looking at other PRs and tickets, this time in English.

I was certainly less comfortable reviewing the English wording, but I was able to make myself useful by fixing any typos or formatting issues.

Various documentation improvements

While translating in French, I sometimes noticed some typos or formatting issues in the original version; this was a good opportunity to get a foot in the English documentation by correcting them.

Then I decided to make some improvements to the API Reference page. The idea was to bring a bit more consistency, add missing information and fix any errors. This gave me the opportunity to exchange with another member of the team.

When v5 was still in beta, I finally tested the Astro tutorial! A bit late… but there was no question of learning here. I wanted to help verify that everything was working correctly and make changes where necessary. I must say that it covers the concepts necessary to quickly get started with Astro!

Participating to the “Talking & Doc’ing” event

Every Thursday, or almost, a “Talking & Doc’ing” event is organized on the Astro’s Discord server. The idea behind this event is to discuss the best way to handle certain issues, changes to be made to a current PR, changes to the organization of the documentation, etc. Since I was interested in the process of creating the documentation, I finally decided to attend.

Since then, I continue to attend to this event. I say “attend” rather than “participate” because I must admit that I am rather passive. To begin with, I don’t really like speaking even in French (which can contrast with my writing). Then, as much as I can write in English, I am not particularly comfortable speaking in English. So, I leave my webcam (for the microphone) put away and I intervene only in writing. I must admit, it is not practical especially when it comes to discussing a PR created by oneself… Maybe one day I will decide to intervene orally.

A bit of technical support

I would sometimes answer questions about Astro on StackOverFlow. Then, when I started translating the Astro documentation, I joined Discord so I could coordinate with other translators and avoid having to submit a duplicate translation. I then started to intervene occasionally in the support channel.

Besides that, I try to help sort issues from the docs repository and from time to time, those from the core repository. If I see an issue that has already been addressed, it’s an opportunity to propose a solution or refer to a ticket that already covers that case.

Contributions leading to surprises

In December 2024, Astro 5 finally becomes stable. A blog post accompanies its official release. I already knew the different changes brought but I still read it with attention. Surprise at the bottom of the page: I saw my name in the acknowledgments!

Then, in early 2025, I received a direct message on Discord from the co-founder of Astro. He offered me to join the Astro maintainers team. I wasn’t expecting it. I’ve certainly been quite active since June, but I didn’t think I would be trusted enough for this role and so quickly. Of course, I accepted this opportunity and I thank the team again for this trust!

The integration of new maintainers into the project is based on a system of nomination and voting. It is not voluntary or by application. Which explains why I was surprised.

Finally, in October 2025, I received a new direct message from the co-founder of Astro to offer me, this time, to join the Astro core team! Obviously, I accepted; all I have to do now is become more comfortable speaking English, haha.

Let’s take stock

I’m not going to hide it from you, yes, I found it a bit intimidating. To begin with, I’m more of an introvert and I’m not particularly comfortable communicating in English. Then, not being used to participating in open-source projects, I wondered if I was doing the right thing by intervening a bit everywhere (and especially in the Astro team’s PRs) or if it was too much…

That said, I don’t regret having started and getting involved in this project. I have to say that the welcome within the Astro community is no stranger to that. I have no doubt that there are other welcoming projects out there, but, I don’t know, there’s a little something extra. So, I’m glad I stumbled upon this project and to be part of it!

For now, I plan to stay on the documentation side even though I know it pretty well now. There are always things to do, and I can practice technical writing in English. No, maintaining the docs is not just about fixing typos. In fact, it even have the right to its own documentation website!

Want to join?

Astro project architecture

Astro has several repositories, here are the main ones:

withastro/astro which contains the project’s core;
withastro/compiler which is used behind the scenes to transform templates;
withastro/language-tools which focuses on the tools editors need to understand Astro syntax;
withastro/starlight which contains the sources for the tool dedicated to creating documentation sites;
withastro/docs which contains Astro’s documentation (and its translations);
roadmap which allows you to propose ideas (and to discuss these ideas) in order to develop Astro features.

All kinds of skills can be useful

Multiple repositories also mean diverse skills. For example, if you are more of a Go developer, you might be interested in the Astro compiler, while for the core of the project, you will need to know Typescript. If you are more of a wordsmith, don’t hesitate to join the Docs team!

You can also contribute without having a lot of time to dedicate. For example, you can help triage tickets, check the code, or proofread the documentation. If you are on Discord, you can also help resolve help requests. Even occasionally, this type of contribution is always welcome!

Don’t see yourself in any description? My list is not exhaustive, feel free to check if there is a place where you can contribute! And remember, you don’t need to commit full time, even occasional contributions are always welcome.

Before starting

If you are still hesitant, I invite you to read the Contribute to Astro page in the documentation. Next, be aware that each of these repositories contains a CONTRIBUTING.md file. I recommend you read it before you start.

Whether it’s for issues, RFCs or PRs, each repository has templates to fill out. These are not there to annoy you but to save time for people who will try to help you (whether to solve your problem, to reread your contribution, etc.). It’s therefore a win-win system.

Finally, don’t hesitate to join the Astro Discord server. Being there is useful for coordinating if needed, but it can also allow you to find help or ask for advice.

[Post] A new website

Tue, 07 Jan 2025 14:40:00 GMT

After about fifteen years of using my old domain name (armandphilippot.com for the record), I decided to start from scratch. It’s now time to present you the first version of armand.philippot.eu; welcome!

Introducing armand.philippot.eu

My technical choices

With this new website, I’m saying goodbye to Next.js and WordPress. I choose to build a static website, or almost. Thanks to Astro, I can have a static website with API routes to deal with some features like the contact form.

My contents are written with Markdown using the MDX format to extend my formatting options a bit with the help of Remark/Rehype plugins and custom components.

Speaking of components, the ones that required a bit of interactivity are build using Web components. With Astro, the template is easy to write : you just need to write an Astro component inside your custom tag. Then, all you need to do is to implement the interactivity with Javascript.

For the search feature, I’m using Pagefind which can build an index for static websites. In the future, I’d like it to be better integrated in my design but for now, as long as it serves its purpose it’s good enough!

Content types

I chose to divide my contents by type. Currently, you will get access to:

guides: a somewhat long format that includes step-by-step procedures to achieve a result,
notes: some raw contents (meaning unstructured, bordering on draft) for my personal usage before all,
bookmarks: some links I find interesting and I want to share or to save to find them again later,
a blogroll: some links to personal websites I like to read,
a blog (posts and dedicated categories): I’ll publish there contents that doesn’t seem to fit elsewhere,
some tags: you can retrieve the different content types on a same page filtered by topic.

This structure could evolve later if I choose to introduce new types of content.

Features

I haven’t added anything fancy. I want a simple content-driven website before all. So the features are the following:

a contact form,
a search field available next to the menu,
some settings allowing you to update:
- the language (English or French),
- the website theme (light or dark),
- the code blocks theme (light or dark) independently of the website theme.

This website is bilingual. However, the translation or the rewriting in English will not be necessarily available at the same time as the French version. Writing takes time, so translating/rewriting (without using an automatic translator) takes even more time. Another point that seems important to me: in the future, some content may be exclusive to a language… I will decide on a case-by-case basis if the opportunity arises.

What’s next?

Improving my development experience

Currently, I’m okay with my choice of technologies. However, I know I have some technical point to improve. I have some issues in development mode. Thankfully they are not blocking to build my website. So I’ll will first search how to improve that.

Automating the build process

I’m not using an host provider like Vercel or Netlify - that allowed to rebuild my website depending on my repository activity - but a VPS. So I’d like to implement something similar (but not necessarily as accomplished) instead of having to rebuild my website manually with each new content. I think that without automating this aspect, I risk getting bored and not posting as often as I would like.

Rethinking the blog posts organization

Blog posts are not meant to be updated (unless a typo or a broken link). So I think another organization could be helpful at least to organize myself.

If I’m doing that, I think I will add some archive pages! They could be helpful to easily find a blog post by date. This change also implies a change in the URL of the page. I’m still hesitating between a classification by year only (/blog/2025/new-website) or by year and by month (/blog/2025/01/new-website). I’ll think about it.

New features

I’d like to add a comment management system and to explore the idea of Webmentions. It’s not urgent, but this is an idea I want to keep in mind for later.

What’s next? Well, I think all I need to do is to add more contents to this website!

Posts category's feed

[Post] New year, new version

Mainly technical improvements

Simplified routing

Use of view transitions

Bug fixes

Graphical changes

Improved navigation sidebar

Refined dark theme

Minor layout changes

What’s next?

[Post] Contribute to the Astro's project

What is a contribution?

My journey as an Astro contributor

Issues opening

Followed by pull requests

Involved in Astro Docs

French translations

Reviewing the English documentation

Various documentation improvements

Participating to the “Talking & Doc’ing” event

A bit of technical support

Contributions leading to surprises

Let’s take stock

Want to join?

Astro project architecture

All kinds of skills can be useful

Before starting

[Post] A new website

Introducing armand.philippot.eu

My technical choices

Content types

Features

What’s next?

Improving my development experience

Automating the build process

Rethinking the blog posts organization

New features