Web platform for connecting the technological needs of front line mission groups with solution providers from churches, like-minded universities, and other mission minded organizations
This PR addresses issue #46 . It requires users to login or create an account to access the create-project page. We should open a new issue for "attaching" project submissions to a login account. We probably need to actually display the User details in the navbar instead of simply a logout button, but I think I want to make that a separate issue.
What kind of change does this PR introduce?
Uses Auth0 for login gating the /create-project page.
Does this PR introduce a breaking change?
This change removes the NetlifyCMS admin panel. The more I think about it, the more convinced I am that we need to "move" any content in markdown files in the repo over to Strapi. Two CMS tools in a single webapp is overkill.
What needs to be documented once your changes are merged?
Create new Issues:
Display profile/avatar in the navbar (make logout a dropdown)
This PR addresses issue #46 . It requires users to login or create an account to access the create-project page. We should open a new issue for "attaching" project submissions to a login account. We probably need to actually display the User details in the navbar instead of simply a logout button, but I think I want to make that a separate issue.
This work is based on this blog: https://auth0.com/blog/securing-gatsby-with-auth0/
What kind of change does this PR introduce? Uses Auth0 for login gating the /create-project page.
Does this PR introduce a breaking change? This change removes the NetlifyCMS admin panel. The more I think about it, the more convinced I am that we need to "move" any content in markdown files in the repo over to Strapi. Two CMS tools in a single webapp is overkill.
What needs to be documented once your changes are merged? Create new Issues: