Skip to content

01Website and e-shop · module

Company website and CMS

Manage pages, articles, menus, and redirects directly in your ERP—even across multiple websites.

  • Website
  • Website domain
  • Page
  • Page section
  • Content item
  • Content revision
  • Menu
  • Menu item
  • Redirect
14
capabilities
9
record types
3
automations
2
integrations and AI tools

02What the module does

Less routine. More value.

Company website and CMS lets you manage your website content directly in Draivix: pages, articles, menus, and redirects for one or more company websites. Content goes through approval, keeps a version history, and can be scheduled for publication on a specific date. A separately built front end renders the website by fetching content via a public JSON API, so your site design isn’t tied to the ERP.

  • Company websites in one placeManage multiple websites within a single company, each with its own domains, primary domain, and SSL (encrypted connection) settings. You can add another website directly inside the system you already work in.
  • Every domain serves the right websiteWhen a visitor opens a URL, the system identifies which website it belongs to by its domain and returns the matching content. Multiple websites can run side by side without their content ever getting mixed up.
  • Incomplete websites won't go liveBefore launch, the system verifies the name, slug (URL path segment), template, default language, active currency, and at least one domain. A website missing any of these cannot be activated.
  • Switch your website to maintenance modeA website has an active, maintenance, or disabled status, and every change is logged as an event. You can trigger automations from it, such as notifying an administrator.
  • Content organized into collectionsSave articles and other content in collections as items with a language, Markdown or HTML body, and SEO fields for search engines. Everything needed for publishing stays together on a single item.
  • Built-in content approval workflowEvery item has a status: draft, pending approval, published, scheduled, or archived. Only users with the right permissions can change the status, so you always know what stage a piece of copy is in.
  • Publish on your scheduleSet a publication date on an item and the content will only appear on the website once that time arrives. You can prepare articles in advance without having to publish them manually on the day.
  • Previous versions always on handEvery edit to a content item is saved as a revision, so you can look up earlier versions at any time and see how the text looked before a change.
  • Build pages section by sectionEvery web page is made up of sections and has its own statuses from draft to archived. You edit content in modular blocks rather than one long wall of text.
  • Full control over website menusBuild your website menu from individual menu items in the editor. You manage navigation right inside the ERP, in the same place as your pages and articles.
  • Old URLs keep workingTrack redirects for old URLs as individual records. This is especially useful when migrating from an older website where page URLs change.
  • Preview articles before importingMigrate existing articles by importing them from Markdown. Review a preview first and only then run the live import, so you know what will land on your website.
  • Import pages and menusBring existing pages and menus into Draivix via JSON import. When moving from an old website, you don't have to rebuild them by hand.
  • The entire website in a single snapshotGenerate a full content snapshot of the entire website for your front end—the independently built visitor-facing layer. Only signed-in users with content read permissions can access it.

03How it works

How it works step by step.

  1. How it works

    Each website in Draivix is a separate Web record with one or more domains. For each domain, you specify whether it is primary and whether it runs on SSL. When a visitor opens an address, the system identifies the website by its domain and returns its content.

    Read in detail

    Draivix acts as a headless CMS. A separately built front end handles the visual presentation and reads content through a public JSON API. Your content, products, orders, and customers all live in one system alongside your accounting and CRM, while your website design can evolve independently.

  2. Launching a website and maintenance mode

    A new website starts in a disabled state. Before launching, the system verifies that the website has a name, slug, and template filled in, that its default language is among the supported languages, that the website currency is one of your company’s active currencies, and that at least one domain exists. Only then does it activate the website.

    Read in detail

    You can switch a live website into maintenance mode and back, or disable it completely. Every status change is logged as an event that can trigger an automation, such as notifying an administrator.

  3. Content publishing with approval

    Articles and other content are stored in collections as content items with a slug, language, Markdown or HTML body, and SEO fields. Each item has a status: draft, pending approval, published, scheduled, or archived. Neither the status nor the publication date can be overwritten directly in the form; they change only through actions visible to users with the required permissions.

    Read in detail

    Only published content—or scheduled content whose publication date has passed—appears on the website. Every edit is saved as a revision, so you can always trace previous versions. Pages are built from sections and follow their own lifecycle from draft to archive.

  4. Menus, redirects, and content import

    You build your website menu from individual items in the menu editor. Redirects for old URLs are tracked as separate records, which makes migrating from a legacy website much easier.

    Read in detail

    Existing content can be migrated via import: articles from Markdown (with a preview first, followed by the live import), and pages and menus from JSON. For your front end or backups, you can create a snapshot of the entire website's content, readable only by signed-in users with content read permissions.

04What runs automatically

Automations that save time.

  1. Activation only after validation

    When you activate a website, the system first checks its name, slug, template, language, currency, and domain. Only when everything is in place does the website go live; otherwise it stays disabled.

  2. Articles go live on the scheduled day

    As soon as the publication date arrives, scheduled content appears on the website automatically. Nobody has to be at their desk or flip any switches manually.

  3. Changes can trigger follow-up actions

    Every website status change and every content publication fires an event. You can hook automations up to it, such as sending an alert to an administrator.

External integrations

  • Website design decoupled from the ERPAn independently built front end fetches content from Draivix via the public JSON API. You can redesign your website independently of the ERP while keeping all content in one place.
  • Images and files in one placeThe system serves website images and files directly from document storage, keeping all your web assets in one place.

05Frequently asked questions

Can I manage multiple websites at once in Draivix?

Yes. Each website is a separate record with its own domains, languages, currency, content, and menus. The system tells which website a visitor opened based on the domain.

Is Draivix a traditional template-based CMS?

No, it works as a headless CMS. You manage content in the ERP, and an independently built front end retrieves it via the public JSON API.

Can I schedule an article for a later date?

Yes. Switch the article to the scheduled status with a publication date, and it will appear on the website as soon as that date arrives.

Can anyone in the company publish content?

No. The status and publication date cannot be edited directly in the form—only through actions visible to users with the appropriate permissions. Changes are saved as revisions.

How do I migrate content from my current website?

Import articles from Markdown with a preview step before the live import, and import pages and menus from JSON. Cover your old URLs with redirect records.

Let’s start together

Tell us how your business works.

We will show you what a system that takes over part of that work could look like.

Book a consultation