You may have noticed that FosseryWeb development became extremely slow in the past few months, and you have to wait ages until I add the features, content you requested. Well, I feel like the codebase overgrew me, the site becomes harder and harder to maintain, as it becomes bigger and bigger. Producing cheatsheets and articles makes it grow pretty rapidly. Producing much of these content isn't really viable in the long run for a static site like FosseryWeb (Min), because if I want to change the code structure, I have to go over each page's HTML file one-by-one (although I could use client-side JS to eliminate some of the duplicate code, but it still wouldn't fully solve the issue because I can't store the full HTML code in JS, and it would also ruin the experience for many of you, who block JS in your browser). The ideal solution would be a dynamic web app, which I already experimented with earlier (see my Java/Spring endeavor: https://social.linux.pizza/@fosserytech/114422738214988335), but it's literally impossible to find a FOSS hosting service with a reasonable Privacy Policy for dynamic sites (unfortunately Codeberg Pages is only for static sites), and I don't have my own server to host a site.
I also promised to release a contribution guide, to make the project a collaborative effort, to speed up development a bit, allow anyone to write articles, produce cheatsheets. I'm already half done with the guide, including most of the rules to follow, but in the past weeks, I thought about it a lot, whether I'll be able to keep up with reviewing all the cheatsheet, article submissions, and the more I think about it, the more I realize that I want a bit too much. I barely have enough free time. I only have about 1-2 hours a day to do anything outside my university studies on weekdays, so I might not have enough time to review all submissions, pull requests, especially if the site becomes more popular in the future (which may never be the case, but who knows)
#FosseryWeb #FosseryWebMin #FosseryTech
