<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Andrew Tassone</title>
    <description>The latest articles on DEV Community by Andrew Tassone (@drew5494).</description>
    <link>https://dev.to/drew5494</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F701287%2Fe8507809-e19b-47db-b8cf-47d985729b81.jpeg</url>
      <title>DEV Community: Andrew Tassone</title>
      <link>https://dev.to/drew5494</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/drew5494"/>
    <language>en</language>
    <item>
      <title>Squashing and Merging  - Telescope</title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Fri, 10 Dec 2021 22:33:15 +0000</pubDate>
      <link>https://dev.to/drew5494/squashing-and-merging-telescope-4i8h</link>
      <guid>https://dev.to/drew5494/squashing-and-merging-telescope-4i8h</guid>
      <description>&lt;p&gt;This week I completed by pull request with some squashing and the changes were &lt;a href="https://github.com/Seneca-CDOT/telescope/commit/cf03b25a6d26f3f7a590e491a855ea6feaf3dccf"&gt;merged&lt;/a&gt; by my professor.  I found that the &lt;a href="https://github.com/Seneca-CDOT/telescope/issues/2554"&gt;problem&lt;/a&gt; of page re-rendering and losing focus could be solved without using &lt;code&gt;autoFocus&lt;/code&gt; and sacrificing accessibility.  &lt;/p&gt;

&lt;p&gt;As pointed out by &lt;a class="mentioned-user" href="https://dev.to/dukemanh"&gt;@dukemanh&lt;/a&gt;
, the problem can be solved by simply returning a JSX expression in &lt;code&gt;searchInput.tsx&lt;/code&gt;. By doing so, it prevents a new component being returned every time and therefore stops the page from re-rendering unnecessarily. I also removed some fields and attributes that were &lt;a href="https://github.com/Seneca-CDOT/telescope/commit/cf03b25a6d26f3f7a590e491a855ea6feaf3dccf"&gt;unnecessary&lt;/a&gt; while in &lt;code&gt;AuthorSearchInput.tsx&lt;/code&gt;. &lt;/p&gt;

&lt;p&gt;It was a rather messy pull request in the end. I had to squash and rebase my two changes, but had some trouble doing so. I hadn't done much of either in previous pull requests. I am getting better at learning how to squash and rebase with this experience. &lt;/p&gt;

&lt;p&gt;It was fun interacting with so many students from Seneca that were interested in solving the same issue. I hope to contribute more to Telescope soon and hopefully not make such a mess with my pull requests in the future!&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>typescript</category>
    </item>
    <item>
      <title>Contributing to Telescope - Release 0.4</title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Sat, 04 Dec 2021 03:08:30 +0000</pubDate>
      <link>https://dev.to/drew5494/contributing-to-telescope-release-04-1in7</link>
      <guid>https://dev.to/drew5494/contributing-to-telescope-release-04-1in7</guid>
      <description>&lt;p&gt;While its been a busy week studying for final exams, I was able to work on contributing to Seneca's open-source project, &lt;a href="https://github.com/Seneca-CDOT/telescope"&gt;Telescope&lt;/a&gt; for my final project. I chose to fix the issue of the &lt;a href="https://github.com/Seneca-CDOT/telescope/issues/2554"&gt;search page re-rerendering on input&lt;/a&gt;. This was due the HTML 5 attribute, &lt;code&gt;autoFocus&lt;/code&gt; that was removed in a recent commit. &lt;/p&gt;

&lt;p&gt;ESLint recommends against using the attribute for accessibility purposes, however some &lt;a href="https://brucelawson.co.uk/2009/the-accessibility-of-html-5-autofocus/"&gt;sources&lt;/a&gt; indicate that it is acceptable, so long as the page is mainly used for searching such as in this case. &lt;/p&gt;

&lt;p&gt;Accessibility is very important for users on the web. I want t o ensure this does not impact screen readers in a negative way. I know fairly well how important they can be for people like myself who are visually impaired. &lt;/p&gt;

