Website: Update device management landing page. (#15702)

Closes: #15685

Changes:
- Updated the transparency section on the /device-management page.
- Updated link styles.
This commit is contained in:
Eric 2023-12-15 17:00:45 -06:00 committed by GitHub
parent c40bd9f3c3
commit 819a0c9d04
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 6 deletions

View file

@ -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;

View file

@ -61,7 +61,7 @@
<h3>Absolute certainty</h3>
<p>Reduce time wasted hunting down whether a change happened. <em>Actually</em> verify that settings are applied using real data pulled from your users' devices.</p>
<div purpose="checklist" class="flex-column d-flex">
<p>Use a git repo as the source of truth to reduce errors (submitting the wrong patch, configuration setting etc).</p>
<p>Use a git repo as the source of truth to reduce errors (submitting the wrong patch, configuration setting, etc.)</p>
<p>Every change to a policy or security control is tracked and auditable in Fleets history, or via the repo commit log</p>
</div>
</div>
@ -82,12 +82,12 @@
<div purpose="feature" class="d-flex flex-md-row flex-column-reverse justify-content-between mx-auto align-items-center">
<div purpose="feature-text" class="d-flex flex-column">
<h3>Transparency for end users</h3>
<p>Provide assurance to your end users with Fleet Desktop about what information is being collected from their device.</p>
<h3>Scope transparency</h3>
<p>Increase <a href="https://fleetdm.com/handbook/company/why-this-way#why-open-source">buy-in</a> from end users by clarifying how their work computers are managed.</p>
<div purpose="checklist" class="flex-column d-flex">
<p>Let end users see the source code for exactly how they are being monitored.</p>
<p>Set clear expectations about what is and isnt acceptable use of work computers.</p>
<p>Let users participate in fixing failing compliance policies.</p>
<p>Give end users assurance about what actions IT can take on their computer</p>
<p>Let end users see exactly what data is collected, all the way down to the source code</p>
<p>Set clear expectations about how to configure company devices</p>
</div>
</div>
<div purpose="feature-image" class="left">