Since we are using React as our framework, most of our codes reside inside src folder. Inside the folder, there are files that are used for setting ups the project. Here, we want to note that index.css is imported to most of our templates. Routes.js is powered by react-router-dom library to support routing between pages.
Inside src, there are three folders that we heavily put effort into.
src/components: Implementations of base components can be found here, for example, the navigation bar, the progress bar, image placeholder, measurement canvas, and etc. These components will be combined later in pages. Basically, after we have been through the process of lo-fi prototyping, we jump into this in the early stages.src/pages: After we finished implementing base components, we start to arrange things into pages. Most of the interaction supports are implemented here. These pages are also routed between each other.src/reducers: We decide to store a copy of the database of one user when the session is established. This way, we do not have to frequently update the database which it might reduce the speed performance via saving since we do support drafting feature (when a user adds a note). Our solution is to use the reducers, which will store states and will be accessible across all pages.
Our prototype is now live at link.
This is our additional section for those who wants to try out our website.
⚠️ Safari's private mode does not share cache between tabs which result in unexpected behaviour. We recommend using Google Chrome. Or if really necessary use it in normal mode.
Since our system focuses on the producers' side (those who make handmade cloth products), we are not supporting the interfaces for the customers' side. For example, to have a discussion in real scenario, there might be a feature that supports live video call and screen sharing as well. In this case, we assume that the video call and the screen sharing are already settled up.
There are totally two steps that require an action from the customer's side: creating a new order and receiving the measurement.
To begin the entire process, you have to reset and restart the entire process by triggering a button.
- Go to sew-you-later.web.app/test/new-orders
- Click "Reset" button to restart the system
- Click "Go to New Orders" to come back to the main pages and view the incoming order
Since the producers need the measurements from the customers, we automate this process so that the interaction feels more real.
After the producer has sent a measurement form, you have to go back to the "Current Orders" page. In a breath, you should see an update by noticing the notification.
- Go to Current Orders page to receive the measurements
redux-state-sync requires to pass payloads for actions in reducers to be JSON.stringify-able. Do not pass functions as payloads
Install all the dependencies running the following command in the project directory.
npm install
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify