↓Skip to main content
Resources for the Modern Web Resources for the Modern Web
  1. All Posts/

bowliciousbowtique

eCommerce CSS

Bowlicious Bowtique (Front-end)

Production: https://bowliciousbowtique.vercel.app/
Staging: https://bowliciousbowtique.vercel.app/

Developers

Matthew Palmer
This is a repo for the official front end for the Bowlicious Bowtique website.
Maintained by MRP Technologies.

About

This project is a faux E-commerce website that turned out to be my final project at Flatiron School. The purposes was to learn more about how React and the Redux library work together.

Objectives

  • Learn more about React and Redux
  • Incorporate RESTful Routing
  • Set communications between React (front-end) and Ruby on Rails (back-end API)

Challenges encountered

  • Redux was the most challenging to understand for this project. It creates a store and maintains all information at the top level of the application. Combating this gap in knowledge involved much trial and error in order to understand how to connect each component connected to the Redux store.

Key Features

  • RESTful Routing
  • Back-end communication (Ruby on Rails)

Tech Stack

  • React.js
  • Redux.js
  • Node.js
  • JavaScript
  • CSS
  • HTML

Dependencies

Dependency
URL

redux
Link

redux-thunk
Link

react-redux
Link

react-router-dom
Link

TailwindCSS
Link

Bootstrap
Link

Back-end Documentation

Click here to access the back-end repo for this project

Getting started

To get the site running locally:

  • Clone this repo
  • Run npm install to ensure the dependencies are installed
  • Run npm start to run the application in a production environment

Note: You may find trouble using this project if you don’t have the back-end running locally on your machine.

Scripts

  • npm run dev – Runs the development environment on your system
  • npm start – Runs the production environment on your system

Testing Documentation

There is currently no testing on this application.

Making Contributions

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Issue/Bug Request

If you are having an issue with the existing project code, please submit a bug report under the following guidelines:
-Check first to see if your issue has already been reported.
-Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
-Create a live example of the problem.
-Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.

Feature Requests

I would love to hear from you about new features which would improve this app and further the aims of my project. Please provide as much detail and information as possible to show me why you think your new feature should be implemented.

Pull Requests

If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.
Pull Request Guidelines

  • Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  • Ensure that your code conforms to our existing code conventions and test coverage.
  • Include the relevant issue number, if applicable.
  • You may merge the Pull Request in once you have the sign-off of the developer(s).


↑