siteit VS izyum

For Lab 9, I was tasked with adding continuous integration to Siteit - an SSG tool that parses markdown and text files and renders results in HTML files.

I encountered a similar bug in the main function of my SSG, because there were no instances where the main function was invoked without passing a value in the codebase.

I equipped Siteit - an SSG tool that I am one of the maintainers of, with static analysis tooling to ensure we, as developers, are writing code that is lint-free, and also correctly formatted.

For Lab 6, I had to familiarize myself with Docusaurus, copy a feature I found interesting, and implement it in my SSG.

Siteit has undergone profound changes as I did some significant refactoring and upgrading. It was a time-consuming and thought-provoking procedure overall. Nonetheless, it improved the source code and also my coding skills.

Siteit is a CLI tool that can .txt and .md files into HTML. Read more about Siteit here or check out the GitHub repo.

I decided to partner up with Taiomoor again and contribute to his repo siteit because he uses the javascript, which I am familiar with and his code style is decent.

Access Siteit on GitHub by clicking here.

The tool reports an issue when reading a single txt file as input (Closed)

Issues I Opened On My Partner's Project https://github.com/SerpentBytes/siteit/issues/1 This one is about the tool showing an error when accepting a single TXT as input, but the tool runs successfully without issue.

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.