&lt;p&gt;Moving forward, I plan to also fix the rendering of the page after text is placed in the input field.  The search page is supposed to search for results after the user inputs text, but does not seem to work unless the search button is clicked. &lt;/p&gt;

&lt;p&gt;Contributing to Telescope has been fun and provides me with more experience for working on larger, more complex projects.  I will continue to contribute more to Telescope in the days ahead!&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>typescript</category>
    </item>
    <item>
      <title>The Great Site Generator v1.0 Release</title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Sat, 27 Nov 2021 20:35:20 +0000</pubDate>
      <link>https://dev.to/drew5494/the-great-site-generator-v10-release-84p</link>
      <guid>https://dev.to/drew5494/the-great-site-generator-v10-release-84p</guid>
      <description>&lt;p&gt;This week I focused on creating an initial v1.0 release of the project, &lt;a href="https://github.com/drew5494/the-great-site-generator/releases/tag/v1.0"&gt;The Great Site Generator&lt;/a&gt;. I was able to use Conan and Gitlab to create the release by following their &lt;a href="https://docs.gitlab.com/ee/user/packages/conan_repository/"&gt;guide&lt;/a&gt;. At first, I tried vcpkg, but found I couldn't get it to work with Gitlab. Conan was able to work well with CMake and did not require too much work. I was happy to see my project finally added to the &lt;a href="https://gitlab.com/drew5494/the-great-site-generator/-/packages/3942572"&gt;Gitlabs registry&lt;/a&gt;.&lt;br&gt;&lt;br&gt;
I had to alter my code before this release.  I wanted to ensure my code looked like it was ready and &lt;a href="https://github.com/drew5494/the-great-site-generator/commit/19d82c73e9de1f07551f29cbfdb137ea9f25bdca"&gt;added another function&lt;/a&gt; to get rid of the remaining global variables. I asked one of my fronds, who is not in my program, to test out my initial release by following the &lt;code&gt;README.md&lt;/code&gt;. They did not seem to have any trouble following it, except for requiring assistance to install Conan.&lt;br&gt;&lt;br&gt;
In order to try out TGSG, you can use the following command. &lt;br&gt;
&lt;code&gt;conan install the-great-site-generator/1.0@root+the-great-site-generator/stable --remote=gitlab--remote=gitlab&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;I hope the community enjoys v1.0 and helps to make it even better for the next release!&lt;/p&gt;

</description>
      <category>cpp</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Learning Github Actions - The Great Site Generator </title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Sun, 21 Nov 2021 03:09:50 +0000</pubDate>
      <link>https://dev.to/drew5494/learning-github-actions-the-great-site-generator-1mc6</link>
      <guid>https://dev.to/drew5494/learning-github-actions-the-great-site-generator-1mc6</guid>
      <description>&lt;p&gt;This week I learned about the great uses of Github Actions for this project. I &lt;a href="https://github.com/drew5494/the-great-site-generator/actions/workflows/learn-github-actions.yml"&gt;created a workflow&lt;/a&gt; that runs CMake and make on a linux system to compile and run the project. It then runs a command to ensure the project passes all tests with Google Test.  &lt;/p&gt;

&lt;p&gt;My partner, &lt;a class="mentioned-user" href="https://dev.to/jli"&gt;@jli&lt;/a&gt;
 used Catch2 to test his project. It looks very similar to Google Test and I was able to add another test to his project. This test is able to &lt;a href="https://github.com/joshuali7536/LennahSSG/pull/25"&gt;check if folders are read by the program&lt;/a&gt;. It was fun writing tests for someone else's project as I enjoy ensuring everything is running as smooth as it can be. &lt;/p&gt;

&lt;p&gt;Now that Ive used CI, I realize how useful it can be for testing pull requests in projects before accidentally merging them with mistakes. I hope to keep using it in my future projects!&lt;/p&gt;

