[{"data":1,"prerenderedAt":900},["ShallowReactive",2],{"blog":3},[4,252,389,522,637,783],{"id":5,"title":6,"body":7,"description":234,"extension":235,"meta":236,"navigation":247,"path":248,"seo":249,"stem":250,"__hash__":251},"blog\u002Fblog\u002F04-04-2024-dev-blog-1-build-a-skyblock-plugin.md","Build a Skyblock Plugin (Part 1): Introduction",{"type":8,"value":9,"toc":224},"minimark",[10,15,20,24,27,31,39,70,75,79,82,96,100,107,127,142,145,156,166,177,181,184,212,216,219],[11,12,14],"h1",{"id":13},"dev-blog-1-build-a-minecraft-skyblock-plugin","Dev Blog #1: Build a Minecraft Skyblock Plugin",[16,17,19],"h2",{"id":18},"what-type-of-plugin-am-i-building","What type of plugin am I building?",[21,22,23],"p",{},"I'm building a Minecraft 1.20.4 Skyblock plugin. Skyblock is a popular game mode in Minecraft where players start on a\nsmall island in the sky and have to expand it by gathering resources, building structures, and completing challenges.\nThe goal is to create a thriving island and become the richest player on the server.",[21,25,26],{},"That's what everyone wants, but I prefer something a little bit more like Hypixel’s Skyblock—not too complex but with\ninteresting features and mechanics.",[16,28,30],{"id":29},"considerations-requirements","Considerations \u002F Requirements",[21,32,33,34,38],{},"This plugin is for ",[35,36,37],"strong",{},"Edmine Network",", a Minecraft server that I'm working on. Here are some considerations and\nrequirements for the plugin (some features are missing):",[40,41,42,46,49,52,55,58,61,64,67],"ul",{},[43,44,45],"li",{},"Players should be able to create and manage their own islands.",[43,47,48],{},"Islands should have a border that prevents players from falling off.",[43,50,51],{},"Players should be able to invite others to their islands.",[43,53,54],{},"Players should be able to visit other players' islands and interact with them.",[43,56,57],{},"Islands should have a shop where players can buy and sell items.",[43,59,60],{},"Players should be able to compete in challenges and earn rewards.",[43,62,63],{},"Implements dungeons, custom items, and custom mobs to enhance the experience.",[43,65,66],{},"Players should be able to level up their islands and unlock new features (size, generator, etc.).",[43,68,69],{},"Players should be able to edit island ranks permissions via a GUI.",[21,71,72],{},[35,73,74],{},"Also, I need a Skyblock that can be played by at least 50 players at the same time.",[16,76,78],{"id":77},"time-to-think-about-the-architecture","Time to think about the architecture",[21,80,81],{},"Before I start coding, I need to think about the architecture of the plugin. Here are some questions I need to answer (I\ndidn't put all the questions):",[40,83,84,87,90,93],{},[43,85,86],{},"How will a Minecraft server in 1.20.4 handle 50 players at the same time?",[43,88,89],{},"How will I store island data? In a database? In files?",[43,91,92],{},"If I have custom mobs and a lot of features, how will I handle performance?",[43,94,95],{},"How will I handle dungeons?",[16,97,99],{"id":98},"what-architecture-did-i-choose","What architecture did I choose?",[21,101,102,103,106],{},"I decided to use a ",[35,104,105],{},"cross-server architecture",". For example, if I have 50 players on the server, I will have:",[40,108,109,115,121],{},[43,110,111,114],{},[35,112,113],{},"1 server"," for the Skyblock spawn (only one because spawns are not that heavy).",[43,116,117,120],{},[35,118,119],{},"3 servers"," for the islands (because islands are resource-heavy).",[43,122,123,126],{},[35,124,125],{},"2 servers"," for dungeons (since combat may be heavy).",[21,128,129,130,133,134,137,138,141],{},"I also need ",[35,131,132],{},"an inventory sync system",". If a player moves from ",[35,135,136],{},"Island Server 1"," to ",[35,139,140],{},"Island Server 2",", their\ninventory should remain the same. This is a bit complex but doable.",[21,143,144],{},"For dungeons, I haven't made final decisions yet.",[21,146,147,148,151,152,155],{},"For storing island data, I will use a ",[35,149,150],{},"database"," to store worlds and other information. I plan to use an updated\nversion of ",[35,153,154],{},"SlimeWorldManager",", a plugin originally developed by Hypixel for 1.8 but maintained by the community for\nnewer versions.",[21,157,158,159],{},"🔗 ",[160,161,165],"a",{"href":162,"rel":163},"https:\u002F\u002Fwww.spigotmc.org\u002Fresources\u002Fadvanced-slimeworldmanager.87209\u002F",[164],"nofollow","Advanced SlimeWorldManager",[21,167,168,169,172,173,176],{},"For the database, I'll use ",[35,170,171],{},"MySQL"," for everything, along with a ",[35,174,175],{},"Redis"," server for caching. However, given Redis’\nrecent license changes, I might opt for an open-source fork.",[16,178,180],{"id":179},"what-about-performance","What about performance?",[21,182,183],{},"For performance optimization:",[40,185,186,193,200],{},[43,187,188,189,192],{},"I will ",[35,190,191],{},"cache"," islands, players, dungeons, mobs, and items.",[43,194,195,196,199],{},"I will rely on ",[35,197,198],{},"async tasks"," to handle heavy operations.",[43,201,202,203,206,207,211],{},"Every database\u002Fcache query will be ",[35,204,205],{},"async",", using ",[208,209,210],"code",{},"CompletableFuture"," and a callback system to ensure results are\nprocessed on the main thread.",[16,213,215],{"id":214},"the-end","The End",[21,217,218],{},"That's it for this blog post. I've started coding the plugin, and I'll post the next blog update when I have something\nsubstantial to show.",[21,220,221],{},[35,222,223],{},"Stay tuned!",{"title":225,"searchDepth":226,"depth":226,"links":227},"",2,[228,229,230,231,232,233],{"id":18,"depth":226,"text":19},{"id":29,"depth":226,"text":30},{"id":77,"depth":226,"text":78},{"id":98,"depth":226,"text":99},{"id":179,"depth":226,"text":180},{"id":214,"depth":226,"text":215},"This article outlines the development of a Minecraft Skyblock plugin for Spigot servers, starting with project goals and context.","md",{"image":237,"date":238,"tags":239,"author":244},"https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Fblog\u002F04-04-2024-dev-blog-1-build-a-skyblock-plugin.jpeg","2024-04-04T21:00:00.000Z",[240,241,242,243],"Minecraft","Spigot","Plugin Development","Skyblock",{"name":245,"picture":246},"Farmeurimmo","https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Flogo.png",true,"\u002Fblog\u002F04-04-2024-dev-blog-1-build-a-skyblock-plugin",{"title":6,"description":234},"blog\u002F04-04-2024-dev-blog-1-build-a-skyblock-plugin","hvycAB7SJTFJ1d_YozNl3hSOPU09kPvyNQSaWu9RZrA",{"id":253,"title":254,"body":255,"description":379,"extension":235,"meta":380,"navigation":247,"path":385,"seo":386,"stem":387,"__hash__":388},"blog\u002Fblog\u002F15-04-2024-dev-blog-2-build-a-skyblock-plugin.md","Build a Skyblock Plugin (part 2): Island System",{"type":8,"value":256,"toc":372},[257,261,268,270,276,284,288,294,297,303,306,315,319,328,331,334,338,341,344,347,350,353,359,362,366,369],[11,258,260],{"id":259},"dev-blog-2-build-a-skyblock-plugin-island-system","Dev Blog #2: Build a Skyblock Plugin: Island System",[21,262,263,264,267],{},"In the last article, we have created the basic structure of our plugin.",[265,266],"br",{},"\nIn this article, we will create the island system that is the core of the Skyblock plugin.",[16,269,30],{"id":29},[21,271,272,273,275],{},"For the cross-server support, I choose to use a cache system. I will use Redis for now with the Jedis client.",[265,274],{},"\nThe cache system will permit reducing the number of requests to the database, share data between servers, improve the\nperformance of the plugin, and allow using a message broker like Redis Pub\u002FSub for cross-server communication.",[21,277,278,279,283],{},"Also, I will use ",[160,280,282],{"href":162,"rel":281},[164],"Advanced Slimeworldmanager"," for\nworld management. This plugin will allow creating, managing, and storing islands in the MySQL database.",[16,285,287],{"id":286},"island-world-system","Island World System",[21,289,290,291,293],{},"Thanks to Advanced Slimeworldmanager, we can easily set up the island system.",[265,292],{},"\nWe just need to create a generic island world, save it in the database as read-only, and then clone it when a player\ncreates an island.",[21,295,296],{},"With this approach, we can have multiple types of islands, such as desert or jungle islands, without struggling with\nFAWE (FastAsyncWorldEdit) or the WorldEdit API, which is not very easy to use. I have already created a Skyblock plugin\nwith this method and got accustomed to it.",[21,298,299,300,302],{},"Another benefit of ASWM (Advanced Slimeworldmanager) is that we can store our worlds in the database. This is very\nuseful for cross-server support.",[265,301],{},"\nWith its API, we can easily load, clone, save, and unload worlds like a normal world but much faster since it was\ndesigned for small worlds.",[21,304,305],{},"I decided to name my worlds \"islands_\" followed by the UUID of the island. A clear name that is unique and easy to find\nin the database.",[21,307,308,309,311,312,314],{},"The downside of ASWM is that it doesn't allow storing huge worlds like a survival world by default, as it wasn't\ndesigned for that.",[265,310],{},"\nHowever, for small worlds like islands, it's perfect. Also, MySQL servers by default don't allow storing huge blobs (\n16MB by default), but we can change that in the configuration.",[265,313],{},"\nFor example, an island world with dimensions 250x250x320 has little chance of exceeding 16MB (though it's possible).",[16,316,318],{"id":317},"island-cross-server-system","Island Cross Server System",[21,320,321,322,324,325,327],{},"First, each island server sends a Pub\u002FSub message every 3 to 5 seconds. This allows the plugin to monitor the server\nload.",[265,323],{},"\nThen, on all servers, the plugin receives the message and stores it locally. The plugin will choose the server with the\nlowest load to create the island.",[265,326],{},"\nThis approach allows distributing the load of islands across all servers and easily adding or removing servers.",[21,329,330],{},"Once a server is selected, it will send a Pub\u002FSub message to the chosen server to create or load the island. When\nloaded, the remote server sends a confirmation message to the selected server, indicating the island is loaded, and the\nplayer can join.",[21,332,333],{},"The next step is to implement a similar system for teleportation. We send the player to another server, and at the same\ntime, we send a Pub\u002FSub message to the server to teleport the player to the island or elsewhere.",[16,335,337],{"id":336},"island-functionalities","Island Functionalities",[21,339,340],{},"As you may know, you can invite, kick, ban, expel, promote, demote, etc., players on your island in any Skyblock plugin.",[21,342,343],{},"I implemented all these functionalities in my plugin. BUT, there's a small constraint: the player must be on the server\nwhere the island is loaded to perform these actions (other servers have read-only data). This is to prevent data\nconflicts.",[21,345,346],{},"I could have implemented it cross-server, but it would require a very large Pub\u002FSub system, making it very complex. I\nopted to keep it simple and efficient.",[21,348,349],{},"So, when on the server where the island is loaded, you can perform all actions on your island. Then, a Pub\u002FSub message\ntells the other servers to update the island data (which is read-only).",[21,351,352],{},"For example, if you change a player's rank, the other servers will know about it in under 3 seconds.",[21,354,355,356,358],{},"This leads to the issue of cooldowns. Imagine if players spam commands to change the rank of a player.",[265,357],{},"\nTo address this, I implemented a cooldown system and a queue system. For example, if a player changes another player's\nrank, the plugin will wait a bit before sending the Pub\u002FSub message to allow for other changes. But critical changes (\nlike money, kick) are sent immediately, overriding whatever is in the queue.",[21,360,361],{},"With cross-server systems, we can encounter many problems like this, so we need to be very careful. You can easily make\nmistakes without realizing it.",[16,363,365],{"id":364},"conclusion","Conclusion",[21,367,368],{},"I’ve discussed the main concepts of the island system. I won’t go into the code details here because for complex systems\nlike this, it’s better to first understand the overall structure before diving into the code. If you’re interested in\nthe code, I can write a more detailed article about it—just reach out to me via Discord (Farmeurimmo), contact form, or\nemail.",[21,370,371],{},"Next time, I’ll cover the Inventory Sync System for cross-server support.",{"title":225,"searchDepth":226,"depth":226,"links":373},[374,375,376,377,378],{"id":29,"depth":226,"text":30},{"id":286,"depth":226,"text":287},{"id":317,"depth":226,"text":318},{"id":336,"depth":226,"text":337},{"id":364,"depth":226,"text":365},"This article delves into the Skyblock plugin's island system, focusing on cross-server compatibility, island distribution, and data management.",{"image":381,"date":382,"tags":383,"author":384},"https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Fblog\u002F15-04-2024-dev-blog-2-build-a-skyblock-plugin.jpeg","2024-04-15T11:28:00.000Z",[240,241,242,243],{"name":245,"picture":246},"\u002Fblog\u002F15-04-2024-dev-blog-2-build-a-skyblock-plugin",{"title":254,"description":379},"blog\u002F15-04-2024-dev-blog-2-build-a-skyblock-plugin","7v1COuY7d1CqPqap5I25FbDlOYMvc4wYWX_N861nlX0",{"id":390,"title":391,"body":392,"description":512,"extension":235,"meta":513,"navigation":247,"path":518,"seo":519,"stem":520,"__hash__":521},"blog\u002Fblog\u002F18-07-2024-dev-blog-3-build-a-skyblock-plugin.md","Build a Skyblock Plugin (part 3): Inventory Sync System",{"type":8,"value":393,"toc":505},[394,398,401,403,420,424,427,430,433,436,441,449,454,465,469,472,475,478,481,484,488,491,494,497,499,502],[11,395,397],{"id":396},"dev-blog-3-build-a-skyblock-plugin-part-3-inventory-sync-system","Dev Blog #3: Build a Skyblock Plugin (part 3): Inventory Sync System",[21,399,400],{},"In the last article, we talked about the island system. In this article, we will create the inventory sync system that\nwill permit to synchronize the inventory of the player between the servers.",[16,402,30],{"id":29},[40,404,405,408,411,414,417],{},[43,406,407],{},"Should be fast, resilient and reliable",[43,409,410],{},"Optimized for performance",[43,412,413],{},"Should be able to handle a large number of players",[43,415,416],{},"Should be compatible with ItemAdder items",[43,418,419],{},"The inventories should be stored on mysql for persistent storage and on redis for caching",[16,421,423],{"id":422},"inventory-sync-system","Inventory Sync System",[21,425,426],{},"There are many ways to synchronize the inventory of the player between the servers. The most common way is to use a\nclass utility that will handle the convert the item into json and store it in the database.",[21,428,429],{},"I could also use the ItemStack.serialize() method that will convert the item into a json map and store it in the\ndatabase.",[21,431,432],{},"All of that is not compatible with item adder items. Item adder items are items that have a custom model data and a\ncustom texture. They have a special thing inside that can't be serialized easily.",[21,434,435],{},"So I decided to go for a Base64 serialization. This will permit to store the item in a string format that can be\nconverted back to an item. This is compatible with item adder items.",[21,437,438],{},[35,439,440],{},"Disadvantages:",[40,442,443,446],{},[43,444,445],{},"Generate huge strings",[43,447,448],{},"Not human readable",[21,450,451],{},[35,452,453],{},"Advantages:",[40,455,456,459,462],{},[43,457,458],{},"Compatible with item adder items",[43,460,461],{},"Fast to serialize and deserialize",[43,463,464],{},"No need to make a utility class with 500 if or getOrDefault",[16,466,468],{"id":467},"performance","Performance",[21,470,471],{},"To improve the performance, I will use a cache system: Redis for now with Jedis client.",[21,473,474],{},"When a player joins the server, the plugin will check if the player has an inventory in the cache. If not, it will\nload the inventory from the database and store it in the cache.",[21,476,477],{},"On join, the thing that takes the most time is going back to the main server thread to ensure thread safety.\nI tried full async, it was working but unsure about the thread safety. Nothing on the documentation about that.",[21,479,480],{},"Just in case, I go back to the main thread to apply inventory changes.\nThis causes between 10ms to 100ms of delay before the inventory is loaded.",[21,482,483],{},"How fast can it load an inventory? I did with a full inventory of random items and it took between 15ms to 50ms.\nThis is acceptable for me. I don't want to go below 10ms because it's not necessary and would lead to more complex\ncode.",[16,485,487],{"id":486},"experience-health-food-and-more","Experience, health, food and more",[21,489,490],{},"I decided to store everything in a json for the cache and in a table for the database.",[21,492,493],{},"To get experience (total experience the player has), I will use the calculateTotalExperiencePoints() method.\nFor the health and food, I will use the getHealth(), getFoodLevel(), getSaturation() methods.",[21,495,496],{},"I also have some custom stats that could be added in the future like current mana left, etc.",[16,498,365],{"id":364},[21,500,501],{},"We talked about the inventory sync system.\nIf you're interested in the code, I can make a more detailed article about it, just send me a\nmessage on discord (Farmeurimmo), via the contact form or by email.",[21,503,504],{},"Next time, I will talk about the Cross Server auction system.",{"title":225,"searchDepth":226,"depth":226,"links":506},[507,508,509,510,511],{"id":29,"depth":226,"text":30},{"id":422,"depth":226,"text":423},{"id":467,"depth":226,"text":468},{"id":486,"depth":226,"text":487},{"id":364,"depth":226,"text":365},"This article explores the Skyblock plugin's inventory synchronization system, detailing how player inventories are managed across servers.",{"image":514,"date":515,"tags":516,"author":517},"https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Fblog\u002F18-07-2024-dev-blog-3-build-a-skyblock-plugin.jpeg","2024-07-18T11:00:00.000Z",[240,241,242,243],{"name":245,"picture":246},"\u002Fblog\u002F18-07-2024-dev-blog-3-build-a-skyblock-plugin",{"title":391,"description":512},"blog\u002F18-07-2024-dev-blog-3-build-a-skyblock-plugin","1b4fO6ezVpGfGszdmsZNrYEvxLup5-oBX2OI4PLPUEY",{"id":523,"title":524,"body":525,"description":627,"extension":235,"meta":628,"navigation":247,"path":633,"seo":634,"stem":635,"__hash__":636},"blog\u002Fblog\u002F27-08-2024-dev-blog-4-build-a-skyblock-plugin.md","Build a Skyblock Plugin (part 4): Cross server auctions",{"type":8,"value":526,"toc":617},[527,531,534,536,549,553,556,559,562,567,570,573,580,583,586,590,593,596,599,603,606,608,611,614],[11,528,530],{"id":529},"dev-blog-4-build-a-skyblock-plugin-part-4-cross-server-auctions","Dev Blog #4: Build a Skyblock Plugin (part 4): Cross server auctions",[21,532,533],{},"In the last article, we talked about the inventory synchronization between the servers.\nIn this article, we will talk about the cross server auctions.",[16,535,30],{"id":29},[40,537,538,541,544,546],{},[43,539,540],{},"Once an item is sold, if you try to buy 2ms after it, you won't be able to",[43,542,543],{},"Transactional system",[43,545,416],{},[43,547,548],{},"Present on all servers",[16,550,552],{"id":551},"cross-server-auctions","Cross server auctions",[21,554,555],{},"I already done an auction system in the past. So I knew how to make the inventory system fast and reliable.\nThe only challenge was to handle the cross server part.",[21,557,558],{},"What happens if a player tries to buy an item on server 1 and the item is on server 2?\nWhat happens if a player buy an item on server 1 and another one on server 2 while the seller is removing the item?",[21,560,561],{},"For storage, I used Redis for caching and MySQL for persistent storage. I reused my class of the Inventory Sync System\nto store the items in the database.",[563,564,566],"h3",{"id":565},"the-solution","The solution",[21,568,569],{},"As always, my solution is to use a pubs\u002Fsubs system with Redis.",[21,571,572],{},"When a player puts an item on the auction house, the plugin will send a message to the Redis channel to notify all the\nservers that an item has been put on the auction house.\nWhen a player buys an item, the plugin will send a message to the Redis channel with the current timestamp and the\nitem id.",[21,574,575,576,579],{},"With my transactional system, I can ensure that the item is not bought twice because the timestamp is unique and if\nthe timestamp of another attempt is lower than the current one, the transaction will be canceled for the highest\ntimestamp.\nThe player with the lower timestamp always wins ",[577,578],"d",{},".",[21,581,582],{},"Plus there is a small delay to let the transaction be processed.",[21,584,585],{},"Then we just have to notify all the servers that the item has been bought and remove it from the auction house.",[563,587,589],{"id":588},"i-know-i-didnt-talk-about-player-money","I know I didn't talk about player money..",[21,591,592],{},"Users are not always loaded on the server so it is a little bit more complex than the auction system itself.",[21,594,595],{},"If the player is on the server when the transaction happens, no problems, but if the player is on another server,\nwe need to send a pubsub to that server to modify the money of the player.",[21,597,598],{},"If offline, we need to load the user from the database, modify the money and save it back.",[16,600,602],{"id":601},"speed","Speed ?",[21,604,605],{},"Of course, there is some delay between the click and the item appearing in the inventory.\nBut in under 5s you can have the item in your inventory.",[16,607,365],{"id":364},[21,609,610],{},"Nothing too complicated, when I first thought about it, I was like \"It is going to be tough, but it is doable\".\nBut in the end, it was pretty easy to do.",[21,612,613],{},"If you're interested in the code, I can make a more detailed article about it, just send me a message on discord (\nFarmeurimmo), via the contact form or by email.",[21,615,616],{},"Next time, I will maybe talk about cross server teleportation with coordinates and fast server switching.\n(For example, you want to go to the pvp warp or you got tpa to another server)",{"title":225,"searchDepth":226,"depth":226,"links":618},[619,620,625,626],{"id":29,"depth":226,"text":30},{"id":551,"depth":226,"text":552,"children":621},[622,624],{"id":565,"depth":623,"text":566},3,{"id":588,"depth":623,"text":589},{"id":601,"depth":226,"text":602},{"id":364,"depth":226,"text":365},"This article explores the Skyblock plugin's auction system, detailing how players can sell and buy items across servers.",{"image":629,"date":630,"tags":631,"author":632},"https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Fblog\u002F27-08-2024-dev-blog-4-build-a-skyblock-plugin.jpeg","2024-08-27T11:00:00.000Z",[240,241,242,243],{"name":245,"picture":246},"\u002Fblog\u002F27-08-2024-dev-blog-4-build-a-skyblock-plugin",{"title":524,"description":627},"blog\u002F27-08-2024-dev-blog-4-build-a-skyblock-plugin","oHG1GJigxY3kHz2OAvorXH2N_mD2veSJtI8qIt7Cb5c",{"id":638,"title":639,"body":640,"description":769,"extension":235,"meta":770,"navigation":247,"path":779,"seo":780,"stem":781,"__hash__":782},"blog\u002Fblog\u002F28-03-2024-new-website-portfolio-v4-edition.md","New website with portfolio in its 4th version",{"type":8,"value":641,"toc":753},[642,646,650,657,661,665,668,672,675,679,682,686,689,693,700,704,711,715,718,722,725,729,736,740,743,747],[11,643,645],{"id":644},"my-new-website-portfolio-v4-edition","My new website \u002F portfolio V4 edition",[16,647,649],{"id":648},"motivations","Motivations",[21,651,652,653,656],{},"I always wanted to have a portfolio to showcase my skills and share my thoughts and ideas with the world. ",[35,654,655],{},"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.",[16,658,660],{"id":659},"tech-choices","Tech Choices",[563,662,664],{"id":663},"svelte-kit","Svelte + Kit",[21,666,667],{},"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.",[563,669,671],{"id":670},"vite-fun-story","Vite + Fun story",[21,673,674],{},"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.",[563,676,678],{"id":677},"tailwindcss","TailwindCSS",[21,680,681],{},"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.",[563,683,685],{"id":684},"shouldve-taken-some-ui-libraries","Should've taken some UI libraries?",[21,687,688],{},"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.",[16,690,692],{"id":691},"multi-language-support","Multi-language support",[21,694,695,696,699],{},"I wanted my portfolio to be multi-language because not everyone can talk English well. For my blog, I ",[35,697,698],{},"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.",[16,701,703],{"id":702},"all-in-one-page","All in one page",[21,705,706,707,710],{},"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. ",[35,708,709],{},"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.",[16,712,714],{"id":713},"the-particle-background","The particle background",[21,716,717],{},"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.",[16,719,721],{"id":720},"the-contact-form","The contact form",[21,723,724],{},"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.",[16,726,728],{"id":727},"the-blog","The blog",[21,730,731,732,735],{},"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. ",[35,733,734],{},"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.",[16,737,739],{"id":738},"seo","SEO",[21,741,742],{},"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.",[16,744,746],{"id":745},"conclusion-of-the-v4","Conclusion of the V4",[21,748,749,752],{},[35,750,751],{},"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":225,"searchDepth":226,"depth":226,"links":754},[755,756,762,763,764,765,766,767,768],{"id":648,"depth":226,"text":649},{"id":659,"depth":226,"text":660,"children":757},[758,759,760,761],{"id":663,"depth":623,"text":664},{"id":670,"depth":623,"text":671},{"id":677,"depth":623,"text":678},{"id":684,"depth":623,"text":685},{"id":691,"depth":226,"text":692},{"id":702,"depth":226,"text":703},{"id":713,"depth":226,"text":714},{"id":720,"depth":226,"text":721},{"id":727,"depth":226,"text":728},{"id":738,"depth":226,"text":739},{"id":745,"depth":226,"text":746},"This article explores the motivations, tech stack (Svelte, Vite, Tailwind CSS), and features (contact form, blog, multilingual) of my fourth website.",{"image":771,"date":772,"tags":773,"author":778},"https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Fblog\u002F28-03-2024-new-website-portfolio-v4-edition.jpeg","2024-03-28T21:00:00.000Z",[774,775,776,777,678],"Website","Portfolio","Svelte","Vite",{"name":245,"picture":246},"\u002Fblog\u002F28-03-2024-new-website-portfolio-v4-edition",{"title":639,"description":769},"blog\u002F28-03-2024-new-website-portfolio-v4-edition","8bzkwVYm5HwRUffTC6Gyarye48S_CXQjkNBEAPLHcWg",{"id":784,"title":785,"body":786,"description":887,"extension":235,"meta":888,"navigation":247,"path":896,"seo":897,"stem":898,"__hash__":899},"blog\u002Fblog\u002F30-03-2025-new-website-v5.md","V5 of my portfolio",{"type":8,"value":787,"toc":881},[788,792,795,798,802,805,808,811,815,829,833,870,872,875,878],[11,789,791],{"id":790},"v5-of-my-portfolio","V5 of My Portfolio",[21,793,794],{},"Long time no see! I haven't posted anything since the last article about the Skyblock plugin.",[21,796,797],{},"The reason: I've been too busy with my studies and projects. However, I plan to slowly get back to my blog and post more\narticles about my work.",[16,799,801],{"id":800},"new-website","New Website",[21,803,804],{},"Once again, I’ve redesigned my website, almost exactly one year after the previous version. I wanted to improve my\nportfolio by using my new skills in web development and to make it more user-friendly.",[21,806,807],{},"I’ve kept the blog articles and projects from the last version, but with a new design and added features.",[21,809,810],{},"The view count is currently not implemented in the new version because I’m unsure if I’ll keep it or not.",[16,812,814],{"id":813},"tech-stack","Tech Stack",[40,816,817,820,823,826],{},[43,818,819],{},"Next.js 15",[43,821,822],{},"React 19",[43,824,825],{},"Tailwind CSS 4",[43,827,828],{},"DaisyUI 5",[16,830,832],{"id":831},"features","Features",[40,834,835,846,849,852,855,858,861,864,867],{},[43,836,837,838,841,842,845],{},"Multilingual (French and English for now) with i18n and path-based routing (",[208,839,840],{},"\u002Fen"," and ",[208,843,844],{},"\u002Ffr",")",[43,847,848],{},"Contact form",[43,850,851],{},"Blog (in markdown, no more weird API fetches with XSS risks)",[43,853,854],{},"Projects",[43,856,857],{},"Dark mode + light mode",[43,859,860],{},"Responsive design",[43,862,863],{},"Legal mentions",[43,865,866],{},"Dynamic sitemap (updated every time I add a new page)",[43,868,869],{},"Pre generated pages (for SEO)",[16,871,365],{"id":364},[21,873,874],{},"I hope you like the new design and features. I’ll try to post more articles about my projects and studies. If you have\nany questions or suggestions, feel free to contact me via the contact form or on my social media.",[21,876,877],{},"I’ll try to answer as soon as possible.",[21,879,880],{},"Thanks for reading!",{"title":225,"searchDepth":226,"depth":226,"links":882},[883,884,885,886],{"id":800,"depth":226,"text":801},{"id":813,"depth":226,"text":814},{"id":831,"depth":226,"text":832},{"id":364,"depth":226,"text":365},"This article explores the tech stack (NextJS, React, Tailwind 4, DaisyUI 5), and features (contact form, blog, multilingual).",{"image":889,"date":890,"tags":891,"author":895},"https:\u002F\u002Fcdn.farmeurimmo.fr\u002Fimg\u002Fblog\u002F30-03-2025-new-website-v5.jpg","2025-03-30T20:00:00.000Z",[774,775,892,893,894,678],"React","NextJS","DaisyUI",{"name":245,"picture":246},"\u002Fblog\u002F30-03-2025-new-website-v5",{"title":785,"description":887},"blog\u002F30-03-2025-new-website-v5","VVWdUKE4qzeULkfNluorDNHlmPXCzOGajcXsElawaBo",1794558957798]