<?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: irenejoeunpark</title>
    <description>The latest articles on DEV Community by irenejoeunpark (@irenejoeunpark).</description>
    <link>https://dev.to/irenejoeunpark</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%2F703905%2F1758f53b-2746-453b-9157-17ee42d35813.png</url>
      <title>DEV Community: irenejoeunpark</title>
      <link>https://dev.to/irenejoeunpark</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/irenejoeunpark"/>
    <language>en</language>
    <item>
      <title>Release 0.4 - Unfinished, but to be continued.</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Thu, 16 Dec 2021 21:19:36 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/release-04-unfinished-but-to-be-continued-179e</link>
      <guid>https://dev.to/irenejoeunpark/release-04-unfinished-but-to-be-continued-179e</guid>
      <description>&lt;p&gt;My Release 0.4 is still not finished but will be continued after. &lt;br&gt;
I was not able to get the PR reviewed since I opened very late. Since I started late, everything was delayed. And installing pnpm on macbook(M1) did not work either. &lt;br&gt;
After a few tries, I had to borrow a windows machine from my friend so that I can work with pnpm. &lt;br&gt;
It still has error when I try to run the whole program using pnpm start, however I was able to run the front-end of the application using "pnpm dev" command. &lt;br&gt;
The fix I have pushed is yet a single small one, however I will try to fix the environment error and resume working on the other issues that has been assigned to me. &lt;/p&gt;

&lt;p&gt;It is still remaining unfinished, but throughout the course, it was a great opportunity to learn about opensources, and contributing to other projects.&lt;br&gt;
Development, sure, need a coding knowledge background, but that is not everything. Outside of the coding skills, I was able to gain knowledges that would be a huge gain.&lt;/p&gt;

&lt;p&gt;Development is a continuous progression, not an one-time event. Open source development is something that allows developers to find their potential to DO.&lt;br&gt;
It was a great pleasure working with the open sources. &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>pnpm</category>
      <category>git</category>
    </item>
    <item>
      <title>Working on Telescope issues</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Thu, 16 Dec 2021 21:03:55 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/working-on-telescope-issues-3c9n</link>
      <guid>https://dev.to/irenejoeunpark/working-on-telescope-issues-3c9n</guid>
      <description>&lt;p&gt;Different from what I have planned first, I contributed on two different projects, &lt;a href="https://github.com/Seneca-CDOT/telescope"&gt;Telescope&lt;/a&gt;, and &lt;a href="https://github.com/felvin-search/instant-apps"&gt;instant-apps&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For the first &lt;a href="https://github.com/Seneca-CDOT/telescope/issues/2583"&gt;issue&lt;/a&gt; I picked, I found the bug in a previous release, which I worked on a mobile UI. The title container is overflowing when scrolling. Screen record of the issue is also in the issue page. I was stuck because of that issue and was trying to find out the cause, but failed in Release 0.3.&lt;/p&gt;

&lt;p&gt;However, I noticed that the issue was not only existing in my branch, it was also existing in the main branch. So I decided to file an issue as a bug so that I can work on this as a follow up. &lt;/p&gt;

&lt;p&gt;After several tries with changing margin, padding and overflow settings in different properties, I finally got to make it work after adding overflowY as hidden in titleContainer. &lt;/p&gt;

&lt;p&gt;The fixes are in &lt;a href="https://github.com/Seneca-CDOT/telescope/pull/2624"&gt;this PR&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;An issue for enhancement, which is a new feature, I decided to work on adding the metronome player to the instant-apps. &lt;br&gt;
Instant app is a search engine that would bring the small apps when searching a certain keywords. &lt;/p&gt;

