You can find the deployed project at https://www.cloudstands.com/
Cloud Stands is a the best way to promote organization and communication between vendors and small markets. Our mission is to streamline the on-boarding process of joining a market.
- Google and Facebook login platforms
- Market Owners can create their marketplace
- Market Owners are able to customize their markets
- Vendors are able to search for markets by city
- Familiarity
- Popularity
- Works with our styling framework
- Single source of state with redux store
- Error state handling/Validation
- Works with redux well
- Keeps track of form data
- Theming
- Prebuilt components that are externally consistent with apps that they are familiar with
- fancy buttons/radios
- Conponent based styling
- Familiar with it
- Plays nice with material with some tweaks
Back end built using:
- Don't have to convert from sqlite3 for production
- Ability to work with Passport and Postgis
- familiarity
- trigram processing for fuzzy search that works with postgres
- It's an extension in postgres and it allows you to use special operators & functions within the calls
- It's Simple and fast to implement for setup & individual execution.
- Sending emails to users to assure them that their actions went into the system.
- Well known , well documented & trusted
- Easy to setup and offers a lot of useful analytics
- Used for validation
Passport oAuth supporting Google , Facebook & Square
Square (not finished)
| Image type | Source / Creator | License |
|---|---|---|
| icon | Sketch app Sources | Sketch app Sources |
| icon | Material UI | Material UI Icons |
| icon | Font Awesome | Font Awesome |
We used Jest on the frontend to test that our major components were displaying properly.
Using yarn: From root run yarn and run yarn start to get this up and running on your system.
Using npm: From root run npm install and run npm start to locally get started with npm.
Alternatively we are live at http://cloudstands.com
* build - creates a build of the application
* start - starts the production server after a build is created
* test - runs jest tests
* test-auto - runs tests in **tests** directory
* eject - copy the configuration files and dependencies into the project so you have full control over them
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.
Please note we have a code of conduct. Please follow it in all your interactions with the project.
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.
We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.
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.
Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.
- Ensure any install or build dependencies are removed before the end of the layer when doing a build.
- Update the README.md with details of changes to the interface, including new plist variables, exposed ports, useful file locations and container parameters.
- 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 two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
These contribution guidelines have been adapted from this good-Contributing.md-template.
See Backend Documentation for details on the backend of our project.