Publishing to Your Own Site

Nolorem publishes to WordPress, Ghost, and Webflow through their own APIs. If your site is none of those, it does not need to be. Declare it as your own site, and Nolorem becomes a first-class publishing destination for it, the same as any adapter.

This article walks the day-one setup, start to finish. It assumes nothing about your site's stack, only that it can make an HTTP request.

What this arrangement actually is

Read this first, because it decides how you build the other end.

Nolorem never calls your site. There is no webhook, no push, no callback. Your site calls Nolorem, on whatever schedule you choose. The Public Content API is a read-only feed: your site polls it, and everything else, including how often, is your decision.

Nolorem tells you when your own setup looks wrong. If your site is declared but nothing is fetching it, or something is fetching it and getting nothing back, that shows up on the Publishing settings page rather than staying invisible. The section below on checking that your site is actually fetching is not an afterthought; it exists because a feed that answers with nothing, silently, forever, is exactly the failure this arrangement is built to catch.

Step 1: Enter your site's address

Open Publishing in your blog's settings and enter your website's address. Click Find my platform.

Nolorem checks whether your address runs on WordPress or Ghost. If it does, you are offered that platform's own connection form instead of the steps below, since a real adapter already exists for it.

If nothing is recognized, that is a normal and expected result, not an error. Most bespoke sites, and every site built on a platform Nolorem does not have an adapter for, land here. You are shown a short message confirming this and moved straight into declaring your own site, with the address you just typed already filled in.

Step 2: Confirm the address and the post path pattern

Two fields describe your site: the site address (confirmed from what you entered) and the post path pattern, the shape of a single post's URL on your site, for example /{slug} or /blog/{slug}.

Nolorem tries to read one real article URL from your site and propose a pattern from it. When it finds one, the pattern field shows a Proposed badge with a note on which page it was read from; check it against a URL you know is correct, then confirm. When it does not find one, the field starts empty, and you fill it in yourself.

This field is required, and it is never guessed silently. An earlier version of this arrangement filled in a default pattern automatically when a customer left the field untouched, and that default was wrong often enough to send readers to a 404. Nolorem now insists on a real answer, from detection or from you, before it composes a single link to a post on your site.

Save. Your site is now declared as a destination.

Step 3: Create a Content API key

Publishing to your own site needs an active Content API key so your site has something to authenticate with. Go to Settings, API Keys and create one, scoped to this blog. See Public Content API for the full walkthrough of key scopes, authentication, and every endpoint the feed exposes; this article does not repeat it.

The Content API is available on every paid plan, including a trial. An active subscription is what unlocks it, not a specific tier.

Step 4: Point your site at the feed

Your site fetches GET /api/v1/posts with the key as a bearer token, and paginates from there. Exactly how to consume it, including cheap polling with If-None-Match and copying images to your own storage rather than hotlinking Nolorem's, is worked through end to end in a runnable, dependency free Node script: sync.mjs (with its README). Download it and use it as a starting point.

Step 5: Check that your site is actually fetching

Back on the Publishing settings page, the section under your declared site shows whether requests are actually arriving:

• No requests yet means the key exists but nothing has used it. Normal in the minutes after setup; a problem if it stays that way.
• A recent request shows when the feed was last fetched and by which key.
• The alarm appears when your key has been fetching repeatedly and getting an empty feed back every time. This is the exact situation that used to be invisible: a site polling for content that never arrives, silently, with nobody told. If you see it, check that the key is scoped to the blog you actually publish on, and that you have published something.

If you publish in more than one language

Ask for each language separately. GET /api/v1/posts?locale=nl returns the same posts you were already getting, but in Dutch wherever a complete Dutch translation exists, and unchanged where none does. It is not a filter: no post disappears because you asked for a language. Use ?language= when you do want to filter on the language a post was written in.

Every post tells you which languages it has. available_locales lists them, and locale_slugs gives the slug each language carries. Those slugs really do differ per language, because each one is chosen around that language's own keyword, so build your per-language URL from locale_slugs rather than translating the slug yourself or reusing the source one.

The details, including what happens to a translation that is not finished yet, are in Public Content API.

What "published" means here

A post published to your own site shows as Available to your site rather than "Published" everywhere its status appears in Nolorem. This is not a lesser state: the post is live in the feed, exactly as it would be for any other destination. The wording only reflects that Nolorem itself never confirms the post rendered anywhere; that confirmation is between your site and whatever it does with the feed.

Changing your mind later

If your site changes platform, or you move away from a bespoke build onto WordPress or another supported CMS, use Change destination on the same Publishing settings page. It walks you through the same migration flow as any other platform switch.