&lt;p&gt;As my first &lt;a href="https://github.com/felvin-search/instant-apps/issues/237"&gt;contribution&lt;/a&gt;, I worked on adding a metronome app to the project. &lt;br&gt;
Since I have an experience adding an external API for react application, I decided to work on this new feature that could be shown when searching for "metronome", "play bpm", "bpm", and etc. &lt;br&gt;
For the project, I aggregated an external &lt;a href="https://www.npmjs.com/package/@kevinorriss/react-metronome"&gt;API&lt;/a&gt;. &lt;br&gt;
The changes are in this &lt;a href="https://github.com/felvin-search/instant-apps/pull/276"&gt;PR&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;More issues are still in progress, which I will continue to work on.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>react</category>
    </item>
    <item>
      <title>Planning on contribution in Telescope</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Wed, 08 Dec 2021 18:25:26 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/planning-on-contribution-in-telescope-36o</link>
      <guid>https://dev.to/irenejoeunpark/planning-on-contribution-in-telescope-36o</guid>
      <description>&lt;p&gt;I decided to choose Telescope to work for my release 0.4.&lt;br&gt;
In Release 0.4 we are expected to add features in the existing open source project. &lt;br&gt;
Since I have contributed on telescope in Release 0.4, and it would be great to work on a different area of the project, I decided to pick some issues, and create a new issue in telescope.&lt;br&gt;
Most of the issues were taken by other students, however there was a new &lt;a href="https://github.com/Seneca-CDOT/telescope/issues/2488"&gt;issue&lt;/a&gt; that I would like to work on, since I have never got to work on the security and policy side in any of the project.&lt;/p&gt;

&lt;p&gt;Also, I did not know that clicking the date or author would open the original post in a new tab, I filed a new &lt;a href="https://github.com/Seneca-CDOT/telescope/issues/2559"&gt;issue&lt;/a&gt; so that clicking the title would open the original post in a new tab. I had to close the issue since now I got to know that the feature is not needed. &lt;/p&gt;

&lt;p&gt;I will keep searching for new issues in other projects as well that I could contribute. &lt;/p&gt;

</description>
    </item>
    <item>
      <title>External PR for Release 0.3</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Thu, 25 Nov 2021 21:10:38 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/external-pr-for-release-03-48a0</link>
      <guid>https://dev.to/irenejoeunpark/external-pr-for-release-03-48a0</guid>
      <description>&lt;p&gt;For the external issue, I chose &lt;a href="https://github.com/MichaelCurrin/badge-generator"&gt;badge-generator&lt;/a&gt; which I was able to find in one of the colleague's blog post. It was created with Vue, and I had zero insight on the framework. I first had to research on the framework and understand the syntax, and how it is applied in the code. You can find the issue &lt;a href="https://github.com/MichaelCurrin/badge-generator/issues/101"&gt;here&lt;/a&gt;.&lt;br&gt;
There were a few components that are needed to be modified in the project. The owner of the project wanted to have all of the tabs to have the html and markdown selection persisted for one single toggle. &lt;/p&gt;

&lt;p&gt;I first had to debug to find out what it does when toggled the switch. It took me the longest time in the whole work. After I find out which action is called when the switch is toggled, I was able to persist the selection by adding an Object in store class. The progress and the changes are in this &lt;br&gt;
&lt;a href="https://github.com/MichaelCurrin/badge-generator/pull/135"&gt;PR&lt;/a&gt;.&lt;br&gt;
I still have to work on this more to improve the feature. &lt;/p&gt;

&lt;p&gt;Open source development to me, is more than just a coding or testing. This is a mixture of cooperation and individual work and on top of that, it is the most relevant on how to communicate properly when collaborating . &lt;br&gt;
Through my six terms of school works, I learned how to code in different languages, In my co-op experiences, I learned how to collaborate. And in this course, open source development, now I am learning how to communicate and work on a same project with different perspectives properly. &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>vue</category>
      <category>typescript</category>
    </item>
    <item>
      <title>[Release0.3]Code Reviews</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Tue, 23 Nov 2021 23:45:13 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/release03code-reviews-2n76</link>
      <guid>https://dev.to/irenejoeunpark/release03code-reviews-2n76</guid>
      <description>&lt;p&gt;As a part of Release0.3, I reviewed two internal PRs opened by other students. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/Seneca-ICTOER/IPC144/pull/104#pullrequestreview-810492913"&gt;First code review&lt;/a&gt; was a documentation update for IPC144. It was made by Antonio Bennett.I looked for other documentations in the repo, and the documentation guide that was created as an &lt;a href="https://github.com/Seneca-ICTOER/IPC144/issues/18"&gt;issue&lt;/a&gt;. It was first time reviewing the documentation and following documentation convention of the whole project is very important for the readers and contributors. I reviewed and comment in the PR, and it seems like the updates were looking good. While I was reviewing the code, I had one curiosity in the styling and commented those and got answered. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/Seneca-ICTOER/IPC144/pull/102#pullrequestreview-810501210"&gt;Second code review&lt;/a&gt; was a similar change with the first one, but it seems like it had more tables and I commented about the styling of the documentation. Because it had a lot of tables and list in the document, it supposed to have unified design for all of the content, while it has little more work left to do on those. First part of the documentation was having all of its content aligned left, while other contents are centred. And I looked for other documentation that has tables, and the styling seemed it does not match with other documentation. &lt;/p&gt;

