Code Monkey home page Code Monkey logo

i4g-opensource-frontend-project-2022's People

Contributors

belikeoscar avatar blessing-tolani avatar chibuike-19 avatar cisco-a avatar codewithmide avatar cybergeni avatar de-mi-de avatar dprincecoder avatar ekezie-victor avatar frankukay avatar gitosas avatar henryola05 avatar ingressive4good avatar mars-reborn avatar modibboyusuph avatar mudi-igbinoba avatar newtraque avatar nhorah avatar omotayobolu avatar onyelaudochukwuka avatar osilaja78 avatar pragmaticaweds avatar prospiroo avatar sandee004 avatar scottdeev avatar shegun-istaken avatar t-bello7 avatar teenuade avatar toescene avatar zakariyahrobiat avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

i4g-opensource-frontend-project-2022's Issues

Authentication: Phone-number-verification-UI

  • Develop PHONE NUMBER VERIFICATION page UI appropriately
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Add Help and Support Page to Route

The routes listed on the App.jsx page includes the Help and Support page, but the route to /support was not added, so the link doesn't work.

Authentication: Create Account-UI

  • Develop the create account UI appropriately
  • Ensure they are responsive and follow the responsive design on the figma
  • Implement images properly
  • Follow the color guide and the appropriate colors

We need a license!

What docs page is being added or updated?

  • Section: LICENSE

For Adding New Content

What kind of content category is this page (tutorial, how-to, explanation, reference)?

A license for the repository

What are the intended results or takeaways from reading this page?

Have a better understanding of the kind of project we are working on and helps the contributors know their right

For Updating Existing Content

What updates should be made to the page?

No update

Authentication: Email Verification-UI

  • Develop the email verification page UI appropriately
  • Ensure they are responsive and follow the responsive design on the figma
  • Implement images properly
  • Follow the color guide and the appropriate colors

Authentication: Verification Sucessful:UI

  • Develop the verification successful page UI appropriately
  • Ensure they are responsive and follow the responsive design on the figma
  • Implement images properly
  • Follow the color guide and the appropriate colors

Add Redux for state management

There is currently no state management tools for the project and an online shop has quite a lot of state to be managed.
So I'll love to set up either redux-toolkit for the project if assigned to me.

Home-page: Footer design

I discovered the footer design on the home page is not carrying the colours on the style guide.

User-Dashboard: Notification

  • Develop the User Dashboard notification pages UI appropriately
  • The user dashboard notification page contains 1 page and a modal
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Authentication: Login-UI

Develop Login page UI appropriately
Ensure they are responsive and follow the responsive design on the Figma
Implement images properly
Follow the colour guide and the appropriate colours

User-Dashboard: Wishlist(View product on wishlist)

  • Develop the User Dashboard wishlist pages UI appropriately
  • The user dashboard upload product page contains 3 pages ( you should send a pull request for each of the pages)
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

User-Dashboard: Profile

  • Develop the User Dashboard profile pages UI appropriately
  • The user dashboard profile page contains 1 page and a modal
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Set Up CI/CD

setting up CI/CD will make the project easier to review.
as all changes made will be reflected making it easier for maintainers to notice errors as the frontend requires a visual representation.

Authentication: KYC-FORM-UI

  • Develop the KYC PAGE UI appropriately
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Update on Readme.md

There is no link from the Readme file to the contribution.md file thus not providing easier onboarding of participants just from the read me

Authentication: Phone-number-verification-success-UI

  • Develop THE PHONE NUMBER VERIFICATION SUCCESS page UI appropriately
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Authentication: Reset Password-UI

  • Develop the reset password page UI appropriately
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

User-Dashboard: Help and Support

Develop the User Dashboard help and support page UI appropriately
Ensure they are responsive and follow the responsive design on the Figma
Implement images properly
Follow the colour guide and the appropriate colours

Authentication: Forget page Notification UI

new page alert on the Authentication page

Develop the forget password notification page UI appropriately

Ensure they are responsive and follow the responsive design on the Figma

Implement images properly

Follow the color guide and the appropriate colors

A clean template for raising an issue

To make it easy for the maintainers to see what changes has been made to the codebase, a well formatted issue must be raised. Kindly check my PR I just created a format for contributors to follow.

