# Projects ideas

{% hint style="warning" %}
**Good to know:** we're updating this page soon!
{% endhint %}

### Project idea 1: User Story - frontend and UX \[up to 2 people] - long project \[350 hours].

User story \[[https://userstory.eosdesignsystem.com/](https://userstory.eosdesignsystem.com/)] is in need of improvements on different areas and for this project we want to, ideally, find 2 people to work together as a team since the scope may be quite large.&#x20;

Scope:

* UX/UI improvements in Desktop and Mobile devices.
* Work on making the application a Progressive Web App \[[https://web.dev/pwa-checklist/](https://web.dev/pwa-checklist/)].
* Polish existing features and increase test coverage.
* Fix all open issues both in Github and in User Story.
* Work on improving the authentication on chrome which still has issues with cleaning cookies and signing out a user after the credentials have expired.

Repository: [https://github.com/EOS-uiux-Solutions/user-story](https://github.com/EOS-uiux-Solutions/user-story)

### Project idea 2: User Story - documentation and landing page - long project \[350 hours].

User story hasn't been launched yet and since we believe that with this last round of GSoC we will be ready to do so, we need to prepare 2 main elements to be ready to promote the product.

Scope:

* We need to create a landing page that showcases all highlights of User Story. The Founder and PM (Cynthia) and project lead (Aditya) will help you identify the main features of User Story, but we want you to explore the product yourself and create a document that tells us what gets your attention the most as a user of User Story (this should be part of your research for your application).
* In addition to the landing page, we want to have technical documentation written for how a team/developer can launch User Story for their organization or product. This will mean that you will need to communicate with the team of project 1 and run User Story yourself locally as well as try it in popular services such as Heroku, AWS, or Azure, so that you provide both feedback to the developers in project 1 if you find issues deploying the service, and so that you provide true guidelines to our consumers to successfully deploy User Story. We don't want you to re-invent the wheel in this step and we prefer that you use Gitbook (the same service used for this page)

Repository: [https://github.com/EOS-uiux-Solutions/user-story](https://github.com/EOS-uiux-Solutions/user-story)

### Project idea 3: EOS Icons - Typescript, Next.js, and guides - short project \[175 hours]

EOS icons \[[https://eos-icons.com/](https://eos-icons.com/)] is our star project. It has been online for over 4 years now and in the last GSoC, we launched new libraries for React.js and Vue.js to expand support to more frameworks.&#x20;

Scope:

* We have documentation for how to use the React and Vue libraries, how to integrate them into your websites, however, what we are missing is the simplicity of a copy/paste code when you find an icon that you like which takes the component of the currently selected icon so that it makes it easier for someone to use icons in React and Vue.\
  Currently, we only have the basic HTML element in the UI. We need to improve the UX so that users can alternate to React/Vue/HTML code snippets, which means that you will need to have skills with Figma or Adobe XD to create wireframes before even thinking about writing code. This is the current interface that we need to expand support for React and Vue:

![](https://4186131728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuZSnpDa3gFGMFFqwoHYT%2Fuploads%2FyyaUy9kddj47JJHdj7ya%2Fimage.png?alt=media\&token=31d3f31a-0a20-4c85-b396-39222a4fe8ea)

* As the web world moves to Typescript, eos icons is laying behind and we want to make the move to migrate the entire front-end to Typescript.&#x20;
* SPA (single page applications) are not efficient when it comes to SEO since they dynamically render content and this is not compatible with search engines crawlers. We want to migrate to Next.js so that we can serve all pages statically, but we do not want server-side rendering as eos-icons.com is served with Github pages and does not have a backend available. Your project lead (Kartikay) will provide you guidance in regards to Next.js and the expectations.

### Project idea 4: EOS icons - Figma and Adobe XD plugins and website - short project \[175 hours]

Last year we also created 2 new plugins to help Figma and Adobe XD users use eos icons flexibly from the applications to embed and find icons easily. These two plugins need to yet be published in the official stores of Figma and Adobe and are in need of some improvements.&#x20;

Scope:

* Improvements for the two applications:&#x20;
  * Support for multiple sizes.
  * Support for color changes.
  * Support for exporting as PNG instead of SVG.
  * Add a link back to [eos-icons.com](http://eos-icons.com/) (UI/UX improvement).
* Once the improvements are ready, we require that you proceed to publish the puglins in their official stores. All contact information should be provided by us. Get in touch with your project lead (Kartikay) and PM (Cynthia) when you find yourself at this stage.&#x20;
* In addition, we also ask you that you add a minimal UI improvement in the eos-icons.com page to help users learn that they can request new icons via User Story. This will require that you do some UI and UX work.