&lt;p&gt;Since it was my first time doing the code reviews for the project that was not written by me, it was very interesting and got study the code and other conventions of the project by reading some documentation of the project. To do a proper code review, I should know what is the issue correctly, and what should be a good change. &lt;/p&gt;

</description>
      <category>codereview</category>
      <category>documentation</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Internal PR for Release 0.3</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Sat, 20 Nov 2021 19:51:33 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/internal-pr-for-release-03-421g</link>
      <guid>https://dev.to/irenejoeunpark/internal-pr-for-release-03-421g</guid>
      <description>&lt;p&gt;Using React style methods and css properties, I was working on (and still in progress) for the telescope project to have the GitHub information for the mobile view. The reason I picked this &lt;a href="https://github.com/Seneca-CDOT/telescope/issues/2373"&gt;issue&lt;/a&gt; was because I wanted to work on something that I would like to work on in the future. Since I am interested in the front end development, and I have barely no experience and knowledge on that, I wanted to gain more experience by working on this issue. &lt;/p&gt;

&lt;p&gt;I first had to understand the structure and how it is getting the GitHub info from the parsed links.&lt;br&gt;
You will be able to see all the progress in this &lt;a href="https://github.com/Seneca-CDOT/telescope/pull/2491"&gt;PR&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I used some cool library of React, Material-UI and its features that could be used in UI side of the development. &lt;br&gt;
Using a component called Accordion, I was able to make the title container area click and expandable, and made those expanded area contain all of the Github information.&lt;/p&gt;

&lt;p&gt;There are some future improvements that I could, or someone else could make is to create some cool animation when toggle a github icon or other button to make the Github information to be shown in action. &lt;/p&gt;

</description>
      <category>ui</category>
      <category>react</category>
      <category>css</category>
    </item>
    <item>
      <title>Github CI Integration</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Fri, 19 Nov 2021 23:06:51 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/github-ci-integration-4de9</link>
      <guid>https://dev.to/irenejoeunpark/github-ci-integration-4de9</guid>
      <description>&lt;p&gt;As a coursework of OSD600, we were integrating CI on our projects. Since my project was being created with Java, and added Maven for dependency and artifacts, I added maven run in my GitHub action CI. &lt;/p&gt;

&lt;p&gt;I have experienced those automated tests and checks through GitHub actions when I was contributing on huge projects before. It is a very cool feature that could allow multiple contributors to check if they broke any core functionality when contributing. &lt;/p&gt;

&lt;p&gt;I had to modify the yml file multiple times because it was not functioning properly at first. I had to add some plugin and scope in pom.xml for maven automated tests.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;groupId&amp;gt;&lt;/span&gt;org.apache.maven.plugins&lt;span class="nt"&gt;&amp;lt;/groupId&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;artifactId&amp;gt;&lt;/span&gt;maven-surefire-plugin&lt;span class="nt"&gt;&amp;lt;/artifactId&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;version&amp;gt;&lt;/span&gt;2.22.2&lt;span class="nt"&gt;&amp;lt;/version&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And after adding surefire, below commands was finally picking up Junit classes for testing&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;      - name: Build maven package
        run: mvn package -DskipTests
      - name: Test
        run: mvn test
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I wanted to add formatter and linter inside the CI, but since the formatter and linter I have used in my project had no functionality to check and format the code with "mvn" command, I had to postpone it to later development. &lt;/p&gt;

