---
title: "New website with portfolio in its 4th version"
description: "This article explores the motivations, tech stack (Svelte, Vite, Tailwind CSS), and features (contact form, blog, multilingual) of my fourth website."
canonical_url: "https://farmeurimmo.fr/blog/28-03-2024-new-website-portfolio-v4-edition"
---

> Index of every page on this site: [llms.txt](https://farmeurimmo.fr/llms.txt)

# My new website / portfolio V4 edition

## Motivations

I always wanted to have a portfolio to showcase my skills and share my thoughts and ideas with the world. **However, I
felt limited by my old blog's design and content management system.** Markdown files offered some flexibility, but I
desired the ability to use HTML, TailwindCSS, and even JavaScript within my articles.

## Tech Choices

### Svelte + Kit

Choosing the tech stack for this new project presented a challenge. I wanted the benefits of both SSR (Server-Side
Rendering) and SSG (Static Site Generation). After evaluating React and Svelte, I opted for Svelte due to its intuitive
and natural feel.

### Vite + Fun story

Vite significantly enhances the development experience with its blazing-fast development server and hot module
replacement (HMR). While it offers these advantages, there's a potential downside: SSR errors like sending duplicate
requests. I encountered this during blog post view development, where the view count inexplicably inflated. The culprit?
Vite sending both the old and new requests! It's a minor inconvenience, but manageable.

### TailwindCSS

TailwindCSS was my pick for rapid and effortless blog design. As a non-designer, I craved a solution that minimized CSS
coding. TailwindCSS perfectly fit the bill, offering an additional perk: removal of unused CSS classes in production,
leading to improved website performance.

### Should've taken some UI libraries?

The decision to use UI libraries involved a trade-off between personalization and efficiency. While libraries could have
saved time, I opted for a more personal touch by building the design myself. This was also a valuable opportunity to
hone my design skills. However, for those less comfortable with TailwindCSS, exploring UI libraries is a worthwhile
recommendation, especially for elements outside of Tailwind's core offerings.

## Multi-language support

I wanted my portfolio to be multi-language because not everyone can talk English well. For my blog, I **assumed** that
the reader would be more knowledgeable in English. Also, technically speaking, I didn't want to have to duplicate the
content for each language. I wanted to have a single source of truth for the content. Plus, it takes less space in the
database and it is easier to maintain.

## All in one page

When you are making a portfolio, you need to take into account that the person looking at your portfolio will not spend
a lot of time on it. You need to make it easy for the person to see your skills and your projects. **I wanted to have
everything on one page.** I wanted to have quick access to my skills, my projects, and my blog. People are lazy (me
included) and they don't want to click on a lot of links to see your work. Unlike my old portfolio + blog, I wanted to
have a single page where you can see everything interesting about me.

## The particle background

As a developer, I'm always looking for what other creative people do but never think about doing something creative
myself. I wanted to have a cool background for my portfolio. Something dynamic and not static. On codepen, I found out
some cool particle backgrounds but those were not to my liking. So I decided to make my own. I don't regret it, it took
time but it was worth it. If you didn't notice, when you click on the page, the particles are changing direction. It's
not a bug, it's a feature HaHa. (It was used during the development to see if the particles were moving correctly but I
liked it so I kept it). Also, sometimes particles are changing randomly direction.

## The contact form

When working on my portfolio, I was thinking of a fast, simple, and secure way to contact me. I didn't want to use a
third-party service like Formspree or Netlify forms. For now, I'm not using bot protection, but I will add one in the
future or maybe some bot detection with an invisible form field to know if it's a bot or not. I'm still thinking about
it.

## The blog

Unlike my old one, the content you see depends on my API and not the last commit on GitHub. Imagine adding a new
MarkdownX (.mdx) file that increases the build time of your website. Plus, if you made a mistake in the Markdown file,
you have to commit again to fix it. I wanted a better way to manage my blog content. **I wanted to have a way to edit my
articles without having to commit and push to GitHub (better for ecology lmfaoo).** Now I can just edit the JSON
containing the HTML article and it will be updated on the website.

## SEO

Good SEO is important for a portfolio. You want to be found by recruiters and other people. I will try to improve it as
much as I can because the more visible you are, the more chance you have of being contacted.

## Conclusion of the V4

**I'm happy with the result of my portfolio.** I wanted something personal, fast, visible, reliable, and easy to
maintain. I think I achieved that with the design and the performance of the website. I hope you like it too. If you
have any feedback, feel free to contact me.

## Sitemap

See the full [sitemap](https://farmeurimmo.fr/sitemap.md) for all pages.
