GithubHelp home page GithubHelp logo

purnima143 / pluto-ui Goto Github PK

View Code? Open in Web Editor NEW
28.0 2.0 56.0 49.44 MB

Pluto UI is a comprehensive React UI component library designed for ecommerce websites. It provides a wide range of reusable and customizable UI elements to enhance the user experience of your online store.

License: MIT License

JavaScript 78.79% SCSS 21.21%
component components-library reactjs rollup ui frontend html javascript npm scss ux

pluto-ui's Introduction

Pluto UI ๐Ÿš€

Pluto UI is a comprehensive React UI component library designed specifically for ecommerce websites. Its purpose is to enhance the user experience of online stores by providing a wide range of reusable and customizable UI elements. Desktop - 12



GitHub repo size GitHub repo file count

GitHub issues GitHub pull requests GitHub GitHub forks GitHub Repo stars

Technologies


Also included these tech stacks:

  • Storybook: A development environment and UI component explorer for building UI components in isolation.
  • PropTypes: A library for type checking React component props.

Color Code

Must follow this color code when creating a component.To ensure consistency and visual coherence, Pluto UI follows a specific color code. When creating new components, it is important to adhere to this color code for a unified look and feel throughout the UI library. Group 3(1)

Components

Here's a comprehensive list of common components should be in the library:

  • Navigation Components:

    • Navigation bar
    • Mega menu
    • Breadcrumbs
    • Sidebar
  • Product Display Components:

    • Product card
    • Product list/grid view
    • Product carousel/slider
    • Product details page
  • Shopping Cart Components:

    • Cart summary
    • Cart items list
    • Cart sidebar
    • Cart checkout process
  • Checkout Components:

    • Address form
    • Payment options
    • Order summary
    • Shipping options
    • Order confirmation
  • User Account Components:

    • Sign-in/sign-up form
    • User profile
    • Order history
    • Wishlist
  • Search Components:

    • Search bar
    • Sorting dropdown
    • Filter options
  • Promotion Components:

    • Banner
    • Sale/Discount badges
    • Featured products
  • Review and Rating Components:

    • Rating system
    • Customer reviews
  • Messaging Components:

    • Notifications
    • Toast messages
    • Alerts
  • Forms and Inputs:

    • Text fields
    • Dropdowns
    • Radio buttons
    • Checkboxes
    • Date pickers
    • Range
  • Miscellaneous Components:

    • Pagination
    • Loading spinners
    • Modal/pop-up windows
    • Tooltips
    • Progress bars
    • Avatars

๐Ÿš€ Getting Started

Prerequisites

Before you begin, ensure that you have Node.js and npm installed on your machine.

Installation

To install Pluto UI, clone this repository to your local machine:

git clone https://github.com/your-username/pluto-ui.git

Then, navigate to the cloned repository and install the necessary dependencies:

cd pluto-ui
npm install

Run Storybook:

npm run storybook

Open your browser and visit http://localhost:6006 to view the Storybook interface.

Usage

With Storybook up and running, you can interact with the individual components, explore their variations, and test their behavior in different scenarios directly in your browser. This allows you to see how the components look and function in isolation and helps you integrate them seamlessly into your own ecommerce website.

Feel free to customize and enhance this markdown file to match your project's specific needs and requirements.

Guidelines for Writing SCSS

When writing SCSS code for our project, please adhere to the following guidelines:

  • Classname Convention: Use the following naming convention for SCSS class names:
    scss

    .pluto--<element-name> {
      /* Styles for the element */
    }

For example, if you are creating a button component, the SCSS class should be named .pluto--button. This convention helps ensure consistency and avoids naming conflicts.

  • Modular Approach: Keep the SCSS styles modular and component-based. Each component should have its own SCSS file, organizing the styles specific to that component.

  • Reusability: Aim for reusable SCSS styles to promote consistency and reduce duplication. Extract common styles into reusable mixins or variables.

  • Maintainability: Keep the SCSS code clean, readable, and well-organized. Use indentation, comments, and appropriate naming conventions to enhance code maintainability.

  • Responsiveness: Consider responsive design principles and write SCSS styles that adapt to different screen sizes and devices.

  • BEM Methodology: Consider utilizing the BEM (Block Element Modifier) methodology for naming classes and structuring the SCSS code. This methodology helps create maintainable and scalable styles.

Please ensure that the SCSS code follows these guidelines to maintain a consistent and organized codebase for our UI library.

Feel free to modify and expand upon these guidelines to fit the specific requirements of your project.

Contributing

