diff --git a/webengine/views/drupal-vs-content-one.html b/webengine/views/drupal-vs-content-one.html index 428b65e..80f01c3 100644 --- a/webengine/views/drupal-vs-content-one.html +++ b/webengine/views/drupal-vs-content-one.html @@ -80,46 +80,6 @@

Drupal - -
-
-
-

At a glance

-

The four trade-offs that show up most often when teams compare Drupal vs Content.One.

-
-
-
-
- -
-

What it really costs

-

Drupal's license is free. The cost is Drupal hosting, developers or an agency, and ongoing maintenance. Content.One is quote-based with hosting included.

-
-
-
- -
-

Who runs it

-

With Drupal, you (or a host like Acquia or Pantheon) run the servers, apply security patches, and handle upgrades. Content.One is managed, with no servers to patch.

-
-
-
- -
-

Multisite

-

Drupal multisite is native but a self-managed, shared-codebase model. Content.One runs federated multisite from one platform, managed for you.

-
-
-
- -
-

When each wins

-

Pick Drupal for open-source control when you have the developers to run it. Pick Content.One for managed federated multisite a marketing team can drive.

-
-
-
-
-
@@ -200,6 +160,46 @@

What real customers

+ +
+
+
+

At a glance

+

The four trade-offs that show up most often when teams compare Drupal vs Content.One.

+
+
+
+
+ +
+

What it really costs

+

Drupal's license is free. The cost is Drupal hosting, developers or an agency, and ongoing maintenance. Content.One is quote-based with hosting included.

+
+
+
+ +
+

Who runs it

+

With Drupal, you (or a host like Acquia or Pantheon) run the servers, apply security patches, and handle upgrades. Content.One is managed, with no servers to patch.

+
+
+
+ +
+

Multisite

+

Drupal multisite is native but a self-managed, shared-codebase model. Content.One runs federated multisite from one platform, managed for you.

+
+
+
+ +
+

When each wins

+

Pick Drupal for open-source control when you have the developers to run it. Pick Content.One for managed federated multisite a marketing team can drive.

+
+
+
+
+
diff --git a/webengine/views/sanity-vs-content-one.html b/webengine/views/sanity-vs-content-one.html index 218772b..946b71b 100644 --- a/webengine/views/sanity-vs-content-one.html +++ b/webengine/views/sanity-vs-content-one.html @@ -80,46 +80,6 @@

Sanity

- -
-
-
-

At a glance

-

The four trade-offs that show up most often when teams compare Sanity vs Content.One.

-
-
-
-
- -
-

Who it's built for

-

Sanity is built for developer-led product teams who want full control of the content model in code. Content.One is built for marketing-led teams running many sites without a developer in the loop for every change.

-
-
-
- -
-

Hosting included

-

Sanity is the content backend and Content Lake only. You build and host your own frontend. Content.One includes hosting and global CDN delivery.

-
-
-
- -
-

Limits and tiers

-

Sanity meters seats, documents, and API requests, and gates SSO, custom roles, and audit logs to Enterprise. Content.One keeps SSO, custom roles, and audit logs in the standard product.

-
-
-
- -
-

When each wins

-

Pick Sanity for code-first builds where engineers own the stack. Pick Content.One for federated multisite setups that marketers run day to day.

-
-
-
-
-
@@ -200,6 +160,46 @@

What real customers

+ +
+
+
+

At a glance

+

The four trade-offs that show up most often when teams compare Sanity vs Content.One.

+
+
+
+
+ +
+

Who it's built for

+

Sanity is built for developer-led product teams who want full control of the content model in code. Content.One is built for marketing-led teams running many sites without a developer in the loop for every change.

+
+
+
+ +
+

Hosting included

+

Sanity is the content backend and Content Lake only. You build and host your own frontend. Content.One includes hosting and global CDN delivery.

+
+
+
+ +
+

Limits and tiers

+

Sanity meters seats, documents, and API requests, and gates SSO, custom roles, and audit logs to Enterprise. Content.One keeps SSO, custom roles, and audit logs in the standard product.

+
+
+
+ +
+

When each wins

+

Pick Sanity for code-first builds where engineers own the stack. Pick Content.One for federated multisite setups that marketers run day to day.

+
+
+
+
+