Adapt the workflow, not the whole website
Give your developer the connector specification from the connection form. They implement the agreed endpoints while keeping your routing, design, content model and existing materials intact.
BUILT FORYour custom website
Your website. Your design. A more reliable content workflow.
Keep the website your team has already built. Prepare articles in Content Factory, then deliver them through a server-side connector that your developer adds to the existing blog. No redesign or platform migration is required by the integration.
- Works with your existing blog
- A developer-built server connector
- Drafts and confirmed delivery
CFContent FactoryExample
Add a cover to the draft
Your sources + your project brief
Your custom websiteYour content, your voiceDraft
Small changes for a more focused day
A thoughtful workspace helps you focus. Start with the lighting, clear away distractions and leave room for the ideas that matter.
Title and summary ready for review
LESS REPETITION. MORE DIRECTION.
A workflow that fits the way you work.
Prepare before the connector is ready
Develop articles, SEO fields and covers inside Content Factory while the technical connection is being prepared. Connecting a website is not required to review an internal draft.
Make delivery easier to trust
A correct adapter supports idempotent requests, persistent images and status checks. These are technical requirements, not optional shortcuts: they help recover from interrupted responses without creating duplicates.
CHOOSE YOUR STARTING POINT
Not every project needs the same starting point.
An established business website
Add an editorial workflow to the blog you already have. Your developer controls how article fields map into your CMS and how drafts and public posts are stored.
A custom CMS or application
Use the connector contract as an integration boundary. If your site is static-only or cannot expose the required server endpoints, agree the publishing approach with a developer before connecting.
FROM MATERIAL TO A FINISHED DRAFT
Four clear steps. You stay in control.
Review the connector contract
Open the custom-website connection form and share its specification with your developer. Do not send secrets in a public ticket.
Add the server-side adapter
Use HTTPS, same-origin endpoints and a dedicated secret. Keep your existing website and publication rules intact.
Verify before publishing
Check access and supported behavior. A test draft is a separate, confirmed action that creates one non-public item; it is not a read-only check.
Run a repeatable workflow
Review articles and choose the intended destination state. Check operation status before retrying an uncertain delivery.
The guide explains connection requirements and permissions, without automatically publishing test content.Read the guide
BEFORE YOU START
Practical answers, without the guesswork.
Is it a one-click connection for every CMS?
No. A developer must implement the connector contract for your website. The work depends on your CMS and hosting; Content Factory does not assume every website already has those endpoints.
Do I have to rebuild my blog?
The intended integration adds publishing endpoints to your existing server. Your developer should preserve the site's design, routes and existing content rather than replace the website.
What does my developer need?
The current specification shown in the connection form, access to your own server code and an agreed way to map articles, images and publication states. Keep the connector secret server-side.
Can I use the writing tools before integration?
Yes. Create internal article drafts, refine your content instructions and review the output while your developer prepares the connector.
Connect the rest of your content workflow.
Use a single destination or combine the channels your project actually needs.
START WITH SOMETHING REAL
Start with a draft you can actually review.
Try your sources and instructions. Publishing and automation come next, once the result feels right for your project.