Skip to main content

CMS Access for Marketing

Marketing users can manage blog posts at:

https://docs.bookcicle.com/admin/

The CMS uses GitHub OAuth. Users must have access to the bookcicle/docs repository before they can create or edit blog content.

Access Requirements​

Each marketing user needs:

  • A GitHub account.
  • Repository access to bookcicle/docs.
  • Permission to commit to the main branch.

The CMS writes blog content directly to main. That is intentional for marketing publishing: approved CMS edits should go live without waiting on an engineering pull request.

First Login​

  1. Open https://docs.bookcicle.com/admin/.
  2. Select the GitHub login option.
  3. Approve the Bookcicle GitHub OAuth app.
  4. Confirm the CMS loads the Blog collection.

If GitHub shows an authorization error, confirm the user has access to the bookcicle/docs repository and that the OAuth app callback URL is:

https://cms-auth.docs.bookcicle.com/callback

Creating a Blog Post​

  1. Open the Blog collection.
  2. Create a new post.
  3. Fill in the title, slug, author, tags, and body.
  4. Use lowercase hyphenated slugs, for example how-to-plan-a-book-launch.
  5. Save the post.
  6. Publish when ready.

Published CMS changes create commits on main. The docs production deploy workflow detects CMS-only blog changes and deploys them to production automatically.

Use the Blog Writing Template for front matter examples, author IDs, tag examples, and a copy-ready Markdown body structure.

Editing Existing Posts​

  1. Open the Blog collection.
  2. Search for the post by title.
  3. Make the content edits.
  4. Save and publish.

Avoid changing a post slug after publication unless redirects or search impact have been reviewed.

Images and Uploads​

Upload blog images through the CMS media picker. Media is stored in static/uploads and served from:

https://docs.bookcicle.com/uploads/

Use descriptive filenames with lowercase words and hyphens.

Publishing Expectations​

CMS publishing is for blog content and uploaded media only. Engineering changes, theme changes, workflow changes, and docs structure changes should still go through a pull request.

After publishing, allow a few minutes for GitHub Actions to deploy and CloudFront to invalidate. Check the live post on https://docs.bookcicle.com/blog/.

Troubleshooting​

  • Not Found or blank CMS: confirm the user is opening /admin/ on docs.bookcicle.com.
  • GitHub authorization fails: confirm repository access and OAuth app settings.
  • Content saves but does not appear live: check the GitHub Actions run for the latest main commit.
  • Images do not render: confirm the uploaded file exists under static/uploads and the Markdown path starts with /uploads/.

Escalate to engineering if a publish creates a broken page, the CMS cannot authenticate, or a production deploy fails.