User-Dashboard: Messages

  • Develop the pages of the User-Dashboard message UI appropriately
  • The user dashboard message contains 2 pages ( you should send a pull request for each of the pages)
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Authentication: Forget Password-UI

  • Develop the forget password page UI appropriately
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Navbar and Hero Component of Landing Page

Title

Develop the Navbar and Hero page

Summary

I want to start by developing the Navbar and Hero page and make it fully responsive

Environment

[environment of where the issue occrs; e.g., operating system version, browser version, and so on]

Steps to reproduce

  1. Create components for the sections.
  2. Link them up
  3. Make it responsive

Expected result

A landing page then we can proceed with other pages.

Create a routing structure for the project

Feature Request

Routing structure in frontend

This will Feature to help the contributors better in developing other pages

Create a routing structure in the app.jsx file as so all other contributors developing other pages will just link there routing page using one convention, so some conflicts are avoided.

User-Dashboard: Products (View uploaded products)

  • Develop the User Dashboard view uploaded product pages UI appropriately
  • The user dashboard upload product page contains 4 pages ( you should send a pull request for each of the pages)
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

[CONTRIBUTING GUIDELINE FIX] Request to add the Style guide and Project structure documentation

What docs page needs to be fixed?

Request to add the Style guide and Project structure documentation

  • STYLE GUIDE:
    This section would communicate clearly the style guide followed in the project. Also providing resources for developers to learn about technologies they are not familiar with but used in the project. I suggest the documentation can be written based on this article https://andela.com/insights/structuring-your-react-application-atomic-design-principles/
  • PROJECT STRUCTURE
    This section would define the file structure of the application. The routes and redux configuration. The tools used and conventions followed would be properly discussed here.

What is the problem?

The chaos of developers just adding any code as long as it can be deployed on netlify is causing redundant code and no clear site of the project structure. Having the style guide and project structure documentation would give both developers and maintainers a reference when reviewing code.

What should be changed to fix the problem?

The entire file structure and routing follow the atomic design principle. The CSS design framework to be approved should only be tailwind CSS.

Authentication: Email Verification successfull UI

Develop the Email Verification successfull UIappropriately
Ensure they are responsive and follow the responsive design on the Figma
Implement images properly
Follow the color guide and the appropriate colors

Code of conduct for contributors

A code of conduct is vital for the success of every community. I have listed few rules which can be applied by every contributor on behalf of the community in my PR

Authentication: Reset-password-Success-UI

  • Develop the reset password success page UI appropriately
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

User-Dashboard: Products (Delete uploaded products)

  • Develop the User Dashboard delete uploaded product pages UI appropriately
  • The user dashboard upload product page contains 4 pages ( you should send a pull request for each of the pages)
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

[BUG] report - Fix routing issue

Prior Issues

Are there any existing issues or PRs that relate to this problem? If so, link them here.
#2 #65 #3 #5 #6 #7 #8

What is the current behavior?

The pages are not linked to the correct routes

User: Dashboard home - UI

  • Develop the User Dashboard pages UI appropriately
  • The user dashboard home contains 5 pages ( you should send a pull request for each of the pages)
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

contribution guideline

Every open source project must have a detailed step by step guideline that all contributors must adhere to.
This will help in in many ways as follows:

  • enables a clean codebase
  • help contributors work in sync
  • helps contributors keep the end goal in mind etc.

User-Dashboard: Product (Add new Product)

  • Develop the User Dashboard add new product pages UI appropriately
  • The user dashboard upload product page contains 4 pages ( you should send a pull request for each of the pages)
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Improved UX in the User's dashboard (Edit and View profile page)

The Mobile first approach of this screen has scroll issue as mobile users are required to scroll back up after filling the form in order to submit their progress and also based on laws of similarity the button might mislead unaware users to attempt account deletion while trying to submit out of Reflex

User-Dashboard: Wishlist(Select & Delete product on wishlist)

Develop the User Dashboard wishlist pages UI appropriately
The user dashboard upload product page contains 2 pages ( you should send a pull request for each of the pages)
Ensure they are responsive and follow the responsive design on the Figma
Implement images properly
Follow the colour guide and the appropriate colours

Authentication: Forget-Password-Success-UI

  • Develop the forget password success page UI appropriately
  • Ensure they are responsive and follow the responsive design on the Figma
  • Implement images properly
  • Follow the colour guide and the appropriate colours

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.