Issue

When we log in as a farmer, we get the option to add a new item from the shop page. However, the layout is shabby and does not use the DaisyUI components. This issue would include the following:

• Usage of DaisyUI Components for the Input Fields, File Picker and Buttons
• Making requests to the backend to add items, with required fields.

Additional Details

1. Set up the project as mentioned, it is preferable to use the Local Server. Check This.
2. Now that your local server is started, it's time to get started with the front end. Check This.
3. Sign up as Farmer and go to the shop and try to add an item.
4. You are now on the AddItem Page.

Backend APIs to be used

• FreshNest/backend/routes/list.js

  Line 46 in ce8d1ea

  * @param {Object} req.body - The request body.

• FreshNest/backend/models/millet_item.js

  Line 40 in ce8d1ea

  function validateMilletItem(item) {

Issue

Currently, we re-fetch all the items when we change the filter. However, we sort them in the front end itself. Instead, sort the list of items as we already store them to render the items.

Files to be changed

fronted/react/src/pages/shop/presentation/Shop.jsx

This is just provided for simplicity of navigation and reference. If required more files can be affected according to needs.

Remove the last star present in Readme.md.

Currently

🙏 Support

This project needs a ⭐️ from you. Don't forget to leave a star ⭐️

Change to

🙏 Support

This project needs a ⭐️ from you. Don't forget to leave a star.

Feature

Add pull-to-refresh on the Shop Page, so that the user can reload/refreshes the items as he wishes and the new data is shown.

Add full stop in last line of README.md

Issue

The spacing between fields doesn't seem equal, especially if we look above the phone label.

How to Reproduce?

1. Go through our Contributing Guidelines and setup your project. Set the environment to the remote development server.
2. Go to your localhost, and log in using the below credentials:

email: [email protected] password: password

3. Go to the user page, and from settings click on Edit Profile. You have now successfully opened the dialog.

Issue

We recently updated our documentation folder from doc to docs in #14. This invalidates the path of some links provided in Readme.md. We require you to update the URL to the valid path.

(PS: The Contribute to AgroMillets link is invalid)

Issue 🙉

On the user profile page, we provide the user with the option to change the background pattern. Currently, we are storing it in the component itself, however, we now want to save it to the local device in the AppState Object, which is globally accessible throughout the application. The logic for storing the AppState object to LocalStorage is already in place, you just need to add a field of pattern to it.

References 🦅

• AppState: https://github.com/AmanNegi/FreshNest/blob/main/frontend/react/src/data/AppState.js
• Profile Page: https://github.com/AmanNegi/FreshNest/blob/dad33b825a067c16b2067181f6d54d594ba78de4/frontend/react/src/pages/Profile/presentation/Profile.jsx#L17C25-L17C25

Feel free to comment and ask if you have any queries.

Change app version to 0.0.1.

Here's the file to edit:
https://github.com/AmanNegi/AgroMillets/blob/main/frontend/flutter/agro_millets/pubspec.yaml#L19

Issue

Currently the app lacks sign up page, add a page where user can signup.

Reference

• https://daisyui.com/docs/install/

In the main directory there is a folder by the name doc rename it to docs.

Issue Overview:

The current documentation for FreshNest gives the impression that we are a brand competing in the eCommerce market. However, our actual purpose is quite different. FreshNest is a full-stack e-commerce application created to serve as a perfect codebase for learning and practice, rather than as a commercial enterprise. This issue aims to address the mismatch between the current documentation and our true purpose.

Scope:

This issue will focus on updating the project documentation to ensure that it accurately reflects FreshNest's role as a full-stack e-commerce application designed primarily for educational purposes. We want to eliminate any potential confusion regarding our project's objectives.

Proposed Changes:

• Revise the project's README to emphasize our educational mission.
• Add a subsection that highlights FreshNest's role as a codebase for new developers.
• Clarify that FreshNest is not intended for commercial use but is meant for learning and practice.
• Additionally, add a section that addresses the question: "Why build it if it is not actively used in the real world?"
• Provide links to relevant resources or documentation for new contributors to get started.

Expected Impact:

By addressing this issue, we aim to align our documentation with FreshNest's true purpose, reducing any potential misconceptions about our project's goals. This will create a more suitable learning environment for those interested in using FreshNest for skill development.

Issue 🙈

We recently renamed our application from AgroMillets to FreshNest, however, our title bar still shows AgroMillets. Could you update this behavior and replace the name wherever we use the old name?

Screenshots 📱

Important Files 🗃

• https://github.com/AmanNegi/FreshNest/blob/main/frontend/react/index.html
• https://github.com/AmanNegi/FreshNest/blob/main/frontend/react/README.md

Other than these feel free to search *AgroMillets globally throughout the project.

Issue

It can be hard to determine types in JavaScript, so following the trend in nowadays market we are thinking of not shifting to TypeScript. An alternative to access features like TypeScript is to use JSDoc. Thus, it would be nice is JSDoc could be added to files.

If no cart count is present in localStorage make a call to the backend and set the count.

Currently we show Contributors in Readme.md it would be better to remove it as it is shown by GitHub automatically in the side bar towards right.

Issue:

Currently, we do have a CONTRIBUTING.md however it does not specify in detail how to set up the React Part of the application and run it in the local system. It would be nice to have, an extensive guide that could help new contributors.

• https://github.com/AmanNegi/FreshNest/blob/dev-react/docs/CONTRIBUTING.md
• https://github.com/AmanNegi/FreshNest/tree/main/frontend/react#readme

Our gallery and Our features container hover effect and they don't redirect to some another page. Can I remove the hover effect and add some gradient effect for the same @AmanNegi

Issue

The user should be able to see the number of items in the Cart, simply as a popup on the icon itself.

Reference

I noticed that when you view the page on a large screen the cards in the "Our User Review" section are not being centered, so this affects the layout of the page.

Please let me work on this issue to participate in HacktoberFest.

Suggestions

Convert React Frontend Code to Typescript, which might be a major change. But it is required for: #101

Issue:

When we open the app, it directly opens without any splash screen. It would be nice to have a splash screen with the application's logo on a white background(because currently we only support light mode).

Issue

Currently, the Contributing guidelines are outdated and do not provide a proper process to setup the project. It would be great if a proper step by step contribution guide could be created.

• We could perhaps break the contribution guidelines setup into 3 different files one for React, another for Node and lastly for Flutter.
• For now we should focus on Backend (node) and React.

Feel free to message to learn more about the steps that need to be involved.

The current Shop page fetches data from the server every time a user selects a filter, resulting in unnecessary API calls and slower performance. To optimize performance and reduce server load, we should transition to client-side filtering.

Proposed Solution:

1. Fetching all necessary data from the server on the initial page load.
2. Implementing client-side filtering to instantly update displayed products when users select filter options.
3. Offering an option for users to refresh data from the server when needed.

Implementing client-side filtering will greatly enhance Shop page performance, creating a more efficient and user-friendly experience

Issue

Can not dismiss keyboard in login/signup pages once opened.

Possible Solution

Cover the entire login/signup pages with GestureDetector and using FocusScope remove focus from the text fields.

Here's a blog as reference: https://flutterigniter.com/dismiss-keyboard-form-lose-focus/

Feature:

When we open a product detail page, we get a cropped image of the product. We should provide a feature where the user can hold on to the image to view it in its original aspect ratio.

Product Detail Page

If the user clicks and holds on the image, we can either show the image on a separate page in fullscreen or simply show it as an overlay. Feel free to discuss which behavior you plan to implement before getting started.

We can add loading to the Login button to indicate that a request is being processed and also disable any actions to prevent multiple requests from being created.

Hi!!

I would like to work on the README.md of this project to make it more appealing by adding badges, emojis, restructuring etc

I would like to be assigned if approved!

Issue

Currently, we show the Password field as a normal field, it would be nice to have an IconButton towards the end, to keep it hidden(obscure) or visible.

Possible Solutions

We currently, use our own CustomTextField to create TextField. Similarly, create a widget PasswordTextField which can be used to hide and display the text.

• Creating a separate widget is preferred because it will be used in two pages Login as well as SignUp.

Issue Description:

Objective:

• Propose a new logo design for FreshNest to replace the current Canva-generated logo.
• Create a visual identity that aligns with the app and website's color swatches and overall theme.

Scope of Work:

1. Logo Design:

• Develop a new logo design that represents the core values and functionality of FreshNest.
• The logo should be visually appealing and memorable.

2. Color Swatches:

• Ensure that the new logo adheres to the existing color scheme used in the app and website.
• Maintain consistency in branding.

3. Visual Identity:

• Create a comprehensive visual identity for FreshNest.
• Include guidelines for fonts, typography, imagery, and design elements.
• Convey the brand's personality and values through the visual identity.

Deliverables:

• A new logo design for FreshNest.
• A set of color swatches that match the app and website's theme.
• Detailed guidelines for the visual identity, including fonts, typography, imagery, and design elements.

Benefits:

• The new logo will help FreshNest create a more distinct and memorable brand image in the market.
• The visual identity guidelines will ensure consistent branding across all marketing materials and communications, strengthening brand recognition and reputation.

Currently, we are missing a CODE_OF_CONDUCT.md file in our repository. If you are new to open source and don't know about the code of conduct you may check this.

Helpful References:

• https://github.com/AppFlowy-IO/AppFlowy/blob/main/CODE_OF_CONDUCT.md
• https://github.com/flutter/flutter/blob/master/CODE_OF_CONDUCT.md

You can basically find it in every open source project, which allows contributors to contribute.

Modification Required

We have now deployed our website. We need to add it to the documentation so that end users can access our platform.

Resources

Website: https://agro-millets.netlify.app/
App: Mentioned under Releases

Currently, we use a generic documentation template in frontend/react/README.md. It would be better if we mentioned real-world documentation that would involve the following:

• Forking and Cloning the project.
• Installing Nodejs.
• Scripts that can be used to run the app (Can be found in fontend/react/agro-millets/package.json.

We have identified the need to enhance the error handling mechanism in our authentication system. Additionally, we need to implement required fields for authentication to ensure the security and usability of our application.

Error Handling Enhancement:

Currently, our application does not provide adequate error feedback to users during authentication. When authentication fails, users are not informed about the specific issue, which can lead to confusion and frustration.

Proposed Changes for Error Handling:

Implement clear and informative error messages for different authentication failure scenarios.
Log errors on the server for debugging and monitoring purposes.
Improve the user interface to display error messages prominently and guide users on how to resolve authentication issues.

Required Fields for Authentication:

To enhance the security of our authentication system, we need to ensure that certain fields are mandatory during the registration and login processes. This will help prevent incomplete or inaccurate user profiles and improve the overall user experience.

Issue

Currently, we get an error while searching cause, we are using the wrong env variable use the appropriate API_URL and it should work as expected.

It dosent check the text to get the right email and password.

I think currently the text "Explore out products" is written on the image itself that's the reason the text is not responsive.
If we cast text over the image that could solve the issue.

I'm interested in contributing, let me know if I should start.

While the items are loading, the page looks empty. It would be nice if a shimmer layout would be displayed to the user.

On 4K screens, the Sign Up and Login pages exhibit design issues:

1. Page Stretching:
   The content on these pages extends too far horizontally, causing user experience problems.

2. Logo Alignment:
   The Sign Up page logo is misaligned with other elements, impacting the design.

In the text under the Live Preview section, check alternatives for displaying Preview links. Which should at least ensure that the text is readable.

Issue

The layout of shop items gets skewed on the Shop Item Page. Use appropriate TailwindCSS to ensure the page looks great on mobile devices as well.

Files to be changed

fronted/react/src/pages/shop/presentation/ItemDetail.jsx

This is just provided for simplicity of navigation and reference. If required more files can be affected according to needs.

Screenshots