ModernSSG VS jun-ssg

Well, I was impressed looking at docusaurus implementing so many features to their website. I wanted to work on Theme and Search Engine Optimization that required a lot of effort and knowledge. So, I started with some basic features that support my ModernSSG.

I have seen two other projects so far making an SSG. One of them was in a different language, so that explains how it would look different. The other one - in the same language I used, JS - had a different structure and implementation.

I have been working with open source development for four weeks now. It has been a great pleasure to work with GitHub. After completing pull requests to other developers. Now, I am moving forward to learn to merge changes from different branches. Here's my Swift development code Repo

https://github.com/japneetsingh035/ModernSSG/issues/16 https://github.com/japneetsingh035/ModernSSG/issues/15 https://github.com/japneetsingh035/ModernSSG/issues/17

PR

The formatting made the code hard to read. This was a big one for me, because I spend quite a bit of time making sure my own code is clean and easy to read. I filed an issue under his repo explaining my thoughts with an example of how to clean it up.

Issue: https://github.com/juuuuuuun/jun-ssg/issues/14 Pull request: https://github.com/juuuuuuun/jun-ssg/pull/15 My issue: https://github.com/nguyenhung15913/OSD600-SSG/issues/14 Jun's pull request: https://github.com/nguyenhung15913/OSD600-SSG/pull/18

I have seen two other projects so far making an SSG. One of them was in a different language, so that explains how it would look different. The other one - in the same language I used, JS - had a different structure and implementation.

This was the biggest challenge for us among many other issues. This is because other problems can be quickly identified and solutions can be applied, but the problem is not easily solved. But, fortunately, my great colleague Alex gave us a clear answer to the problem, and fortunately we went beyond that and can focus on improving the task at hand.

npm i -g https://github.com/juuuuuuun/jun-ssg.git

I found their code pretty different. They used packages to solve problems, where I preferred to stay with "vanilla" and stick to what I know. I remember googling and finding the same packages as a solution that I saw in their code, but decided not to use those because of unfamiliarity. It wasn't that I didn't understand their code, but it was rather.. loaded. And without comments at all. They used like only three functions, grouping more things into a single pack. I instead made functions for every task. I'm not sure if it's a good or a bad thing. I also left comments everywhere, cause... I was used to it from my other classes, and I think it generally helps not only other people to read my code, but also myself.