We welcome contributions from everyone. Here are some guidelines to get started:

  1. Fork the repository and create your branch: git checkout -b your-branch-name. For example, if you are working on the Navbar component, you can create a branch named navbar.
  2. Make your changes and commit them: git commit -m 'Add some feature'.
  3. Push to your forked repository: git push origin your-branch-name.
  4. Open a pull request to the dev branch and mention which component you have worked on.

For example, if you have made changes to the Navbar component, you can mention it in the pull request title or description: "Feature: Updated Navbar component".

Resources

  • React Documentation: React is a popular JavaScript library for building user interfaces. The React documentation provides comprehensive information and guides on React concepts, components, and best practices.
  • Storybook Documentation: Storybook is a powerful tool for developing UI components in isolation. Refer to the documentation to learn how to set up and use Storybook for Pluto UI development.
  • SCSS Guide: SCSS (Sass) is a popular CSS preprocessor that offers additional features and flexibility. The SCSS Guide provides detailed information on how to write SCSS code effectively.

Please utilize these resources to enhance your understanding and contribute effectively to the project.

pluto-ui's People

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

pluto-ui's Issues

Design: Create design for Review and Rating component

Issue summary

There is currently no design for the Review and Rating component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the Review and Rating components using the colors of the project which is already given in the README.

Tasks

  • Rating system
  • Customer reviews

Before working on the issue, dm me or @AdityaSingh-02 and @purnima143 to be added to the Figma file and please, strictly follow the styleguide.

PR Rules

  • Create the PR against the dev branch not the master branch
  • Link the issue your PR is for by saying Fixes #PRNumber
  • Add a description of what your PR is about
  • Add screenshots or video of the working implementation of your PR

Frontend: Build the Sidebar sub component for both Light and Dark mode

Issue Summary

The design for Sidebar as part of the Navbar component has being completed and now it needs to be built using our chosen tech stacks.

Figma link

The design for the Sidebar can be found here. Please make sure what you build follows the design.

Suggested fix

  • Build the Sidebar component following the design in the Figma file.
  • Make sure your codes are maintainable and legible.
  • After coding the component using React and scss, create storybook for the component.
  • Test it out on your end and make sure it's working properly.

Coding Rules

  • Let your codes look neat and readable
  • No unnecessary spacing and always leave one empty line after each code block
  • Separate each word with a hyphen - in your scss classes, ids.

PR Rules

  • Link the issue your PR is for by saying Fixes #PRNumber
  • Add a description of what your PR is about
  • Add screenshots or video of the working implementation of your PR

Design: Create design for Promotion components

Issue summary

There is currently no design for the promotion component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the promotion component using the colors of the project which is already given in the README.

Tasks

  • Banner
  • Sale/Discount badges
  • Featured products

Before working on the issue, dm me or @AdityaSingh-02 and @purnima143 to be added to the Figma file and please, strictly follow the styleguide.

PR Rules

  • Create the PR against the dev branch not the master branch
  • Link the issue your PR is for by saying Fixes #PRNumber
  • Add a description of what your PR is about
  • Add screenshots or video of the working implementation of your PR

Design: Create designs for the Navigation component

Issue summary

There is currently no design for the navigation component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the navigation component using the colors of the project which is already given in the README.

Tasks

  • Navigation bar
  • Mega menu
  • Breadcrumbs
  • Sidebar

NB: There is no font family chosen yet, so you would have to pick one yourself

After you start working on the issue, i.e designing, drop a link to the figma page here and give me alongside @AdityaSingh-02 and @purnima143 edit access

Product Card

PRODUCT CARD

  • Product card has 2 parts : 1) Product's image 2) Product's description

Product's description

  • Product's description contains mainly of : 1) Product title 2) Product Description paragraph 3) Add to Card button of accent color (CTA) 4)Price

DARK MODE

Product-card-dark

LIGHT MODE

Product-card-light

Things that can be added on to Product cards

[ ] Badges

Design: Create design for Form and Inputs components

Issue summary

There is currently no design for the Form and Inputs component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the Form and Input components using the colors of the project which is already given in the README.

Tasks

  • Text fields
  • Dropdowns
  • Radio buttons
  • Checkboxes
  • Date pickers
  • Range

Before working on the issue, dm me or @AdityaSingh-02 and @purnima143 to be added to the Figma file and please, strictly follow the styleguide.

PR Rules

  • Create the PR against the dev branch not the master branch
  • Link the issue your PR is for by saying Fixes #PRNumber
  • Add a description of what your PR is about
  • Add screenshots or video of the working implementation of your PR

Add table of content

