Giter Club home page Giter Club logo

little-shop-bulk's Introduction

Little Esty Shop

logo

Project Description

"Little Esty Shop" is a mid-mod group project where students are tasked with building a fictitious e-commerce platform. The project aims to create a robust web application that allows merchants and admins to efficiently manage inventory and fulfill customer invoices.


๐Ÿ”ง Tools Used ๐Ÿ”ง

Rails 7.0.5 Ruby 3.2.2 ActiveRecord
SimpleCov VS Code Capybara
Github Render RSpec
HTML SQL Pry

Over View

The main features of "Little Esty Shop" include:

  • Inventory Management: Merchants can add, edit, and disable products, ensuring they have control over their store's inventory.

  • Invoice Management: Admins can add, enable and disable, and update merchants. They can also see all invoices, and update invoice statuses.

  • API Integration: The application utilizes a public API to fetch external data, enhancing the user experience with up-to-date information.

  • Deployment on Render: The project requires students to deploy the application on the Render platform, showcasing their ability to make the application accessible online.


๐Ÿ’ช Work complete

  1. Database Design In this project, we have carefully designed and implemented the database structure to efficiently store and manage data. Leveraging what we learned in class, we ensured data integrity, and optimal performance.

  2. MVC (Model-View-Controller) We adopted the MVC architectural pattern to organize our application code. The Model represents the data logic, the View handles the presentation logic, and the Controller acts as the intermediary, managing user requests and coordinating data flow between the Model and View. This separation of concerns enhances code maintainability, promotes teamwork among developers, and allows for easier future enhancements.

  3. Advanced Routing To provide a seamless user experience and enable complex interactions within our application, we implemented advanced routing techniques. Our routing system efficiently handles incoming requests and maps them to the appropriate controllers and actions, allowing for dynamic content generation and customization.

  4. Active Record We used the ORM Active Record to interact with the database. Active Record enables us to perform database operations using Ruby objects, abstracting away complex SQL queries. This simplifies data manipulation and database access, reducing development time and potential errors.

  5. API Consumption We integrated API consumption capabilities into our application, enabling interaction with Unsplash. By seamlessly consuming APIs, we enrich our application, and enhance user experience.

  6. POROs (Plain Old Ruby Objects) We utilized POROs to encapsulate and manage API consumption logic and data manipulation tasks that do not require database interactions. By keeping these operations outside the database layer, we enhance code clarity and maintainability.

  7. Deployment on Render For seamless deployment and high availability, we chose Render as our platform of choice. Render's user-friendly interface, automated scaling, and monitoring features enable us to deliver a reliable and scalable solution to our end-users. With Render, we ensure a smooth user experience and rapid response times.


๐Ÿ—๏ธ Next Steps and Potential Refactors

Although we have successfully implemented the project's core functionality, there are several areas that can be further refined and improved to enhance the application's overall robustness and maintainability. Here are some potential next steps and refactors we could explore if given more time:

  1. Enhanced Testing with FactoryBot: Implementing FactoryBot for streamlined testing and fixture management. By defining factories for our test data, we can create more reliable and maintainable test cases, leading to better test coverage.

  2. Consistent Utilization of Helper Methods: Refactor and expand the use of helper methods throughout the codebase. Utilizing helpers consistently can lead to cleaner, more readable code and promote DRY principles.

  3. Partial Rendering for Forms: Employ partials to modularize and simplify form rendering. By using partials, we can avoid code duplication and enhance the maintainability of our view templates.


Contributors

๐Ÿ‘จ Ethan Black: Github, LinkedIn

๐Ÿ‘ฉ Zanna Fitch: Github, LinkedIn

๐Ÿ‘ฉ Jorja Fleming: Github, LinkedIn

๐Ÿ‘จ Daniel Gallagher: Github, LinkedIn


๐Ÿ’ Acknowledgments ๐Ÿซถ

We express our gratitude to our instructors, teaching assistants, and cohort-mates for their guidance and support throughout the development of this project.

little-shop-bulk's People

Contributors

ethanrossblack avatar daniel-gallagher92 avatar jorjaf avatar z-fitch avatar cjsim89 avatar mikedao avatar

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.