You can find the deployed project at Social Media Strategy.
Jason Long | Jess Wolff | Jose Rivera | Matthew Bedard | Tyler Gilchrist |
---|---|---|---|---|
|
|
|
|
|
Social media managers / Small Business owners don't know how to most effectively engage with their audience.
Our mission is to create the most efficient way to create social posts that get the attention of your followers. To making planning, drafting, and creating social content an easy and enjoyable task.
- Clean and modern drag-and-drop interface
- Suggestive scheduling
React
- Supports reusable components
- Ease of deployment and maintenance
Redux
- Integrates well with React
- State management capabilities match that of application
Material-UI
- Ease of component styling
Styled Components
- Ease of component styling
- Provides easier interaction with React-Beautiful DnD
React-Beautiful-DnD
- Controls and styles drag-and-drop functionality
Back end built using:
- Node.js
- Express.js
- Postgres
Provided by our backend to handle account creation and social media network authorizations.
In order for the app to function correctly, the user must set up their own environment variables. There should be a .env file containing the following:
* REACT_APP_API_URL - this variable points to the back end
🚫Document what you used for testing and why
- Fork and Clone Repository
- run NPM install to download dependencies
* build - creates a build of the application
* start - starts the production server after a build is created
* test - 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.