I can add a table of content as mentioned below to readme.md for easy navigation, can you assign me this issue to me under GSSOC'23?
tabofcontent

Add Auto Comment Feature to Improve Collaboration

Issue Description:
As an active contributor to your open-source project, I believe that implementing an auto-comment feature would greatly enhance collaboration and communication within the project. This feature would automatically generate comments in response to specific events, such as when an issue is opened, a pull request is created, an issue is assigned, or an issue is unassigned.

Feature Details:

  • When an issue is opened, the auto-comment should greet the author and provide a brief acknowledgement and request for additional context.
  • When a pull request is opened, the auto-comment should greet the author, express gratitude, and remind them to follow the project's contributing guidelines.
  • When an issue is closed, the auto-comment should thank the author for their contribution and encourage further engagement.
  • When an issue is assigned to someone, the auto-comment should notify the assignee and encourage them to start working on it.
  • When an issue is unassigned from someone, the auto-comment should notify the assignee about the change and suggest reassignment if they are offline.

Benefits:

  • Improved communication and engagement with contributors.
  • Provides clear instructions and acknowledgements for various events.
  • Enhances collaboration by setting expectations and providing reminders.
  • Reduces manual effort by automating comment generation.

Acceptance Criteria:

  • The auto-comment feature should be implemented using the "wow-actions/auto-comment" GitHub Action.
  • Comments should be appropriately customized for each event, mentioning relevant parties and providing the necessary information.
  • The auto-comment workflow should trigger on the following events: issues opened, pull requests opened, issues closed, issues assigned, and issues unassigned.
  • The feature should be added to the project's existing GitHub Actions workflow file.

Additional Context:
Feel free to ask any questions or seek clarification regarding the auto-comment feature. I'm excited about contributing to your project and believe this enhancement will greatly benefit its community.

Home page component

Hi @purnima143
I want to create a home page component for this project and I'll set the basic Structure of the project so that other people will be able to start working on other components as well
Please assign me this task

Design: Create designs for Checkout components

Issue summary

There is currently no design for the checkout component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the checkout component using the colors of the project which is already given in the README.

Tasks

  • Address form
  • Payment options
  • Order summary
  • Shipping options
  • Order confirmation

Before working on the issue, dm me or @AdityaSingh-02 and @purnima143 to be added to the Figma file.

adding tech stack badges and shields in readme.

i would like to add tech stack badges and shields in readme . it makes the readme look more pretty and ggive better ingo about the technologies used.
please assign me this issue as gssoc contribution
example:
image

Frontend: Build the MegaMenu sub component for both Light and Dark mode

Issue Summary

The design for the MegaMenu as part of the Navbar component has being completed and now it needs to be built using our chosen tech stacks.

Figma link

The design for the MegaMenu can be found here. Please make sure what you build follows the design.

Suggested fix

  • Build the MegaMenu component following the design in the Figma file.
  • Make sure your codes are maintainable and legible.
  • After coding the component using React and scss, create storybook for the component.
  • Test it out on your end and make sure it's working properly.

Coding Rules

  • Let your codes look neat and readable
  • No unnecessary spacing and always leave one empty line after each code block
  • Separate each word with a hyphen - in your scss classes, ids.

PR Rules

  • Link the issue your PR is for by saying Fixes #PRNumber
  • Add a description of what your PR is about
  • Add screenshots or video of the working implementation of your PR

Design Product card

I'm interested to design a Product card for Pluto UI which has different variants and States

Variants

  • On Sale (Offer)
  • Out of Stock
  • New Arrival

States

  • Default
  • Hovered
  • Focused

Options

  • Various Options to customise the card elements

Readme update

Screenshot 2023-05-21 160801
Adding this badges to readme makes it more attractive assign me this issue under GSSOC'23

Frontend: Create Shopping cart component

Issue Summary

The design for the shopping cart component is amost cdone and now it needs to be built using our chosen tech stacks.

Suggested fix

  • Build the shopping cart component following the design in the Figma file.
  • Make sure your codes are maintainable and legible.
  • After coding the component using React and scss, create storybook for the component.

Adding table of contents and improving the Readme.md file

Hey! Since there are so many components as part of this project, I would like to add a table of contents in the readme.md file which will make navigation convenient and make the readme file look more engaging. Please assign this to me as part of GGSOC'23.

Adding Table of Contents and improving README.md

Hey! Since there are so many components as part of this project, I would like to add a table of contents in README.md file which will make navigation convenient and make the readme file look more engaging.

Please assign this to me as part of GGSOC'23.

Design: Create design for Search components

Issue summary

