qck VS siteit

Anatoliy's Project on GitHub: https://github.com/aserputov/qck-ssg-final

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.