Skip to content

How it works

Write once, publish on every REM product

REM Blogs is where teams at REM write the content around their products. Each product shows that content on its own website, in its own brand, without running a CMS of its own.

From draft to every website, in five steps

  1. Sign in with your REM account

    Writers sign in at REM Blogs admin with REM Auth, the same account they use for every REM product. What you may do (author, editor or admin) comes from your REM Auth groups, so access is managed in one place.

  2. Write in the editor

    The editor handles headings, lists, tables, code blocks, task lists, links and images you upload yourself. Guide pages also get tabs, steps and cards. Markdown works too.

  3. Send it for review

    An author sends a post to review; editors comment on it and the author hears about every comment. An editor publishes it now, or with a future date so it appears on its own at that time.

  4. Choose the products it belongs to

    A post can belong to one product or several. Its canonical address stays on the product it is mainly about, so search engines see one original and no duplicates.

  5. Every product shows it, at once

    Publishing sends a signed webhook to each product, which refreshes its pages, sitemap and feeds. Subscribers get one mail, on the topics they picked.

What a team publishes here

  • Blog postsLaunches, changes, how-tos and engineering notes, with topics, authors, related posts, RSS and Atom feeds and a newsletter.
  • User guides and developer docsDocs sets per product with a page tree, search, previous/next links, and every page downloadable as PDF, Word, ODT, HTML or Markdown.
  • Company and legal pagesAbout, contact, terms, privacy, refunds, cookies and acceptable use. Each published version is kept with its effective date; pages that need acceptance say so.
  • Forms and newslettersContact and waitlist forms land in an encrypted inbox and can be passed on to Zoho CRM or a signed webhook. Newsletters use double opt-in and one-click unsubscribe.

What each product gets without building it

  • Its own domain and brand. Content is fetched on the product’s server with its service token and drawn with the product’s own name, logo and colours. Visitors never talk to REM Blogs directly.
  • Search and AI readiness. Structured data (JSON-LD), canonical links, sitemaps, robots rules for AI crawlers and llms.txt for every product.
  • Consent-first analytics. Google Tag Manager or GA4 load only after the visitor agrees, with a consent banner the product does not have to write.
  • Fast pages. Published content is cached and refreshed by the publish webhook, so a change shows within moments and a busy page never waits on the hub.

Publishing for a REM product?

Ask your product’s admin to add you to the right REM Auth group, then sign in.

Questions? Write to support@remplatforms.com.