[{"data":1,"prerenderedAt":162},["ShallowReactive",2],{"project--28-03-2024-new-website-portfolio-v4-edition":3},{"id":4,"title":5,"body":6,"description":144,"extension":145,"meta":146,"navigation":157,"path":158,"seo":159,"stem":160,"__hash__":161},"blog\u002Fblog\u002F28-03-2024-new-website-portfolio-v4-edition.md","New website with portfolio in its 4th version",{"type":7,"value":8,"toc":125},"minimark",[9,14,19,28,32,37,40,44,47,51,54,58,61,65,72,76,83,87,90,94,97,101,108,112,115,119],[10,11,13],"h1",{"id":12},"my-new-website-portfolio-v4-edition","My new website \u002F portfolio V4 edition",[15,16,18],"h2",{"id":17},"motivations","Motivations",[20,21,22,23,27],"p",{},"I always wanted to have a portfolio to showcase my skills and share my thoughts and ideas with the world. ",[24,25,26],"strong",{},"However, I\nfelt limited by my old blog's design and content management system."," Markdown files offered some flexibility, but I\ndesired the ability to use HTML, TailwindCSS, and even JavaScript within my articles.",[15,29,31],{"id":30},"tech-choices","Tech Choices",[33,34,36],"h3",{"id":35},"svelte-kit","Svelte + Kit",[20,38,39],{},"Choosing the tech stack for this new project presented a challenge. I wanted the benefits of both SSR (Server-Side\nRendering) and SSG (Static Site Generation). After evaluating React and Svelte, I opted for Svelte due to its intuitive\nand natural feel.",[33,41,43],{"id":42},"vite-fun-story","Vite + Fun story",[20,45,46],{},"Vite significantly enhances the development experience with its blazing-fast development server and hot module\nreplacement (HMR). While it offers these advantages, there's a potential downside: SSR errors like sending duplicate\nrequests. I encountered this during blog post view development, where the view count inexplicably inflated. The culprit?\nVite sending both the old and new requests! It's a minor inconvenience, but manageable.",[33,48,50],{"id":49},"tailwindcss","TailwindCSS",[20,52,53],{},"TailwindCSS was my pick for rapid and effortless blog design. As a non-designer, I craved a solution that minimized CSS\ncoding. TailwindCSS perfectly fit the bill, offering an additional perk: removal of unused CSS classes in production,\nleading to improved website performance.",[33,55,57],{"id":56},"shouldve-taken-some-ui-libraries","Should've taken some UI libraries?",[20,59,60],{},"The decision to use UI libraries involved a trade-off between personalization and efficiency. While libraries could have\nsaved time, I opted for a more personal touch by building the design myself. This was also a valuable opportunity to\nhone my design skills. However, for those less comfortable with TailwindCSS, exploring UI libraries is a worthwhile\nrecommendation, especially for elements outside of Tailwind's core offerings.",[15,62,64],{"id":63},"multi-language-support","Multi-language support",[20,66,67,68,71],{},"I wanted my portfolio to be multi-language because not everyone can talk English well. For my blog, I ",[24,69,70],{},"assumed"," that\nthe reader would be more knowledgeable in English. Also, technically speaking, I didn't want to have to duplicate the\ncontent for each language. I wanted to have a single source of truth for the content. Plus, it takes less space in the\ndatabase and it is easier to maintain.",[15,73,75],{"id":74},"all-in-one-page","All in one page",[20,77,78,79,82],{},"When you are making a portfolio, you need to take into account that the person looking at your portfolio will not spend\na lot of time on it. You need to make it easy for the person to see your skills and your projects. ",[24,80,81],{},"I wanted to have\neverything on one page."," I wanted to have quick access to my skills, my projects, and my blog. People are lazy (me\nincluded) and they don't want to click on a lot of links to see your work. Unlike my old portfolio + blog, I wanted to\nhave a single page where you can see everything interesting about me.",[15,84,86],{"id":85},"the-particle-background","The particle background",[20,88,89],{},"As a developer, I'm always looking for what other creative people do but never think about doing something creative\nmyself. I wanted to have a cool background for my portfolio. Something dynamic and not static. On codepen, I found out\nsome cool particle backgrounds but those were not to my liking. So I decided to make my own. I don't regret it, it took\ntime but it was worth it. If you didn't notice, when you click on the page, the particles are changing direction. It's\nnot a bug, it's a feature HaHa. (It was used during the development to see if the particles were moving correctly but I\nliked it so I kept it). Also, sometimes particles are changing randomly direction.",[15,91,93],{"id":92},"the-contact-form","The contact form",[20,95,96],{},"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\nthird-party service like Formspree or Netlify forms. For now, I'm not using bot protection, but I will add one in the\nfuture or maybe some bot detection with an invisible form field to know if it's a bot or not. I'm still thinking about\nit.",[15,98,100],{"id":99},"the-blog","The blog",[20,102,103,104,107],{},"Unlike my old one, the content you see depends on my API and not the last commit on GitHub. Imagine adding a new\nMarkdownX (.mdx) file that increases the build time of your website. Plus, if you made a mistake in the Markdown file,\nyou have to commit again to fix it. I wanted a better way to manage my blog content. ",[24,105,106],{},"I wanted to have a way to edit my\narticles without having to commit and push to GitHub (better for ecology lmfaoo)."," Now I can just edit the JSON\ncontaining the HTML article and it will be updated on the website.",[15,109,111],{"id":110},"seo","SEO",[20,113,114],{},"Good SEO is important for a portfolio. You want to be found by recruiters and other people. I will try to improve it as\nmuch as I can because the more visible you are, the more chance you have of being contacted.",[15,116,118],{"id":117},"conclusion-of-the-v4","Conclusion of the V4",[20,120,121,124],{},[24,122,123],{},"I'm happy with the result of my portfolio."," I wanted something personal, fast, visible, reliable, and easy to\nmaintain. I think I achieved that with the design and the performance of the website. I hope you like it too. If you\nhave any feedback, feel free to contact me.",{"title":126,"searchDepth":127,"depth":127,"links":128},"",2,[129,130,137,138,139,140,141,142,143],{"id":17,"depth":127,"text":18},{"id":30,"depth":127,"text":31,"children":131},[132,134,135,136],{"id":35,"depth":133,"text":36},3,{"id":42,"depth":133,"text":43},{"id":49,"depth":133,"text":50},{"id":56,"depth":133,"text":57},{"id":63,"depth":127,"text":64},{"id":74,"depth":127,"text":75},{"id":85,"depth":127,"text":86},{"id":92,"depth":127,"text":93},{"id":99,"depth":127,"text":100},{"id":110,"depth":127,"text":111},{"id":117,"depth":127,"text":118},"This article explores the motivations, tech stack (Svelte, Vite, Tailwind CSS), and features (contact form, blog, multilingual) of my fourth website.","md",{"image":147,"date":148,"tags":149,"author":154},"https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Fblog\u002F28-03-2024-new-website-portfolio-v4-edition.jpeg","2024-03-28T21:00:00.000Z",[150,151,152,153,50],"Website","Portfolio","Svelte","Vite",{"name":155,"picture":156},"Farmeurimmo","https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Flogo.png",true,"\u002Fblog\u002F28-03-2024-new-website-portfolio-v4-edition",{"title":5,"description":144},"blog\u002F28-03-2024-new-website-portfolio-v4-edition","8bzkwVYm5HwRUffTC6Gyarye48S_CXQjkNBEAPLHcWg",1794558958121]