Content on our main website is being constantly added and updated on a term-by-term basis. Having to update this data directly from within the codebase, or the database, would be a hassle. Also, we want executives on the team who don’t work on the website codebase to be able to update the content as well. The CMS solves these issues, making updating data on the website quick and simple for all authorized executives on the team.
- Ensure you have
node v16,yarn v2+andDocker Desktopinstalled. See onboarding docs for more info. 0.1. https://yarnpkg.com/getting-started/migration#step-by-step - Install dependencies with
yarn install - Create a
.envfile, then copy + paste relevant variables from wloop.ca/web-env-vars - Start the backend by running
yarn docker:dev, then open a new terminal and runyarn dev - Launch the frontend in a new terminal with
yarn start:frontend - For more commmands please see
package.jsonunder the "scripts" section.yarn startto start the application. - (Optional): Download React Tools and Redux Devtools to debug components from your browser.
Follow https://docs.google.com/document/d/1dCXT49owNXHkC0MzgUdcb9Do9u-lwnCYmN15ukDl_Q0/edit# for deployment instructions. Please do not share sensitive variables directly; redirect developers to this document instead!
- Unit and integration tests will not work with the default Plug n' Play PnP configuration. To make them work, please add
nodeLinker: node-modulesto your .yarnrc.yml and rerunyarn install, then try running the unit/integration tests. 1.1. Hopefully this will be resolved in the future; currently Mocha doesn't like PnP. 1.2. DO NOT COMMIT YOUR .yarnrc.yml CHANGES!!!
- Full coverage of dynamic content on the main website, so that the majority of updateable content on the site can be updated through the CMS.
- Improve the login/logout functionality logic.