jellybean VS GMOT-SSG

After writing a few unit and E2E Integration tests for my static site generator, Jellybean, last week, this week I added Continuous Integration to the repository. It was very easy to set up and is useful if you or other contributors forget to manually test while making changes. It ensures that changes or pull requests made to the main branch are automatically tested by running a workflow.

For Leyang's project, I found that getHtlmlTitleBody() was not tested yet so I decided to contribute some tests to it. This function accepts the content of the file as a string and a boolean indicating whether it's a text file or not, it then returns an object with 2 properties: title and body.

This week, I continued working on my static site generator Jellybean and focused on creating and running tests for the program. I decided to use Jest for testing, mostly because it was what was recommended and I have tried other tools such as Jasmine and Karma before, but not Jest, so I thought this would be a good opportunity to learn how it works.

For my own static site generator, Jellybean, one feature of Docusaurus that I wanted to implement was full markdown support. This is because my static site generator previously only had partial markdown support, which is not very user-friendly. Thankfully, there are a some great open-source libraries which can provide full markdown support and I decided to use markdown-it for my project.

It was my first time learning about interactive rebases and I found this process to be so useful as it gives you so much freedom in customizing your commits. I used the interactive rebase command (git rebase main -i) to squash all my commits into a single commit. In addition, I used the git commit --amend command to modify my commit message and add more details. After this exercise, I feel so much more confident in using rebases to modify my commits and project history.

This week, I worked on Leyang Yu Static Site Generator project called jellybean. I added a new issue on her repo to let her know that I wanted to add a new --config option to support a JSON config file. Luckily she agreed, so I got started right away.

I also received an issue and pull request to my repo. I had a lot of great discussion with Francesco and he mentioned that he was "really seeing the benefit of code review now" after I tested his changes and made several suggestions. I was able to test his code by adding his repo as a remote to my local repo and creating a tracking branch. After going back and forth a few times and fixing all issues, I was successfully able to merge Francesco's branch with my main branch.

I've been working on a static site generator called Jellybean over the past few weeks and this week, I wanted to add a few more features:

For this lab, I decided to contribute to Leyang Yu project, Jellybean SSG, . He is also using JavaScript so I decided that it would be a good idea to try adding to his project, so I filled and Issue Issue #6.

Similarly, Gustavo created an issue, added markdown support, and created a pull request for my repo. I provided some comments.

Today I will talk about my first experience publishing a package to npm. Which means that now you can install it on your machine and use it! My project is here in case you want to check it. It is a Static Site Generator; it will take txt or md files as input and transform it in HTML!

I added some tests to Gustavo's SSG project. I added some e2e tests to his repo which reminded me to add e2e tests to my repo as well :D

This week lab’s goal is to test out our SSG. We were instructed to use a tester like Jest to test our code and check if everything is working as intended.

This time this lab is all about setting configuration files for our SSG project. mine. The configuration that we should add is:

For my SSG, I decided to go with the Full Markdown support. Issue #16 The Full Markdown support consists in making the SSG able to parse all markdown into HTML. As described in LAB 06, I could use a open source library to help me with that.

To be completely honest, I had refactored my code long time ago, when David made Issue #7 and Issue #6. So for this lab I had to make only a few changes to make it good to go.

For this week, the goal was to choose 2 features and add it to our SSG project. GMOT-SSG But each feature had to be in a different branch so we could have different merging experience.

In the other hand, Leyang Yu filled an issue in my repository. Issue #8. His issue goal was to add the Markdown feature to my project.

First, I filed an issue in the GMOT-SSG repository. For this issue, I wanted to add markdown support to the program. This involved several tasks including:

GMOT-SSG