There is currently no design for the search component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the search component using the colors of the project which is already given in the README.

Tasks

  • Search bar
  • Sorting dropdown
  • Filter options

Before working on the issue, dm me or @AdityaSingh-02 and @purnima143 to be added to the Figma file and please, strictly follow the styleguide.

Improving the readme file

I would like to improve the readme file of this project making it engaging for the users and make it more expressive.

Frontend: Build Product card Component for both light and dark modes

Issue Summary

The design for Product card as part of the Product component has been completed and now it needs to be built using our chosen tech stacks. The Product card has to be inside the Product component story

Figma link

The design for the Product card can be found here. Please make sure what you build follows the design.

Suggested fix

  • Build the Product card component following the design in the Figma file.
  • Make sure your codes are maintainable and legible.
  • After coding the component using React and scss, create storybook for the component.
  • Test it out on your end and make sure it's working properly.

Coding Rules

  • Let your codes look neat and readable
  • No unnecessary spacing and always leave one empty line after each code block
  • Separate each word with a hyphen - in your scss classes, ids.

PR Rules

  • Link the issue your PR is for by saying Fixes #PRNumber
  • Add a description of what your PR is about
  • Add screenshots or video of the working implementation of your PR

Preview

Light mode



Dark mode


Update the readme file

I would like to update the README file as it appears that the provided Git clone URL is not functioning correctly. Additionally, I would like to make changes to lines such as "cd pluto-ui". Please assign me this issue under GSSOC 2023.

Design: Create designs for the Product component

Issue summary

There is currently no design for the Product component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the Product component using the colors of the project which are already given on the README.

Tasks

  • Product card
  • Product list/grid view
  • Product carousel/slider
  • Product details page

After you start working on the issue, i.e designing, drop a link to the figma page here and give me alongside @AdityaSingh-02 and @purnima143 edit access

Design: Create designs for the Shopping cart component

Issue summary

There is currently no design for the shopping cart component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the shopping cart component using the colors of the project which is already given in the README.

Tasks

  • Cart summary
  • Cart items list
  • Cart sidebar
  • Cart checkout process

After you start working on the issue, i.e designing, drop a link to the figma page here and give me alongside @AdityaSingh-02 and @purnima143 edit access

Missing Issue Template in Repository

Description:

I noticed that the repository does not have an issue template. Having an issue template can greatly improve the clarity and consistency of issue reports, making it easier for contributors and maintainers to understand and address the problems or feature requests effectively.

add readme badges

i want to add readme badges. Please assign this issue to me under GSSOC
badges

[Design] Implement spinner component

  • There is no similar existing issue
  • This is a part of GSSOC23

Description

Implementing the spinner component according to PlutoUI Design language as it is not implemented yet. It will be implemented in different colours and sizes.

Making a design system for Pluto UI and implement them

I want to work on design system for this project .

We will be covering all the major thing required for E-Commerce UI libraries .

Goal of the UI lib : An E-Commerce website can be made just by our components alone . No additional coding should be required .

Needs : 1) Documented & Well designed components
2) Components independent of each other
3) Consistent design

Design: Create design for User Account component

Issue summary

There is currently no design for the user account component and in order for the project to have a uniform styleguide, a design has to be created for each of the components.

Proposed fix

Create a design for the user account component using the colors of the project which is already given in the README.

Tasks

  • Sign-in/sign-up form
  • User profile
  • Order history
  • Wishlist

Before working on the issue, dm me or @AdityaSingh-02 and @purnima143 to be added to the Figma file and please, strictly follow the styleguide.

Adding Dockerfile

A Dockerfile provides a standardized and efficient way to package, distribute, and run your project, simplifying development, deployment, and maintenance processes.

Frontend: Build the Breadcrumbs sub component for both Light and Dark mode

Issue Summary

The design for Breadcrumbbs as part of the Navbar component has being completed and now it needs to be built using our chosen tech stacks.

Figma link

The design for the Sidebar can be found here. Please make sure what you build follows the design.

Suggested fix

  • Build the Breadcrumbs sub component following the design in the Figma file.
  • Make sure your codes are maintainable and legible.
  • After coding the component using React and scss, create storybook for the component.
  • Test it out on your end and make sure it's working properly.

Coding Rules

  • Let your codes look neat and readable
  • No unnecessary spacing and always leave one empty line after each code block
  • Separate each word with a hyphen - in your scss classes, ids.

PR Rules

  • Link the issue your PR is for by saying Fixes #PRNumber
  • Add a description of what your PR is about
  • Add screenshots or video of the working implementation of your PR

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.