&lt;p&gt;For the future improvement, I would like to add a script to run formatter and linter that could automatically reformat and check all of the file, and add the script into the CI. This would require more research and knowledge on CI. &lt;/p&gt;

&lt;p&gt;A successful action that ran for the pull request could be found &lt;a href="https://github.com/irenejoeunpark/ssgApplication/runs/4269864900?check_suite_focus=true"&gt;here&lt;/a&gt;. I created a unit test to test if the html header &amp;amp; footer writer method is working properly. &lt;/p&gt;

&lt;p&gt;Second part of the lab was to partner up with another student and create a unit test for their project and see if the CI is working properly. &lt;/p&gt;

&lt;p&gt;I contributed on Le Minh Pham's &lt;a href="https://github.com/lmpham1/cool_ssg_generator"&gt;project&lt;/a&gt; which was written in Python. &lt;br&gt;
Unit testing in python was a lot simpler than using Java.&lt;br&gt;
I created two unit testings, which have test cases for horizontal rules and a combined markdown feature. &lt;br&gt;
First I failed on horizontal rules testing, and had to discuss with Le Minh Pham, he was able to fix the part where it breaks the &lt;/p&gt;
&lt;p&gt; tag inside the html body. &lt;/p&gt;

&lt;p&gt;After his fixes and commits, my &lt;a href="https://github.com/lmpham1/cool_ssg_generator/pull/26"&gt;PR&lt;/a&gt; was able to pass the automated checks and was able to get merged.&lt;/p&gt;

</description>
      <category>github</category>
      <category>java</category>
      <category>python</category>
      <category>testing</category>
    </item>
    <item>
      <title>Unit testing using JUNIT</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Fri, 12 Nov 2021 21:41:59 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/unit-testing-using-junit-5bio</link>
      <guid>https://dev.to/irenejoeunpark/unit-testing-using-junit-5bio</guid>
      <description>&lt;p&gt;As a weekly course work, I added JUNIT testing framework into my ssg application. &lt;/p&gt;

&lt;h3&gt;
  
  
  Adding framework
&lt;/h3&gt;

&lt;p&gt;Junit is a most popular testing framework that is being used for Java developers. &lt;br&gt;
I was able to add Junit API and frameworks using maven dependencies and it was very quick and easy. &lt;br&gt;
After add the dependencies, I was able to create test class from the class that I want to test. &lt;/p&gt;
&lt;h3&gt;
  
  
  About Unit testing
&lt;/h3&gt;

&lt;p&gt;It was my first time creating testing methods for unit tests.&lt;br&gt;
Unit tests are created based on assert methods that are comparing the expected value and actual value. &lt;/p&gt;
&lt;h3&gt;
  
  
  Wrote first unit test for the simplest method
&lt;/h3&gt;

&lt;p&gt;Below is my first unit testing method, which was to test the function for converting the filename from array of strings to a string.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="kt"&gt;void&lt;/span&gt; &lt;span class="nf"&gt;testFileNameReader&lt;/span&gt;&lt;span class="o"&gt;()&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;
        &lt;span class="nc"&gt;String&lt;/span&gt;&lt;span class="o"&gt;[]&lt;/span&gt; &lt;span class="n"&gt;fileName1&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;&lt;span class="s"&gt;"example"&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="s"&gt;"file"&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="s"&gt;"name.txt"&lt;/span&gt;&lt;span class="o"&gt;};&lt;/span&gt;
        &lt;span class="n"&gt;assertEquals&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="s"&gt;"example file name.txt"&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt;&lt;span class="nc"&gt;HTMLBuilder&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;fileNameReader&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="n"&gt;fileName1&lt;/span&gt;&lt;span class="o"&gt;));&lt;/span&gt;

        &lt;span class="nc"&gt;String&lt;/span&gt;&lt;span class="o"&gt;[]&lt;/span&gt; &lt;span class="n"&gt;fileName2&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;&lt;span class="s"&gt;"sample.md"&lt;/span&gt;&lt;span class="o"&gt;};&lt;/span&gt;
        &lt;span class="n"&gt;assertEquals&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="s"&gt;"sample.md"&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt;&lt;span class="nc"&gt;HTMLBuilder&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;fileNameReader&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="n"&gt;fileName2&lt;/span&gt;&lt;span class="o"&gt;));&lt;/span&gt;
    &lt;span class="o"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Core unit testing
