-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMS updating documentation! #79
Comments
luckily we're all very good at typos and there are generally ways to undo most things that you might mess up within the CMS, so -- worry not! i'd like to get this round of edits (we have a couple of things in progress) done soon, and have @avawillis and @anaqb take the lead on updating the pages, with @joshyam-k and @zolli22 backing them up, where "soon" could be edits done via git/R this week, changes made in CMS next week or thereabouts (D@R pages polished by 2021/11/22?) |
also we always want our github repo to be fully up to date, so changes should always happen in this repo before they happen in the CMS! |
file path additions: |
internal file paths: |
Updating the CMS webpages (aka literally editing the reed website) is a bit scary at first (i always feel like too much power is being given to someone who is prone to making typos), but we have some great documentation that makes it a lot easier!
The main resource is this document
If it's your first time making changes or creating a new page I wouldn't worry about updating the links (see last section on doc) since its pretty confusing and something that ingrid and I can do!
Finally Leila made a great video found in our shared drive walking you through some of the things that the above document describes, so I'd definitely recommend watching it before you set out to actually edit the CMS webpages.
The text was updated successfully, but these errors were encountered: