Created a simplified dashboard for viewing, editing, and managing campaigns by using create-react-app. I used React Bootstrap as a means of being able to build out components in a timely manner and Context API to avoid prop-drilling.
To get inspiration, I referenced the Postscript dashboard and expanded upon the layout with some revisions. From there, I planned out the routes to properly navigate the application to display campaigns (both sent and open), as well as a means to create new campaigns and edit them.
✔️ I can view a list of my Preview (unsent) campaigns and their target segments.
✔️ I can view a list of my Sent campaigns and their performance stats (amount sent, click through rates).
✔️ I can create a new campaign or edit a Preview campaign.
✔️ There is a live preview of my campaign as I edit it.
✔️ I can add/edit a media link in my campaign to attach a picture or GIF to the message.
✔️ My created campaign can use tags to replace parts of the message with variables.
✔️ Tags required for this demo are {shop_link}, {first_name}, and {shop_name}
✔️ Select a target segment for campaign
✔️ You may add support for additional tags (custom links, personalized offers, etc.)!
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.