jpedroschmitz / backy

BackOffice for small stores

Hey, I'm João Pedro! 👋

I'm a Front-End Engineer from Brazil 🇧🇷 working remotely for Hygraph. Lately, I'm making a lot of cool applications with React, Next.js, and Remix. I also love sharing knowledge and contributing to Open Source projects.

If you would like to discuss these things, you can send me an email or DM me on Twitter (the best way to talk with me). I'm looking forward to connecting with you :)

backy's Issues

v2 features

Changes proposed

On v2, the software will need to maintain and register customers (create, read, update and delete).

Each customer must have a:

• name
• cpf
• street
• house number
• district
• city
• zip
• state

Additional context

This issue is related to #1 and depends on the implementation of #2.

[Umbrella] Backy development

Backy is a BackOffice for small stores. It will have features such as customer registration and control of orders and products.

The development will be divided into 4 phases. Each phase will include new features or new enhancements to the software.

• Version 1 #6
• Version 2 #7
• Version 3 #8
• Version 3.1 #9

ps: all version features and enhancements must be incremental and cumulative

v3.1 - new fields and enhancements

Changes proposed

On v3.1, we will include one field for products and customers. Also, will have some enhancements for orders page.

Products:

• include price field

Customers:

• include base discount field

Orders:

• when the users enter an order, the software must get the product price
• when the users enter an order, the software must get the base discount for that client

Additional context

This issue is related to #1 and depends on the implementation of #2, #3 and #4.

Add more information about the project on the Readme

The following sections could be added:

• Getting Started;
• Contributing;
• Authors;
• License;

v1 features

Changes proposed

On v1, the software will need to maintain and register products (create, read, update and delete).

Each product must have a:

• name
• description
• maker

Additional context

This issue is related to #1.

v3 features

Changes proposed

On v3, the software will need to maintain and register orders (create, read, update and delete).

Each order must have a:

• product (can have more than one)
• customer
• quantity
• price
• discount
• total

Additional context

This issue is related to #1 and depends on the implementation of #2 and #3.