⌘ the internet is hard.
← THE OPEN WORKBENCH

WEB INFRASTRUCTURE / GITHUB

Give your CMS the missing authentication bridge.

GitHub OAuth endpoints for Decap CMS sites hosted on Cloudflare Pages.

THE PROJECT, IN PRACTICE

What you can do with it.

01

Cloudflare Functions endpoints

Run the OAuth bridge alongside your Pages project.

02

Decap CMS configuration

Start from the included admin configuration and point it at your own site.

03

A focused integration

Connect the CMS, GitHub OAuth application, and deployment environment without a separate full application server.

FROM IDEA TO USE

How it works.

  1. 01

    Register OAuth

    Create the GitHub OAuth application for your site.

  2. 02

    Configure secrets

    Store the client ID and secret in your hosting environment.

  3. 03

    Deploy and sign in

    Add the Functions and admin files, configure the CMS, and test the login flow.

The authentication path
Decap CMS → GitHub OAuth
                ↕
     Cloudflare Functions
                ↕
       Your site repository

Use your own OAuth application and deployment configuration. Never put client secrets in browser code.

TAKE IT FOR A SPIN

Start here.

Follow the repository setup guide for OAuth registration, Cloudflare configuration, and the CMS admin files.

STATUS & REQUIREMENTS

Based on community Netlify CMS OAuth work and adapted to Cloudflare Functions. A starter configuration still needs site-specific setup.