&lt;/h3&gt;

&lt;p&gt;As one of the core unit testing, I chose a method in "HTMLBuilder.java" which is created to parse text or md file and write a html file, which was created at the beginning of the project. &lt;br&gt;
To create a unit testing, I had to create a mock sample file to compare which contain the content that is expected to be created. &lt;br&gt;
I used a text file for the comparison and used a method "assertTrue". &lt;br&gt;
Since the compared object is a file, it was easier with using FileUtils library and compare the two files. &lt;/p&gt;

&lt;h3&gt;
  
  
  CONTRIBUTING.md
&lt;/h3&gt;

&lt;p&gt;For contributors, I updated the documentation for the testings, explaining how it works and how to use it. &lt;br&gt;
In that case, it would be easier to review and merge codes for me, and easier for the contributors to find out any bugs or improvements from the code. &lt;/p&gt;

&lt;p&gt;You can click &lt;a href="https://github.com/irenejoeunpark/ssgApplication/commit/cb9a626175fc794451de6f73ab8dd8283dc2a019"&gt;here&lt;/a&gt; to see the changes I made through multiple commits. &lt;/p&gt;

</description>
      <category>junit</category>
      <category>testing</category>
      <category>java</category>
      <category>maven</category>
    </item>
    <item>
      <title>Useful tools for contribution</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Fri, 05 Nov 2021 16:53:43 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/useful-tools-for-contribution-2ei0</link>
      <guid>https://dev.to/irenejoeunpark/useful-tools-for-contribution-2ei0</guid>
      <description>&lt;p&gt;As seventh lab of OSD600, I added some useful tools for the future contribution. &lt;br&gt;
Here are some revisions I made&lt;/p&gt;
&lt;h3&gt;
  
  
  IDEA setup
&lt;/h3&gt;

&lt;p&gt;I used IntelliJ for my SSG application. The ide setting were already pushed in the GitHub, I did not have much things to do for the default project setting for the contributors.&lt;/p&gt;
&lt;h3&gt;
  
  
  Added maven to the project
&lt;/h3&gt;

&lt;p&gt;For smoother dependencies/plugin managements for other developers, I decided to add Maven to my project. We do not have to have physical .jar files to use dependencies when we use maven. Maven is a great build tools especially when the project is not only being revised locally. &lt;/p&gt;
&lt;h3&gt;
  
  
  Source code formatter
&lt;/h3&gt;

&lt;p&gt;I used google-java-formatter in my project, and added instruction on how to use it. &lt;br&gt;
It is very simple to use in IntelliJ. It is easily addable in IntelliJ Marketplace, and once its been enabled, user can use the regular reformat shortcut, which is "CTRL+ALT+L". &lt;/p&gt;
&lt;h3&gt;
  
  
  Linter
&lt;/h3&gt;

&lt;p&gt;SpotBug is a tool for spotting some silly mistakes that might cause bug in the future. Through maven, I was able to add spotbug plugin easily, and it is in "pom.xml" of the project. &lt;br&gt;
It is very simple to run spotbug.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mvn spotbugs:gui
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This command above will inspect the code and show you some possible bugs with some UI. &lt;/p&gt;

&lt;h3&gt;
  
  
  CONTRIBUTING.md
&lt;/h3&gt;

&lt;p&gt;I created an &lt;a href="https://github.com/irenejoeunpark/ssgApplication/blob/master/CONTRIBUTING.md"&gt;instruction&lt;/a&gt; for the contributors. &lt;br&gt;
It has step-by-step instructions on what requirements you need, how to install and run the project, what you need to do after fixing issues. &lt;br&gt;
Through Release0.2, I got a chance to contribute in other projects, but it was way easier to contribute in a project that has detailed instructions, and their own standards. &lt;/p&gt;

