Skip to content

Using a Website

Scribe CMS stores your content. To display that content on a website, you need a website that has been set up to read from your Scribe account using the Scribe SDK.

This page explains how the two pieces fit together and what to ask a developer for if you need help.

  1. You write and publish content in Scribe CMS.
  2. A website built with the Scribe SDK reads your content directly from your account.
  3. Visitors to your website see your published articles — grouped and navigable, with an RSS feed and a sitemap.

Your content stays in your account at all times. The website reads it when someone visits — there’s no export, copy-paste, or sync required.

If a developer is building or connecting a website to your Scribe account, they’ll need two things:

WhatExampleWhere to find it
Your Bluesky handlealice.bsky.socialYour Bluesky profile — the username with the @
Your site’s domain (as entered in Scribe CMS)alice.example.comYour site settings in Scribe CMS

That’s it. The developer uses these to configure the SDK — no passwords or tokens are shared.

If your blog lives at a path on your domain (e.g. alice.example.com/blog/) rather than at the root, you need to set a URL prefix in your site settings.

In this example, set the URL prefix to blog. If your content is at the root of the domain, leave the URL prefix empty.

Any website built with the Scribe SDK can expose an RSS feed and XML sitemap automatically. Ask your developer to enable these — they’re a one-file addition to the site. Once enabled:

  • The RSS feed lets readers subscribe to your content in any feed reader
  • The sitemap helps search engines find and index your articles

The Scribe SDK works with any web framework. If a developer is building a new site from scratch to display your content, point them to the Developer documentation — specifically the Quickstart and Framework Guides.