This is a proof-of-concept tool to help solve a domain-specific workflow problem for direct printing on substrates (phone cases, t-shirts, cups, and mugs).
This is really just a stripped down Photoshop, with quality-of-life (QoL) features to directly assist with this workflow. It is intended to specifically excel when embedded into e-commerce CMS to allow for user-orchestrated customization of product designs. For all self orchestrated workflows (i.e. bulk printing via Photoshop), this might not be the most effective tool.
At the moment, there is no backend set up (see issues tab). Frontend data is persisted via local storage, and most of the file state is manipulated in local state, not saved anywhere.
Image manipulation is done via React Konva, which is great for single canvas manipulations, but not great when you need a canvas on a canvas. As a food for thought, it may be better to rewrite some of this functionality and reduce dependencies. But from a prototyping perspective, I wanted to see if it was possible to do all the image manipulation I need from just this library (seems like no).
Also, only one image can be uploaded, but it would significantly increase usability if multiple images can be uploaded. Nice QoL features for the admin would be bleed guides, for example.
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.