</description>
      <category>cpp</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Code Reviews and Pull Requests - Release 0.3</title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Sat, 20 Nov 2021 00:40:04 +0000</pubDate>
      <link>https://dev.to/drew5494/code-reviews-and-pull-requests-release-03-4b73</link>
      <guid>https://dev.to/drew5494/code-reviews-and-pull-requests-release-03-4b73</guid>
      <description>&lt;p&gt;For my third release, I focused on contributing to the community with code reviews and pull requests. In both external and internal school projects, I helped to fix issues. &lt;/p&gt;

&lt;p&gt;I helped to &lt;a href="https://github.com/redxzeta/Awesome-Adoption/issues/213"&gt;improve image viewing&lt;/a&gt; in a React app called &lt;a href="https://github.com/redxzeta/Awesome-Adoption"&gt;Awesome Adoption&lt;/a&gt; that I had previously worked on during Hacktoberfest. Importing the Carousel component from Bootstrap, I was able to make images more accessible on mobile. I am still working on ensuring the image size is correct for all. &lt;/p&gt;

&lt;p&gt;I also contributed to my internal school project called &lt;a href="https://github.com/Seneca-CDOT/telescope"&gt;Telescope&lt;/a&gt;, a great tool for aggregating blog feeds. I helped fix an issue &lt;a href="https://github.com/Seneca-CDOT/telescope/pull/2493"&gt;improving local development setup&lt;/a&gt; of the status dashboard for development purposes. My work was later merged with the help of the community. &lt;/p&gt;

&lt;p&gt;I also did a few code reviews for the first time on Github.  I reviewed two pull requests on Telescope. I had never checked out a pull request before and it was interesting working to test others contributions. I approved a change for &lt;a href="https://github.com/Seneca-CDOT/telescope/pull/2480#pullrequestreview-811760996"&gt;updating the CSS of the build log dashboard&lt;/a&gt; and &lt;br&gt;
&lt;a href="https://github.com/Seneca-CDOT/telescope/pull/2485#pullrequestreview-810706413"&gt;adding a port redirect for nigx&lt;/a&gt;. I hope to contribute more to Telescope in the future! &lt;/p&gt;

</description>
      <category>javascript</category>
      <category>cpp</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Adding Google Test - The Great Site Generator </title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Sat, 13 Nov 2021 04:23:28 +0000</pubDate>
      <link>https://dev.to/drew5494/adding-google-test-the-great-site-generator-53l9</link>
      <guid>https://dev.to/drew5494/adding-google-test-the-great-site-generator-53l9</guid>
      <description>&lt;p&gt;This week I focused on adding a tester to my project. I chose to use &lt;a href="https://github.com/google/googletest"&gt;Google Test&lt;/a&gt; as I have read it is a very popular tester for C++. Google Test cam be used easily with CMake which was also being used in this project. &lt;br&gt;
I setup the tester by changing the &lt;code&gt;CMakeLists.txt&lt;/code&gt; which can download the Google Test folder to the root directory by only using &lt;code&gt;FetchContent_Declare&lt;/code&gt;.&lt;br&gt;&lt;br&gt;
While writing the &lt;a href="https://github.com/drew5494/the-great-site-generator/commit/e12b58fe1bcbf3e7977e3efd753a6bcf6f9b4810"&gt;test cases&lt;/a&gt;, I learned that it was more difficult than I had expected. I made sure my tests checked that the HTML output files were correct by reading the file and comparing it to the correct lines. I got stuck trying to get CMake to compile correctly. I eventually figured out that I did not have the correct executable files listed. &lt;/p&gt;

