Skip to content

waterloop/waterloop-cms

Folders and files

NameName
Last commit message
Last commit date

Latest commit

8c89681 · Mar 16, 2023
May 9, 2022
Jan 3, 2021
Dec 16, 2022
May 22, 2021
Mar 16, 2023
Dec 16, 2022
Nov 28, 2022
Nov 28, 2022
May 7, 2022
Dec 16, 2022
May 7, 2022
May 7, 2022
Dec 16, 2022
May 7, 2022
Dec 16, 2022
Jan 28, 2023
May 7, 2022
Dec 16, 2022
Nov 28, 2022
Dec 16, 2022
Dec 16, 2022

Repository files navigation

Content Management System (CMS)

Why do we need a Content Management System?

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.

Setup

  1. Ensure you have node v16, yarn v2+ and Docker Desktop installed. See onboarding docs for more info. 0.1. https://yarnpkg.com/getting-started/migration#step-by-step
  2. Install dependencies with yarn install
  3. Create a .env file, then copy + paste relevant variables from wloop.ca/web-env-vars
  4. Start the backend by running yarn docker:dev, then open a new terminal and run yarn dev
  5. Launch the frontend in a new terminal with yarn start:frontend
  6. For more commmands please see package.json under the "scripts" section. yarn start to start the application.
  7. (Optional): Download React Tools and Redux Devtools to debug components from your browser.

ISSUES:

  1. Unit and integration tests will not work with the default Plug n' Play PnP configuration. To make them work, please add nodeLinker: node-modules to your .yarnrc.yml and rerun yarn 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!!!

💻 Technologies

🔨 Some features to implement

  • 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.