ssg-factory VS dodo-ssg

After ensuring that the CI was working, I decided to file an issue to Tue's repo and asked if I could help him test his text to HTML conversion. We worked with each other through Slack and GitHub, with myself taking notes of what he wanted to check and what the expected results should be. After struggling with managing and rebase commits when changing the code based on Tue's review, I was able to merge my pull request.

Afterwards, I pulled the repo to update my local and added more tests to my program as I recently refactored it to test easier. One of the commits passed testing after integrating GitHub Actions.

This week, I have a chance implement them into my project as an author to ensure my code stay consistent when different people contribute. The extensions I chose to add to the workflow are:

You can take a look at the commit and my Docusaurus demo site

Checkout THE COMMIT

You can take a look at Roxanne's repo here or mine

This week, I continued working with Git and Github to learn the basics of pull requests, code reviews and more. I collaborated with Tue Nguyen to add functionality to his Static Site Generator: tue-1st-ssg.

Francesco's SSG My SSG

The issues weren't severed, the program still functioned fine, but the HTML files generated had quite a few HTML markdown errors and the help command didn't print enough information. After some discussions, Oliver managed to fixed those issues easily, he also caused a bug but quickly patched it up.

It didn't take me a lot of time to fix the issue, so I decided, in return for his help, to test his program, which was also a SSG written in Javascript.

I setup a new action to run Jest tests on "ubuntu-latest" using both Node 14 and Node 16 every time a new Pull Request is created or a new commit is added. I tested it with a new PR and this is what showed up at the bottom:

This week I looked at code testing for my Static Site Generator dodo-SSG. I picked Jest for this since it is a very popular unit testing tool used by many open source projects.

There are some amazing tools available for developers to make coding easier. Today I am looking at a few of those and how it was like installing and using them in my dodo-SSG repo.

I chose to take two features from Docusaurus and implement them into my own dodo-SSG tool:

To practice, I worked on refactoring my dodo-SSG project in a new branch that I called refactoring. I started by fixing the code format from previous contributions using prettier. I then changed the code to get rid of global variables. To do that, I had to split up some code into separate smaller functions. At each of these steps, I created a new commit to make sure I could easily go back to the previous version if anything broke (And things broke a lot while doing this!).

This week I was contributing to the dodo-ssg's remote repo. My intention was to add a feature so that when someone types in "--config" or "-c" followed by a path to a JSON file, the program will read its contents and execute the commands inside of it. This is a useful feature when you don't want to see a super long line in the command line interface filled with a bunch of commands. Here is my PR.

In my Static Site Generator dodo-SSG, I added two new issues, one to Add support for inline code blocks and the other to Add support for a horizontal rule in Markdown.

While I was working on Tue's project, he was busy adding Markdown features on my dodo-SSG project. He sent me a pull request and I got started reviewing it. I noticed that the program was working only with Markdown files inside a directory when that directory was selected as input like: dodo-SSG -i ./directory but it did not work when a Markdown file was selected directly as input: dodo-SSG -i ./directory/file.md

Adding markdown support to Francesco's dodo-SSG

This was my first time sending my code for review to a classmate instead of submitting it to a professor. I like the fact that this activity is made to learn from others and to hopefully improve each other's code. I received some helpful feedback such as this issue. Using the option -v or --version on my program only showed the version number without anything else. I took that feedback and I improved the output to be: