What you’re connecting to
The content manager is the editing screen at /admin on your site. It’s where you change words and photos without touching code. Signing in with GitHub is how it knows you’re you.
Why GitHub
Your site’s pages are files stored on GitHub, with a history of every change. When you save an edit, the content manager writes it there under your name. That is why GitHub asks for access to repositories: saving is writing to one.
What the permission covers
GitHub’s permission screen is broader than what the content manager uses. It lists access to every repository your account can reach, because GitHub offers no narrower choice for this kind of sign-in. The content manager on your site reads and writes one repository only: the one that holds your site.
What stays private
- Your password. You type it on github.com and nowhere else. Neither your site nor I ever see it.
- The key GitHub issues once you approve. It goes straight to your browser and stays there. The sign-in service keeps no copy and stores nothing about you.
Removing it
You can disconnect at any time. Open your authorized apps on GitHub (Settings, then Applications, then Authorized OAuth Apps) and revoke Joybringr Content Manager. Your site and everything you’ve saved stay exactly as they are. Sign in again whenever you want to edit.
Questions
Ask before you approve anything you’re unsure of. Reach me the way you usually do, or message me on LinkedIn.