my-button-ssg VS nan1-ssg

I also added a test to a partner's SSG. Writing a test for their SSG was not difficult as their code was easy to understand. They were using the same testing framework/workflow as me.

Test Function htmlGen file Adding Jest Updatting my-button.js Coverage Files

This week, I was tasked with adding config file parsing to another student's ssg. I chose to add this feature to Oscar's my-button-ssg. The config file would contain the available options for the ssg in JSON format. I created an issue and began implementing the new feature.

I decided to look at their ssg project (my-button-ssg) which was made using JavaScript. However, since someone had already created an issue for markdown support, I decided to pick another project. After some browsing, I decided to add markdown support to SSGo since it was written using Go. I thought it would be nice to learn more about Go since I had never used it. So, I created an issue, forked the repo, and started working on it.

I worked on this git repo and here I made pull request.

Link to pull request to my repo: https://github.com/LostButton/my-button-ssg/pull/7#event-7435285897 Link to my repo: https://github.com/LostButton/my-button-ssg

Link to Repository

This week I added CI to my SSG. I used GitHub's CI service GitHub Actions to accomplish this. It was very easy to set up as I just had to find the Node.js workflow and add it.

This week I added some testing tools to my SSG. The project now uses Jest for testing. I chose to use Jest because it is a very popular testing framework for JavaScript. I contemplated using Mocha, but after doing some research, decided Jest was easier to use out of the box. Installing Jest was easy. All I had to do was install it using npm: npm install --save-dev jest.

This week I added some static analysis tools to my SSG. The tools I added are Prettier and ESLint. Prettier is a code formatter to make code consistent and ESLint checks your code for any common errors/warnings.

I also chose a feature from Docusaurus to add into my own SSG. The previous version of my SSG had some basic Markdown support, so I decided to upgrade my Markdown support by using an existing open source Markdown converter.

This week, I refactored my SSG repo to clean up my repo. Here is the commit.

I decided to collaborate with Neil and contribute to his static site generator.

This week, I continued to work on my SSG and I added two new features.

My Filed Issue

node_modules shouldn't be commited in git - In another class I took with Prof. Humphrey (CCP555), we learned about the importance of .gitignore files, and that the node_modules is a folder we should avoid committing to git.

This week, I created my own SSG (static site generator) called nan1-ssg using JavaScript and node.js. My SSG will generate .html files from .txt files as specified by the user.