Getting things ready to Publish EOS Icons in the Marketplace

Hello everyone, fifth week with Google Summer of Code had come to an end with EOS Design Systems.

What did I do this week?

The most important goal of the week was to find out how to publish the plugins in the Figma Community and Adobe Xd Marketplace after the modified code had been merged. To do this, it was necessary to create a new official EOS Design Systems Id in order to publish a plugin in both the marketplaces. In order to publish a version from there, I asked my mentors and my organization's admin to provide me an official account with the required authentication enabled and organization details filled.

The relevant data and cover art that we had to include in our plugin follow next. Throughout this week, I created a variety of cover arts for the Figma and Adobe Xd plugins while maintaining the varying dimensions for each plugin art. To make sure everything is going smoothly, I maintained frequent communication with my mentors. The Figma cover image underwent a few changes as a result of discussions with the mentors.

The Adobe Xd plugin had a different method of publishing than the Figma Plugin, which only requires our manifest.json file and automatically retrieves the folder. First, we must zip the entire folder and then convert it to a .xdx format. I made a test folder with a .xdx extension, and when I clicked on it, the plugin was installed in my Adobe Xd. However, it didn't work and didn't install when I tried it with our plugin folder. The main.js and manifest.json files should be located in the same directory, I discovered after reading through the various documentations on Adobe Xd resources. However, the manifest.json file and main.js were being built in the dist folder, which is located inside the main repo folder. Finally, the plugin was successfully installed when I attempted to create the dist(distribution) folder with the.xdx extension. We are now prepared to release both Plugins once the cover art and the description have been finalized.

What is coming up next?

The publishing phase of the Plugins will continue the next week. I'll release them to the market once everything is ready.

Did I get stuck anywhere?

Yes, there were a few moments when I got stuck, such as when I needed an id to publish the plugins or needed advice on the made cover arts, but all thanks to my mentors Cynthia and Kartikay for being available and giving me the feedback and information I needed.

Final Testing & Updation before Publishing

Hello everyone, fourth week with Google Summer of Code had come to an end with EOS Design Systems.

What did I do this week?

The primary goal for this week was to do the necessary code cleanups & updations before releasing the plugins. The very first task of the week was to include documentation on how a user might trigger a release when the semantic releases for both plugins were completed. I started making changes to the codebase as soon as the documentation was updated.

In the EOS Icons Figma Plugin Repository, I made a few little UI adjustments. A new manifest Id was created because the used manifest Id had expired.

Some significant modifications were made in the EOS Icons Adobe Xd Plugin repository. The manual search panel required the user to first look for the icon and then click on search to look for the icon. I added a handleOnChange and Debounce hook to automate the search panel. Additionally, I resolved the problem where the plugins would hang and stop loading icons anytime a user tried to search for All icons. This was taking place as a result of the plugin's build size, which is approximately 17.5Mb and requires more time to load. There were also a few minor UI fixes that I made as discussed with my mentor.

What is coming up next?

After the updated changes gets reviewed and merged, I will start to figure out the publishing of both the plugins in their respective marketplace. 

Did I get stuck anywhere? 

I did not get stuck anywhere at this week.

Figuring out GH006 (The Protected Branch Issue)

Hello everyone, third week with Google Summer of Code had come to an end with EOS Design Systems.

What did I do this week?

This week was focused on resolving the conflict which was not letting semantic release a version for the EOS Icons Adobe Xd Plugin Repository. Whenever I was trying to push a commit with a commit message that will let semantic trigger a release, it throws the error of remote: error: GH006: Protected branch update failed for refs/heads/main. I had to conduct a thorough internet search to find a solution and discovered that the branch protection rules were the cause of the problem. While both the Figma and Adobe Xd repositories follow the same branch protection rules, semantic released a version in the Figma repository without encountering any issues while throwing an exception in the Adobe Xd repository. I tried every online fix I could find, but it didn't work. I came up with the idea of deleting the branch protection rules and then setting them up once again so that they can operate. I tried it, and it worked; the failing semantic actions were now successful, and semantic prompted a release for the Adobe Xd repository. This marked the completion of adding Semantic Releases to both the Plugin repositories and we are now at Version 1.0.0 for both the plugin repositories. 

What is coming up next?

For the upcoming week, I will be updating the codebase for both the Plugin repositories, some minor UI fixes and automating the search panel in the Adobe Xd repository using separate debounce hook. After this, I can start with publishing of the plugins in the marketplace.

Did I get stuck anywhere? 

Yes, I was stuck with the GH006 error, but my mentor Kartikay sir was always in touch with me and helped me gain access to repository settings and testing of repositories actions so that I can figure out this whole issue.

Enhancing GitHub workflows with Semantic Release

Hello everyone, second week with Google Summer of Code had come to an end with EOS Design Systems.

What did I do this week?

This week was primarily focused on updating workflows to implement Semantic Releases. semantic-release automates the whole package release workflow including: determining the next version number, generating the release notes, and publishing the package. semantic-release uses the commit messages to determine the consumer impact of changes in the codebase. For this, I had to alter the repository's package file and Github workflow file, which will aid in triggering a certain release depending on the nature of the commit message.

This week, I created up workflows for the Adobe Xd and Figma repositories of the EOS Icons Plugins. The workflow was pushed to the main repositories and the workflow successfully passed the semantic-release workflow for EOS Icons Figma Plugin. Branch protection issue GH006 is affecting the EOS Icons Adobe Xd repository, and I'll fix it as soon as I can.

What is coming up next?

For the upcoming week, I will be resolving the branch conflicts occurring in EOS Icons Adobe Xd repository which are creating issues while running workflows and preventing semantic, release a version. Also, I will be updating the documentation in both the repositories on how to release a version based on a commit message.

Did I get stuck anywhere? 

The workflows failed at @semantic-release/commit-analyser when the branch was being pushed to the main. But I must give special thanks to my mentors, Kartikey Bhutani and Vinayak Sharma, who were really helpful to me during this.

A New Journey Begins

Hello, my name is Anshuman Dhiman, a Pre-Final Year Information Technology student from India. I will be polishing & adding new features to EOS Icons Figma & Adobe XD Plugins and also work on EOS Icons Website during Google Summer of Code 2022. I will be working with EOS Design Systems on the project : EOS icons Figma and Adobe XD plugins and website.

What did I do this week?

With the guidance of the mentors in the community bonding period, I started setting up the project repositories. Figma and Adobe XD plugins are two distinct plugins that will be developed independently and concurrently. The goal of the first week was to test the codebase and update the documentation for both plugins (EOS Icons Figma Plugin and EOS Icons Adobe XD Plugin). This includes updating the documentation describing (how to run the plugin?) and providing relevant test commands before submitting a Pull Request to maintain cleaner code. Additionally, I am also testing the functionality of the plugins and the codebase locally to check if they are properly implemented and require any changes.

What is coming up next?

For the upcoming week, I will be continuing to test the codebases and finalize both the plugins so they can be scheduled for publishing on the Figma & Adobe XD communities. In order to keep accurate release versions in the projects, I will also be adding semantic releases to both the plugin's repositories. This could involve making improvements to the Github workflows and packages files so that they can generate and maintain a release version based on the type of commit message.

Did I get stuck anywhere?

While testing the codebase, I ran into trouble making changes that involved making a separate file for a hook. My mentor Abhirup sir helped me understand this, and I am now working on implementing the change.