&lt;p&gt;I have used a tester before, when contributing to other projects on GitHub. They are a great way for developers to check their own code and for others to contribute without breaking any parts of the project. I will continue to try to incorporate testers like Google Test in my projects. &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>cpp</category>
    </item>
    <item>
      <title>Adding a Linter - The Great Site Generator </title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Sat, 06 Nov 2021 03:39:38 +0000</pubDate>
      <link>https://dev.to/drew5494/adding-a-linter-the-great-site-generator-1ph3</link>
      <guid>https://dev.to/drew5494/adding-a-linter-the-great-site-generator-1ph3</guid>
      <description>&lt;p&gt;This week I focused on adding &lt;code&gt;clang-format&lt;/code&gt; to &lt;a href="https://github.com/drew5494/the-great-site-generator/commit/d2ce6eea082830dfacaf10f3ed9008b91d64937a"&gt;my code&lt;/a&gt; to have better consistency when other developers are contributing.  I chose this as it has a &lt;a href="https://marketplace.visualstudio.com/items?itemName=xaver.clang-format"&gt;VSCode extension&lt;/a&gt; and works very well with C++ which is what my project is written in. &lt;/p&gt;

&lt;p&gt;I added settings in the &lt;code&gt;.vscode&lt;/code&gt; folder to ensure that every time a user saves their work, the code is automatically formatted according to the &lt;code&gt;.clang-format&lt;/code&gt; file requirements. Originally, there was a script I created, but I decided to remove it as it wasn't very necessary when VSCode automatically formats it anyway.&lt;br&gt;&lt;br&gt;
After running it on my code, I noticed it had found many things it didn't like. It mostly indented long lines into shorter lines for easier readability. It also moved some braces around. &lt;/p&gt;

&lt;p&gt;I finally learned how I can integrate formatters into my IDE and make it easier for developers to contribute. That is what Github is all about after all!  &lt;/p&gt;

</description>
      <category>cpp</category>
      <category>opensource</category>
    </item>
    <item>
      <title>My Last Pull Requests For Hacktoberfest  </title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Fri, 29 Oct 2021 19:26:57 +0000</pubDate>
      <link>https://dev.to/drew5494/my-last-pull-requests-for-hacktoberfest-jch</link>
      <guid>https://dev.to/drew5494/my-last-pull-requests-for-hacktoberfest-jch</guid>
      <description>&lt;p&gt;This last week of Hacktoberfest, I finished my last pull requests. I solved an issue for a &lt;a href="https://github.com/drew5494/Awesome-Adoption"&gt;Pet Adoption site&lt;/a&gt; built with React. The other pull request involved supporting &lt;code&gt;count(1)&lt;/code&gt; for an SQL database queries in &lt;a href="https://github.com/questdb/questdb"&gt;QuestDB&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;To solve the first &lt;a href="https://github.com/redxzeta/Awesome-Adoption/issues/198"&gt;issue&lt;/a&gt;, I had to create a private route for the &lt;code&gt;reset-password&lt;/code&gt; page. I had never done this before, so I had to do some research on private routes. I made a mistake at first by using the wrong authentication type but the developer was very helpful and I figured it out.&lt;/p&gt;

&lt;p&gt;The other &lt;a href="https://github.com/questdb/questdb/issues/1420"&gt;issue&lt;/a&gt; for QuestDB involved accepting &lt;code&gt;count(1)&lt;/code&gt; the same way as &lt;code&gt;count()&lt;/code&gt; in a database query. I struggled very much with this as it was a larger project. The developer again gave me some directives on what to do. &lt;/p&gt;

&lt;p&gt;Both issues were eventually &lt;a href="https://github.com/redxzeta/Awesome-Adoption/pull/202"&gt;merged&lt;/a&gt; just in time. Hacktoberfest was a challenge for me, who is not very experienced as a developer yet, but I managed to complete four pull requests before the deadline and learned a lot from the experience. Best of luck to the other developers who have contributed greatly! &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>hacktoberfest</category>
      <category>react</category>
    </item>
    <item>
      <title>First Pull Requests - SnapIT HacktoberFest </title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Fri, 15 Oct 2021 18:51:13 +0000</pubDate>
      <link>https://dev.to/drew5494/first-pull-requests-snapit-hacktoberfest-434e</link>
      <guid>https://dev.to/drew5494/first-pull-requests-snapit-hacktoberfest-434e</guid>
      <description>&lt;p&gt;I began working on pull requests for HacktoberFest this week. I haven't really done much work on big repos, other than my classmates or my own. I found a great project by &lt;a href="https://github.com/SnapITSolutions"&gt;SnapITSolutions&lt;/a&gt; that is an open source project that directs users to their in-person and virtual hackathons. &lt;/p&gt;

