izyum VS SSGo

This week we worked on integrating CI into our open-source projects. It is not the first time for me to work with CI and pipelines in general, but I find it very satisfying to put my project on some pipeline every time. These kinds of automations sometimes feel like magic to me.

Repo I picked for adding unit tests is izyum, which is another SSG written in Node.js and TypeScript.

This week's objective was to set up a unit test environment for izyum and write some unit tests in order to cover core functionality.

The first thing I added was a CONTRIBUTING.md file where I located all info that I used to have in readme.md file about how to install the tool for development setup.

First of all, I created the issue for izyum where I briefly described what I want to do and how I am going to achieve it. After that, I made an implementation and created PR, which approved myself :)

Izyum has a lot of space for improvement in terms of code refactoring. The first and most obvious thing was the fact that all code was contained in a single index.ts file, which is a really bad practice. The combination of facts that it is a school project with deadlines and sometimes I can be pretty bad in terms of time management made the codebase to be a mess.

Hi! Thanks for checking in. This week I worked on adding a new feature to another Static Site Generator Izyum. It is written in TypeScript and CLI apps in TypeScript is something new for me, so let me tell you how it went.

This week's task was to implement two features for the existing product, for me it is izyum, which is my ssg tool.

Last week I was presented with the opportunity to contribute to Izyum, a static site generator tool that creates an HTML file for each .txt file provided. Since the application had no existing support for processing markdown files, I began by filing an issue for it.

Later,Tymur connected with me via Slack DM to test his SSG tool Izyum. This SSG is created using Typescript and NodeJS.

Hey there! Thanks for coming by. Today, I want to tell you how I created a Continuous Integration workflow for SSGo using GitHub Actions, as well as how I created some tests for a different Open Source repo. Maybe you'll find something useful, too!

It was also important to document everything for coming developers, so I mentioned everything in CONTRIBUTING.md. Come check it out if you want :)

Hey there! Thanks for checking in again! This week, I've been trying to set up formatting and linting for my SSGo project. Maybe you'll get some valuable information from my experience!

I initially wanted SSGo to have full Markdown support, but when I was trying out Docusaurus I decided to use a ready-made package called gomarkdown for parsing.

Hey! Thanks for coming by. Today, I worked on refactoring the code for SSGo a bit, and eventually added a couple features that are making the 0.4 pre-release.

This week I worked with devils2ndself again, this time on his SSG project which was created using Go. This was my first time working with source code written in Go, but it was relatively simple with my prior knowledge of C++. I forked and created a new branch to make my changes to. Then, when I completed my changes I created a pull request (#13) and asked the owner to review my code and shortly after my changed were merged (de7d8773).

SSGo is at release 0.3, which means some additional Markdown features!

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.

New minor patch for SSGo - a Static Site Generator built with Go!

Yeah... I know, the name isn't that creative, but this is actually a new project I just published on GitHub! Come check it out at https://github.com/devils2ndself/SSGo