From 819a0c9d041e07215e0dbbcf5e04891055a5f6e6 Mon Sep 17 00:00:00 2001 From: Eric Date: Fri, 15 Dec 2023 17:00:45 -0600 Subject: [PATCH] Website: Update device management landing page. (#15702) Closes: #15685 Changes: - Updated the transparency section on the /device-management page. - Updated link styles. --- website/assets/styles/bootstrap-overrides.less | 4 ++++ website/views/pages/fleet-mdm.ejs | 12 ++++++------ 2 files changed, 10 insertions(+), 6 deletions(-) diff --git a/website/assets/styles/bootstrap-overrides.less b/website/assets/styles/bootstrap-overrides.less index bfafde0ca9..24b7a217a0 100644 --- a/website/assets/styles/bootstrap-overrides.less +++ b/website/assets/styles/bootstrap-overrides.less @@ -56,6 +56,10 @@ b, strong, .font-weight-bold { color: @core-fleet-black; } +a[href] { + color: @core-vibrant-blue; +} + footer { font-size: 14px; line-height: 24px; diff --git a/website/views/pages/fleet-mdm.ejs b/website/views/pages/fleet-mdm.ejs index 961931a3ee..202de50048 100644 --- a/website/views/pages/fleet-mdm.ejs +++ b/website/views/pages/fleet-mdm.ejs @@ -61,7 +61,7 @@

Absolute certainty

Reduce time wasted hunting down whether a change happened. Actually verify that settings are applied using real data pulled from your users' devices.

-

Use a git repo as the source of truth to reduce errors (submitting the wrong patch, configuration setting etc).

+

Use a git repo as the source of truth to reduce errors (submitting the wrong patch, configuration setting, etc.)

Every change to a policy or security control is tracked and auditable in Fleet’s history, or via the repo commit log

@@ -82,12 +82,12 @@
-

Transparency for end users

-

Provide assurance to your end users with Fleet Desktop about what information is being collected from their device.

+

Scope transparency

+

Increase buy-in from end users by clarifying how their work computers are managed.

-

Let end users see the source code for exactly how they are being monitored.

-

Set clear expectations about what is and isn’t acceptable use of work computers.

-

Let users participate in fixing failing compliance policies.

+

Give end users assurance about what actions IT can take on their computer

+

Let end users see exactly what data is collected, all the way down to the source code

+

Set clear expectations about how to configure company devices