Closed geekyme closed 4 years ago
@geekyme Did you mean to check in the screenshot?
@matrinox thanks for the catch. I've removed it
Sure let me wait a couple of days for @pqvst to give his thoughts.
Thanks guys! Let's try it and see how. I'll give details over slack later.
Description
This adds configurations required for NetlifyCMS to work. I limit the scope of CMS edits to just the faq pages. Our new workflow:
See screenshot of the flow
The CMS should be available at the
https://taiwangoldcard-cms.netlify.app/admin
endpoint, and CMS users are added using netlify identity service. All requested reviewers have already been invited to the instance.Closes #46
Motivation
As described in https://github.com/taiwangoldcard/website/issues/46, we want to:
Deployment
There is no change to existing deployment flow for https://taiwangoldcard.com.
I've setup a netlify instance in parallel, which will detect changes on master and build its copy for the CMS. So
https://taiwangoldcard-cms.netlify.app/admin
is our secret url to access the CMS.I don't think accessing https://taiwangoldcard.com/admin will work according to this. But if it happens to work then I can get rid of my netlify instance.
Limitations / Risks
Netlify Identify service only allows up to 5 users per website. Therefore we can only allow 5 users into the CMS -
We can have shared account for content editors to work around this.