Post whitepaper IT leader's guide to Linux device management AND fix whitepaper form hardcode. (#43780)

<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** Resolves
#https://github.com/fleetdm/confidential/issues/14837
**Related issue:** Resolves
#https://github.com/fleetdm/confidential/issues/14839


Commit 1 - fixes the basic-whitepaper.ejs page so that the LP form
headline is not hard coded to GitOps anymore.
Commit 2 - posts the whitepaper and sets up the LP page 


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Updates**
  * Form headline on whitepaper download page is now customizable.
  * Enhanced email submission feedback handling during download process.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

articles/IT-leaders-guide-to-Linux-device-management.md

@@ -0,0 +1,54 @@
+### Linux adoption is growing. Management hasn't kept up.
+
+* macOS and Windows have mature management ecosystems. Linux does not.
+* Compliance frameworks don't grant exemptions by operating system.
+* Security audits don't skip Linux workstations.
+* These create the Linux gap.
+
+### Unmanaged devices are unmanaged risk.
+
+This guide helps IT leaders understand and close the Linux management gap.
+
+### What you'll learn
+
+You'll learn about a maturity model for planning your adoption path, a clear framework for defining your requirements, and a concrete evaluation scorecard for comparing management platforms. Whether you manage 50 Linux workstations or 5,000, this guide gives you the structure to make a defensible platform decision and explain it to your team.
+
+### Chapter list
+
+- **Why Linux devices are important**
+    * What's driving enterprise Linux adoption and why management is no longer optional.
+- **The business case for managing Linux devices**
+    * Cost, compliance, talent retention, and the price of inaction.
+- **Defining your Linux device management needs**
+    * Key questions to ask and a maturity model to map your goals.
+- **Automated provisioning for Linux desktop in the enterprise**
+    * The provisioning gap, enrollment approaches, and what zero-touch looks like on Linux.
+- **Security baselines for Linux**
+    * Why baselines matter, what to enforce, and how to fight configuration drift.
+- **App and certificate management for Linux**
+    * Software distribution challenges, the notarization gap, patching speed, and shrinking certificate lifetimes.
+- **Protecting the Linux device**
+    * USB and Bluetooth threats, the sudo problem, and remote lock and wipe.
+- **Controlling your software and your data**
+    * Software sovereignty, data sovereignty, and why your management tooling should reflect the values that made Linux worth adopting.
+- **Choosing the right solution**
+    * Business and technical requirements, an evaluation criteria table, and a structured way to compare platforms.
+
+
+
+<meta name="articleTitle" value="The IT leader's guide to Linux device management"> 
+
+<meta name="authorFullName" value="n/a">
+<meta name="authorGitHubUsername" value="fleet-release">
+
+<meta name="category" value="whitepaper">
+<meta name="publishedOn" value="2026-04-20">
+<meta name="description" value="Close the Linux management gap. A guide to help IT leaders understand the business case, security, compliance, and choosing the right solution.">
+
+
+<meta name="articleImageUrl" value="../website/assets/images/articles/IT-leaders-guide-to-Linux-device-management-cover-image-504x336@2x.png">
+<meta name="whitepaperFilename" value="IT-leaders-guide-to-Linux-device-management.pdf"> 
+<meta name="formHeadline" value="Learn how to close the Linux management gap">
+
+<meta name="introductionTextBlockOne" value="Linux now exceeds 5% of desktop market share. Stack Overflow's 2025 developer survey shows nearly 30% of developers use Linux as their primary work OS.">
+<meta name="introductionTextBlockTwo" value="Your most important contributors, developers, engineers, and security practitioners, are choosing Linux. And in most organizations, those devices sit outside formal IT management.">

articles/modern-endpoint-management-managing-devices-as-code.md

@@ -57,6 +57,7 @@ You will also see how treating device management as a software discipline helps
 
 
 <meta name="articleImageUrl" value="../website/assets/images/articles/modern-endpoint-management-managing-devices-as-code-cover-image-504x336@2x.png">
+<meta name="formHeadline" value="Learn how GitOps transforms device management">
 
 <meta name="whitepaperFilename" value="fleet-modern-endpoint-device-management-managing-devices-as-code.pdf"> 
 <meta name="introductionTextBlockOne" value="Traditional device management does not scale. Teams still rely on manual updates, GUI tools, and scattered inventories."> 

handbook/company/writing.md

@@ -163,6 +163,8 @@ Whitepaper articles use a separate article template that requires additional `<m
   - `articleImageUrl`: A relative link to a cover image for the whitepaper. The specified image is placed next to the article title on the whitepaper article template page.
 - Optional `<meta>` tags:
   - `introductionTextBlockTwo` - A optional second introduction paragraph for the whitepaper. The contents of this meta tag are added as a separate paragraph to the introduction above the Markdown content.
+  - `formHeadline` - Put in a short phrase that will show immediately above the form fields. If not used, a default generic phrase will be use ("Get the white paper to learn more")
+
 
 **Example whitepaper article meta tag section**
 
@@ -177,6 +179,7 @@ Whitepaper articles use a separate article template that requires additional `<m
 <meta name="whitepaperFilename" value="fleet-modern-endpoint-device-management-managing-devices-as-code.pdf"> 
 <meta name="introductionTextBlockOne" value="Traditional device management does not scale. Teams still rely on manual updates, GUI tools, and scattered inventories."> 
 <meta name="introductionTextBlockTwo" value="Modern IT teams treat device management like software engineering. They define device state in code, review changes in Git, and deploy updates automatically.">
+<meta name="formHeadline" value="Learn more about modern IT device management">
 ```
 
 

website/views/pages/articles/basic-whitepaper.ejs

@@ -22,7 +22,7 @@
             <div purpose="right-sidebar" class="d-flex flex-column">
               <div purpose="form-container">
                 <div id="download-form" purpose="whitepaper-download-form">
-              <h4>Learn how GitOps transforms device management</h4>
+                  <h4><%- thisPage.meta.formHeadline || 'Get the white paper to learn more' %></h4>
                   <ajax-form class="w-100" action="deliverWhitepaperDownloadRequest" :form-errors.sync="formErrors" :form-data="formData" :form-rules="formRules" :syncing.sync="syncing" :cloud-error.sync="cloudError" @submitted="submittedDownloadForm()" v-if="!cloudSuccess">
                     <div class="form-group">
                       <label for="first-name">First name *</label>