&lt;p&gt;You can find all of those changes &lt;a href="https://github.com/irenejoeunpark/ssgApplication/commit/5be3d6b654ab8c07448ec571b1802be4c84dd230"&gt;here&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>java</category>
      <category>linter</category>
      <category>formatter</category>
    </item>
    <item>
      <title>[Hacktoberfest 2021] Fourth and the last pull request</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Wed, 03 Nov 2021 15:16:41 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/hacktoberfest-2021-fourth-and-the-last-pull-request-ef2</link>
      <guid>https://dev.to/irenejoeunpark/hacktoberfest-2021-fourth-and-the-last-pull-request-ef2</guid>
      <description>&lt;p&gt;As my last and the fourth contribution in hacktoberfest 2021, I contributed in another issue from meiliesearch-java, which was the first project I contributed in hacktoberfest. &lt;/p&gt;

&lt;p&gt;I was planning to work on another issue, but I faced some environment issues with the project, I had to choose another issue from other project. &lt;/p&gt;

&lt;p&gt;The reason I picked this issue was that I know the sub-setting methods already from previous experience which I worked on creating unit tests for sub-setting methods. I understood the project structure and the standards.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/meilisearch/meilisearch-java/issues/269"&gt;Click here to see the issue&lt;/a&gt;&lt;br&gt;
The issue was to add and update code samples of the sub-setting methods. &lt;/p&gt;

&lt;p&gt;It was my first contribution on documentation. It was also my first experience using .yaml type file. &lt;br&gt;
You can check my pull request &lt;a href="https://github.com/meilisearch/meilisearch-java/pull/274"&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I added some "reset" samples of the sub-setting methods, and updated "update" code samples of the same sub-settings.&lt;/p&gt;

&lt;p&gt;As of this, I completed four pull requests for hacktoberfest 2021. &lt;br&gt;
This was a great experience actually "contributing" in some huge projects by working on small issues. &lt;/p&gt;

</description>
      <category>hacktoberfest</category>
      <category>opensource</category>
      <category>java</category>
    </item>
    <item>
      <title>[Hacktoberfest 2021] Responsive design with css</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Mon, 01 Nov 2021 20:35:22 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/hacktoberfest-2021-responsive-design-with-css-19ii</link>
      <guid>https://dev.to/irenejoeunpark/hacktoberfest-2021-responsive-design-with-css-19ii</guid>
      <description>&lt;p&gt;My third contribution to the hacktoberfest 2021 was fixing the responsive design.&lt;br&gt;