&lt;p&gt;I enjoy working with react and websites so I thought this would be fun to work on.  I solved two open issues that were created by another developer.  The first was &lt;a href="https://github.com/SnapITSolutions/snapit-hacktoberfest/issues/114"&gt;adding support for other languages to the homepage&lt;/a&gt;. The other included &lt;a href="https://github.com/SnapITSolutions/snapit-hacktoberfest/issues/113"&gt;adding support for other languages to the registration page&lt;/a&gt;.  &lt;/p&gt;

&lt;p&gt;In order to fix these issues, I first had to add the translations required into a json file for both &lt;code&gt;es-us&lt;/code&gt; and &lt;code&gt;en-us&lt;/code&gt;. I then had to ensure the react-intl module was imported to provide the service for each page. Lastly, I added &lt;code&gt;FormattedMessage&lt;/code&gt; to all buttons and textfields as a wrapper, in order to translate all of the values. &lt;/p&gt;

&lt;p&gt;After I was done creating my pull request, I realized I missed a step in the contribution guidelines that require all pull requests to be linted and tested with &lt;a href="https://eslint.org"&gt;ESLint&lt;/a&gt;. Tests failed the first time but I was able to correct it by simply importing the react-intl module in one of the pages. &lt;/p&gt;

&lt;p&gt;The code was eventually &lt;a href="https://github.com/SnapITSolutions/snapit-hacktoberfest/commit/d75cdb318499422d3beb7a6c53f1be68ea76f5d0"&gt;merged&lt;/a&gt; by the developer. I created one pull request instead of two which meant less credit for Hacktoberfest, so the developers were nice enough to allow me to create another one.  &lt;/p&gt;

&lt;p&gt;It felt great contributing to the community and communicating with someone who's all the way in Texas. I hope to continue to work on this project and make it even better! &lt;/p&gt;

</description>
      <category>javascript</category>
      <category>opensource</category>
      <category>react</category>
      <category>hacktoberfest</category>
    </item>
    <item>
      <title>Refactoring The Great Site Generator</title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Fri, 15 Oct 2021 16:40:42 +0000</pubDate>
      <link>https://dev.to/drew5494/refactoring-the-great-site-generator-1gl5</link>
      <guid>https://dev.to/drew5494/refactoring-the-great-site-generator-1gl5</guid>
      <description>&lt;p&gt;This week, I focused on refactoring this project using &lt;code&gt;git rebase&lt;/code&gt; to rewrite history on a branch for my first time. I also learned how to use &lt;code&gt; git commit --amend&lt;/code&gt; to change the information in my commit. &lt;/p&gt;

&lt;p&gt;I wanted to reduce redundancy in my code so &lt;a href="https://github.com/drew5494/the-great-site-generator/commit/87ff668cb13ebb6c40451035daadc957de4cf210"&gt;I created a function&lt;/a&gt; called &lt;code&gt;readFolder()&lt;/code&gt; for reading folders. I also combined &lt;code&gt;readMarkdownFile()&lt;/code&gt; into &lt;code&gt;readFile()&lt;/code&gt;. This supports both file types of either .txt or .md. &lt;/p&gt;

&lt;p&gt;Lastly, I separated these functions into a new class called &lt;a href="https://github.com/drew5494/the-great-site-generator/blob/main/thegreatsitegenerator/reading.h"&gt;Reading&lt;/a&gt;. I then placed the class into its own &lt;code&gt;reading.h&lt;/code&gt; file. I broke it a few times during this process, usually just forgetting a brace somewhere. &lt;/p&gt;

&lt;p&gt;Using the interactive vim to edit commits was new to me. Ive used command line editors before but not very much. At first, I made a few mistakes by accidentally adding too many spaces between the commit ID and action. I received a few errors but figured it out eventually!&lt;/p&gt;

