ssg-factory VS GMOT-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.

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