When I saw the word "responsive", it seemed very interested for me because I have not worked on css for a while after second semester of school.&lt;br&gt;
I chose the issue that I could bring up my old memories from few years ago. &lt;br&gt;
&lt;a href="https://github.com/mohitbalwani/Citi-site/issues/1"&gt;https://github.com/mohitbalwani/Citi-site/issues/1&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It is an one-page website that is created with html and css only now, and had some bug with the last section when reducing the window size. &lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--cPxwRFS_--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rrwvbye3tkm4syjsgasi.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--cPxwRFS_--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rrwvbye3tkm4syjsgasi.png" alt="Image description" width="880" height="791"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The update was made with css. I first updated the division of the section as two-column design. &lt;br&gt;
Inside "row 4" division, I added two more divisions for the column designs. And added width as percentages to make those columns align horizontally.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="nc"&gt;.column&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;float&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nb"&gt;left&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nf"&gt;#col1&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="m"&gt;55%&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="nf"&gt;#col2&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;margin&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="m"&gt;0%&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nl"&gt;width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="m"&gt;45%&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After, I wanted to add some specific rules for smaller windows, by using "@media" struct.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;
&lt;span class="k"&gt;@media&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;max-width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="m"&gt;700px&lt;/span&gt;&lt;span class="p"&gt;){&lt;/span&gt;
    &lt;span class="nc"&gt;.row4&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nl"&gt;height&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="m"&gt;70vh&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="nc"&gt;.column&lt;/span&gt; &lt;span class="nt"&gt;h1&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nl"&gt;font-size&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="m"&gt;2rem&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="nc"&gt;.form&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nl"&gt;font-size&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="m"&gt;1.2rem&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="nc"&gt;.column&lt;/span&gt; &lt;span class="nt"&gt;button&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nl"&gt;width&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="m"&gt;22vw&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="nl"&gt;text-align&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;center&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="nc"&gt;.column&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nl"&gt;align-items&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;center&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After the fixes, with the smaller windows, width under 700px it looked like the image below. &lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--nDZ5JYWz--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/6aicl9sn7av3oynmfgos.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--nDZ5JYWz--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/6aicl9sn7av3oynmfgos.png" alt="Image description" width="880" height="585"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Also, I added another media struct for even smaller windows such as phones. &lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--PNtAaZxC--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/27gocsdztqhrpmcz1wvn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--PNtAaZxC--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/27gocsdztqhrpmcz1wvn.png" alt="Image description" width="880" height="579"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This issue had very little description and no Readme.md in the project, and that made me understanding the code little longer. However the owner of the project was very responsive and communicated with me well so that I could move on to solve the issues. &lt;/p&gt;

&lt;p&gt;You can find my pull request on this issue below.&lt;br&gt;
&lt;a href="https://github.com/mohitbalwani/Citi-site/pull/4"&gt;https://github.com/mohitbalwani/Citi-site/pull/4&lt;/a&gt;&lt;/p&gt;

</description>
      <category>css</category>
      <category>opensource</category>
      <category>html</category>
      <category>hacktoberfest</category>
    </item>
    <item>
      <title>[Hacktoberfest 2021] Fixes UI of the application</title>
      <dc:creator>irenejoeunpark</dc:creator>
      <pubDate>Mon, 01 Nov 2021 20:19:53 +0000</pubDate>
      <link>https://dev.to/irenejoeunpark/hacktoberfest-2021-fixes-ui-of-the-application-5d3n</link>
      <guid>https://dev.to/irenejoeunpark/hacktoberfest-2021-fixes-ui-of-the-application-5d3n</guid>
      <description>&lt;p&gt;My second contribution was for a website called "GDSC JGEC Website". &lt;br&gt;
The issue was with some UI of the webpage, which had some bug, and also design that was not enough.&lt;br&gt;
&lt;a href="https://github.com/gdscjgec/gdscjgec.github.io/issues/38#issuecomment-953101856"&gt;https://github.com/gdscjgec/gdscjgec.github.io/issues/38#issuecomment-953101856&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--MwV_KyDZ--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/o2t338tnb2um84fj90bt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--MwV_KyDZ--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/o2t338tnb2um84fj90bt.png" alt="Original Page" width="880" height="479"&gt;&lt;/a&gt;&lt;br&gt;
The original page looked like this. There was a bug with the banner "Upcoming Events" which was not showing properly. &lt;br&gt;
I updated the margin-top from 2% to 5% to show off the whole banner properly. &lt;/p&gt;

&lt;p&gt;For the design of the website, I wanted to make it looks like matching with the website theme. &lt;br&gt;
So I re-used the background image from another page of the application. Also the color, light green did not quite suit with the website theme. I looked at other pages to find some colors that goes with the main theme of the webpage, and re-used those colors to the event card. &lt;br&gt;
Also, font and the box designs was modified to match with other pages. &lt;br&gt;
After the fixes, it looks like below.&lt;br&gt;
&lt;a href="https://github.com/gdscjgec/gdscjgec.github.io/pull/40"&gt;https://github.com/gdscjgec/gdscjgec.github.io/pull/40&lt;/a&gt;&lt;br&gt;
&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--jXpGHJ-a--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/tcuwkdcv2hbeqzlprhz9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--jXpGHJ-a--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/tcuwkdcv2hbeqzlprhz9.png" alt="Image description" width="880" height="484"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>css</category>
      <category>html</category>
      <category>opensource</category>
      <category>hacktoberfest</category>
    </item>
  </channel>
</rss>