&lt;p&gt;Changing git history was interesting and a useful thing to learn when cleaning up code and changing commits. It was confusing to do at first but I will keep practicing. I hope to use it again in the future!  &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>cpp</category>
    </item>
    <item>
      <title>Drafting My First Pull Request</title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Mon, 11 Oct 2021 02:56:39 +0000</pubDate>
      <link>https://dev.to/drew5494/drafting-my-first-pull-request-7gg</link>
      <guid>https://dev.to/drew5494/drafting-my-first-pull-request-7gg</guid>
      <description>&lt;p&gt;This week, I focused on adding a new feature to my friends site generator, &lt;a href="https://github.com/joshuali7536/LennahSSG/pull/16"&gt;LENNAH SSG&lt;/a&gt;. Using a fork of his project with an &lt;a href="https://github.com/drew5494/LennahSSG/tree/issue-15"&gt;issue branch&lt;/a&gt;, I was able to add support for config files using &lt;code&gt;--config&lt;/code&gt;.  I also created a &lt;a href="https://github.com/joshuali7536/LennahSSG/pull/16"&gt;draft pull request&lt;/a&gt; in order to better communicate our ideas to each other. &lt;/p&gt;

&lt;p&gt;I ran into issues adding support for folders in the config file, as it has to recognize both files or folder.  I solved this by first checking for a &lt;code&gt;.txt&lt;/code&gt; extension in the JSON file and then using the recursive file checking method, implemented before to read files within a folder. &lt;/p&gt;

&lt;p&gt;It was very difficult working on someone else's code, however after some time playing with it, it feels just like my own! My friend, &lt;a class="mentioned-user" href="https://dev.to/jli"&gt;@jli&lt;/a&gt;
 was very satisfied with my work and I hope to collaborate with him again in the future. &lt;/p&gt;

&lt;p&gt;I learned a great deal from this experience. I am now more familiar with how I can collaborate with others on Github and contribute to the community using the draft pull request feature.  I also learned more about merging and pushing to a remote repo. &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>cpp</category>
    </item>
    <item>
      <title>Adding Language Support and More! - The Great Site Generator</title>
      <dc:creator>Andrew Tassone</dc:creator>
      <pubDate>Thu, 30 Sep 2021 21:36:19 +0000</pubDate>
      <link>https://dev.to/drew5494/adding-language-support-and-more-the-great-site-generator-1jkl</link>
      <guid>https://dev.to/drew5494/adding-language-support-and-more-the-great-site-generator-1jkl</guid>
      <description>&lt;p&gt;Along with support for html headers in markdown, the &lt;code&gt;--lang&lt;/code&gt; flag for &lt;a href="https://github.com/drew5494/the-great-site-generator/issues/12"&gt;specifying a language&lt;/a&gt; is now supported! &lt;/p&gt;

&lt;p&gt;Three language tags including English Canada &lt;code&gt;en-CA&lt;/code&gt;, French &lt;code&gt;fr&lt;/code&gt; and Brazilian Portuguese &lt;code&gt;pt-BR&lt;/code&gt; are currently supported with more coming in the near future! &lt;/p&gt;

&lt;p&gt;Other features, such as &lt;a href="https://github.com/drew5494/the-great-site-generator/issues/13"&gt;more accurate error detection and prevention&lt;/a&gt; has also been improved. If there are no errors, the program will exit with 0. Otherwise, it will exit with 1 as per C++ standards. &lt;/p&gt;

&lt;p&gt;This was the first time I worked on issues using Feature Branches. I usually just work on my main branch, but I'm aware a lot can go wrong that way!  &lt;/p&gt;

&lt;p&gt;I will be working on adding more features soon. If you'd like to contribute, you can fork it on &lt;a href="https://github.com/drew5494/the-great-site-generator"&gt;Github&lt;/a&gt;  &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>cpp</category>
    </item>
  </channel>
</rss>
