mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 13:37:30 +00:00
Website: update article categories (#6679)
* add deploy category, change product to guides * update links to deployment guides * Update deploy-fleet-on-hetzner-cloud.md * Update enrolling-a-digital-ocean-droplet-on-a-fleet-instance.md * Update how-to-install-osquery-and-enroll-linux-devices-into-fleet.md * Update delivering-data-to-snowflake-from-fleet-and-osquery.md * Update how-to-install-osquery-and-enroll-windows-devices-into-fleet.md * Update how-to-install-osquery-and-enroll-macos-devices-into-fleet.md * Update deploying-fleet-on-aws-with-terraform.md * Update deploying-fleet-on-render.md * Update how-to-uninstall-osquery.md * Update osquery-a-tool-to-easily-ask-questions-about-operating-systems.md * Update get-and-stay-compliant-across-your-devices-with-fleet.md * Update work-may-be-watching-but-it-might-not-be-as-bad-as-you-think.md * Update converting-unix-timestamps-with-osquery.md * Update correlate-network-connections-with-community-id-in-osquery.md * Update using-elasticsearch-and-kibana-to-visualize-osquery-performance.md * Update fleet-quick-tips-querying-procdump-eula-has-been-accepted.md * Update locate-assets-with-osquery.md * Update osquery-consider-joining-against-the-users-table.md * Update import-and-export-queries-and-packs-in-fleet.md * Update ebpf-the-future-of-osquery-on-linux.md * Update generate-process-trees-with-osquery.md * Update get-and-stay-compliant-across-your-devices-with-fleet.md * Update work-may-be-watching-but-it-might-not-be-as-bad-as-you-think.md * Update ebpf-the-future-of-osquery-on-linux.md * Change category meta value back to guides Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com> * change article category * update latest article category * add redirects for articles not handled by cloudflare rules * Update to main nav I did a little more housekeeping on the main nav for when we do the switch on these categories. - Added link to /deploy under Guides on the Documentation dropdown. - Added link to /guides under Guides on the Documentation dropdown - Removed the now redundant "See all" from under Guides on the Documentation dropdown - Removed the now redundant "See all" from under Articles on the Community dropdown (There's no need to point users to All categories any more, since all the category land are now linked to independently from the main nav. * Update article category name Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com> Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
This commit is contained in:
Eric
GitHub
parent
0312454f4c
commit
f10e33d387
26 changed files with 52 additions and 56 deletions
|
|
@ -77,9 +77,9 @@ So there we go. Simple, human readable timestamps with osquery.
|
|||
|
||||
Let us know if you can think of any other example scenarios you’d like us to cover.
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorFullName" value="Mike Thomas">
|
||||
<meta name="authorGitHubUsername" value="mike-j-thomas">
|
||||
<meta name="publishedOn" value="2021-06-15">
|
||||
<meta name="articleTitle" value="Converting unix timestamps with osquery">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/converting-unix-timestamps-with-osquery-cover-800x450@2x.jpeg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/converting-unix-timestamps-with-osquery-cover-800x450@2x.jpeg">
|
||||
|
|
|
|||
|
|
@ -114,9 +114,9 @@ The `community_id` column can then be used to correlate the events logged by net
|
|||
On Linux, the `socket_events` table may produce additional utility as it captures all socket connections, not only those active at the time of query execution.
|
||||
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorFullName" value="Zach Wasserman">
|
||||
<meta name="authorGitHubUsername" value="zwass">
|
||||
<meta name="publishedOn" value="2021-06-02">
|
||||
<meta name="articleTitle" value="Correlate network connections with community ID in osquery.">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/correlate-network-connections-with-community-id-in-osquery-cover-800x502@2x.jpeg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/correlate-network-connections-with-community-id-in-osquery-cover-800x502@2x.jpeg">
|
||||
|
|
|
|||
|
|
@ -707,7 +707,7 @@ Now that you’re ready to use Fleet and have a host installed. Here's some next
|
|||
- Import Fleet's [standard query library](https://fleetdm.com/docs/using-fleet/standard-query-library) to start asking questions about your hosts.
|
||||
- To run a more secure setup, consider creating a dedicated `fleet` user with Docker's support for user [namespaces](https://docs.docker.com/engine/security/userns-remap/).
|
||||
|
||||
<meta name="category" value="guides">
|
||||
<meta name="category" value="deploy">
|
||||
<meta name="authorGitHubUsername" value="ksatter">
|
||||
<meta name="authorFullName" value="Katheryn Satterlee">
|
||||
<meta name="publishedOn" value="2022-06-27">
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Deploying Fleet on AWS with Terraform
|
||||
|
||||
There are many ways to deploy Fleet. Last time, we looked at deploying [Fleet on Render](https://fleetdm.com/guides/deploying-fleet-on-render). This time, we’re going to deploy Fleet on AWS with Terraform IaC (infrastructure as code).
|
||||
There are many ways to deploy Fleet. Last time, we looked at deploying [Fleet on Render](https://fleetdm.com/deploy/deploying-fleet-on-render). This time, we’re going to deploy Fleet on AWS with Terraform IaC (infrastructure as code).
|
||||
|
||||
Deploying on AWS with Fleet’s reference architecture will get you a fully functional Fleet instance that can scale to your needs
|
||||
|
||||
|
|
@ -145,7 +145,7 @@ Navigating to `https://fleet.queryops.com` we should be greeted with the Setup p
|
|||
Setting up all the required infrastructure to run a dedicated web service in AWS can be a daunting task. The Fleet team’s goal is to provide a solid base to build from. As most AWS environments have their own specific needs and requirements, this base is intended to be modified and tailored to your specific needs.
|
||||
|
||||
|
||||
<meta name="category" value="guides">
|
||||
<meta name="category" value="deploy">
|
||||
<meta name="authorGitHubUsername" value="edwardsb">
|
||||
<meta name="authorFullName" value="Ben Edwards">
|
||||
<meta name="publishedOn" value="2021-11-30">
|
||||
|
|
|
|||
|
|
@ -142,9 +142,9 @@ fleetctl apply -f standard-query-library.yaml
|
|||
That’s it! We have successfully deployed and configured a Fleet instance! Render makes this process super easy, and you can even enable auto-scaling and let the app grow with your needs.
|
||||
|
||||
|
||||
<meta name="category" value="guides">
|
||||
<meta name="category" value="deploy">
|
||||
<meta name="authorGitHubUsername" value="edwardsb">
|
||||
<meta name="authorFullName" value="Ben Edwards">
|
||||
<meta name="publishedOn" value="2021-11-21">
|
||||
<meta name="articleTitle" value="Deploying Fleet on Render">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/deploying-fleet-on-render-cover-1600x900@2x.jpg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/deploying-fleet-on-render-cover-1600x900@2x.jpg">
|
||||
|
|
|
|||
|
|
@ -14,9 +14,9 @@ This talk discusses the Audit approach to Linux events with osquery, including c
|
|||
|
||||
<iframe class="speakerdeck-iframe" frameborder="0" src="https://speakerdeck.com/player/a0444dd4b2b24bad8db7908590506699" title="eBPF & the future of osquery on Linux" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true" style="border: 0px; background: padding-box padding-box rgba(0, 0, 0, 0.1); padding: 0px; border-radius: 6px; box-shadow: rgba(0, 0, 0, 0.2) 0px 5px 40px; width: 560px; height: 314px;" data-ratio="1.78343949044586"></iframe>
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="security">
|
||||
<meta name="authorGitHubUsername" value="zwass">
|
||||
<meta name="authorFullName" value="Zach Wasserman">
|
||||
<meta name="publishedOn" value="2021-01-25">
|
||||
<meta name="articleTitle" value="eBPF & the future of osquery on Linux">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/ebpf-the-future-of-osquery-on-linux-cover-700x394@2x.png">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/ebpf-the-future-of-osquery-on-linux-cover-700x394@2x.png">
|
||||
|
|
|
|||
|
|
@ -123,4 +123,4 @@ Which should return all the commands typed in the shell, and I got an output lik
|
|||
<meta name="authorFullName" value="Kelvin Omereshone">
|
||||
<meta name="publishedOn" value="2022-05-26">
|
||||
<meta name="articleTitle" value="Enrolling a DigitalOcean Droplet on a Fleet instance">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/enrolling-a-digitalocean-droplet-server-on-a-fleet-instance-cover-1600x900@2x.jpg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/enrolling-a-digitalocean-droplet-server-on-a-fleet-instance-cover-1600x900@2x.jpg">
|
||||
|
|
|
|||
|
|
@ -21,9 +21,9 @@ For more information about the recent security breach, take a look at [Microsoft
|
|||
### Could this post be more helpful?
|
||||
Let us know if you can think of any other example scenarios you’d like us to cover.
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorGitHubUsername" value="mike-j-thomas">
|
||||
<meta name="authorFullName" value="Mike Thomas">
|
||||
<meta name="publishedOn" value="2021-05-11">
|
||||
<meta name="articleTitle" value="Fleet quick tips — identify systems where the ProcDump EULA has been accepted">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/fleet-quick-tips-querying-procdump-eula-has-been-accepted-cover-700x440@2x.png">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/fleet-quick-tips-querying-procdump-eula-has-been-accepted-cover-700x440@2x.png">
|
||||
|
|
|
|||
|
|
@ -131,9 +131,9 @@ FROM (
|
|||
With this query as a building block, osquery provides the capability to generate rich process trees. Consider using this with an osquery TLS server such as [Fleet](https://fleetdm.com/) to examine this information on multiple machines at once.
|
||||
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorGitHubUsername" value="zwass">
|
||||
<meta name="authorFullName" value="Zach Wasserman">
|
||||
<meta name="publishedOn" value="2020-03-17">
|
||||
<meta name="articleTitle" value="Generate process trees with osquery">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/generate-process-trees-with-osquery-cover-700x393@2x.jpeg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/generate-process-trees-with-osquery-cover-700x393@2x.jpeg">
|
||||
|
|
|
|||
|
|
@ -95,9 +95,9 @@ Thanks to automation and open source tools like osquery and Fleet, compliance is
|
|||
|
||||
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="security">
|
||||
<meta name="authorFullName" value="Drew Baker">
|
||||
<meta name="authorGitHubUsername" value="DrewBakerfdm">
|
||||
<meta name="publishedOn" value="2022-03-09">
|
||||
<meta name="articleTitle" value="Get and stay compliant across your devices with Fleet.">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/get-and-stay-compliant-across-your-devices-with-fleet-cover-1600x900@2x.jpg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/get-and-stay-compliant-across-your-devices-with-fleet-cover-1600x900@2x.jpg">
|
||||
|
|
|
|||
|
|
@ -88,4 +88,4 @@ If you’re managing an enterprise environment, you will likely have a deploymen
|
|||
<meta name="authorGitHubUsername" value="ksatter">
|
||||
<meta name="publishedOn" value="2022-03-19">
|
||||
<meta name="articleTitle" value="How to install osquery and enroll Linux devices into Fleet">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/install-osquery-and-enroll-linux-devices-into-fleet-cover-1600x900@2x.jpg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/install-osquery-and-enroll-linux-devices-into-fleet-cover-1600x900@2x.jpg">
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ Alternatively, you can run a preview environment of Fleet locally (which automat
|
|||
|
||||
## Prerequisites
|
||||
|
||||
Before installing osquery on macOS and enrolling that macOS device, you will need to have access to a Fleet server (see [Deploying Fleet on Render](https://fleetdm.com/guides/deploying-fleet-on-render) for an example.)
|
||||
Before installing osquery on macOS and enrolling that macOS device, you will need to have access to a Fleet server (see [Deploying Fleet on Render](https://fleetdm.com/deploy/deploying-fleet-on-render) for an example.)
|
||||
|
||||
You will also need to install the `fleetctl` CLI tool if you don’t have it already. `fleetctl` can be installed via `npm` by running the command below:
|
||||
|
||||
|
|
@ -58,4 +58,4 @@ Fleet makes it easy to install osquery and enrol macOS devices with fleetctl. If
|
|||
<meta name="authorGitHubUsername" value="dominuskelvin">
|
||||
<meta name="publishedOn" value="2022-01-13">
|
||||
<meta name="articleTitle" value="How to install osquery and enroll macOS devices into Fleet">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/install-osquery-and-enroll-macos-devices-into-fleet-cover-1600x900@2x.jpg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/install-osquery-and-enroll-macos-devices-into-fleet-cover-1600x900@2x.jpg">
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ Alternatively, you can run a preview environment of Fleet locally (which automat
|
|||
|
||||
## Prerequisites
|
||||
|
||||
Before installing osquery on Windows and enrolling that Windows device, you will need access to a Fleet server (see [Deploying Fleet on Render](https://fleetdm.com/guides/deploying-fleet-on-render) for an example.)
|
||||
Before installing osquery on Windows and enrolling that Windows device, you will need access to a Fleet server (see [Deploying Fleet on Render](https://fleetdm.com/deploy/deploying-fleet-on-render) for an example.)
|
||||
|
||||
If you don’t already have it, you will also need to install the `fleetctl` CLI tool. `fleetctl` can be installed via `npm` by running the following command:
|
||||
|
||||
|
|
|
|||
|
|
@ -57,4 +57,4 @@ Are you running into trouble uninstalling osquery on macOS, Windows, or Linux? G
|
|||
<meta name="authorGitHubUsername" value="eashaw">
|
||||
<meta name="publishedOn" value="2021-09-08">
|
||||
<meta name="articleTitle" value="How to uninstall osquery">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/how-to-uninstall-osquery-cover-1600x900@2x.jpg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/how-to-uninstall-osquery-cover-1600x900@2x.jpg">
|
||||
|
|
|
|||
|
|
@ -37,9 +37,9 @@ Here’s how you can do this in 2 quick fleetctl commands.
|
|||
|
||||
Let us know if you can think of any other example scenarios you’d like us to cover.
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorGitHubUsername" value="noahtalerman">
|
||||
<meta name="authorFullName" value="Noah Talerman">
|
||||
<meta name="publishedOn" value="2021-02-16">
|
||||
<meta name="articleTitle" value="Import and export queries and packs in Fleet">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/import-and-export-queries-and-packs-in-fleet-cover-700x343@2x.png">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/import-and-export-queries-and-packs-in-fleet-cover-700x343@2x.png">
|
||||
|
|
|
|||
|
|
@ -32,9 +32,9 @@ WHERE url = 'http://ipapi.co/json';
|
|||
Other techniques
|
||||
A common technique for geolocation of macOS devices with osquery is to use the `wifi_survey` table in combination with the [Google Geolocation API](https://developers.google.com/maps/documentation/geolocation/intro#wifi_access_point_object). This strategy has become more difficult to use due to security controls introduced in macOS 10.15, and poses privacy concerns due to the precision of the location data returned by the API.
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorGitHubUsername" value="zwass">
|
||||
<meta name="authorFullName" value="Zach Wasserman">
|
||||
<meta name="publishedOn" value="2021-05-11">
|
||||
<meta name="articleTitle" value="Locate device assets in the event of an emergency.">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/locate-assets-with-osquery-cover-700x393@2x.jpeg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/locate-assets-with-osquery-cover-700x393@2x.jpeg">
|
||||
|
|
|
|||
|
|
@ -59,9 +59,9 @@ To deploy osquery at scale across your organization’s devices, an osquery mana
|
|||
|
||||
Ready to give Fleet a try? Head over to our [get started page](https://fleetdm.com/get-started), and you can be up and running with a sandbox environment in less than 5 minutes. Alternatively, check out the [docs](https://fleetdm.com/docs) to learn how to deploy Fleet across your organization.
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorGitHubUsername" value="dominuskelvin">
|
||||
<meta name="authorFullName" value="Kelvin Omereshone">
|
||||
<meta name="publishedOn" value="2022-04-04">
|
||||
<meta name="articleTitle" value="Osquery: a tool to easily ask questions about operating systems">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/osquery-a-tool-to-easily-ask-questions-about-operating-systems-cover-1600x900@2x.jpg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/osquery-a-tool-to-easily-ask-questions-about-operating-systems-cover-1600x900@2x.jpg">
|
||||
|
|
|
|||
|
|
@ -60,9 +60,9 @@ Writing the query with this `JOIN` ensures that osquery first generates the list
|
|||
|
||||
Note: It is important to use `CROSS JOIN` as this tells the query optimizer not to reorder the evaluation of the tables. If we use a regular `JOIN` it is possible that reordering could result in the original error being encountered (because the `chrome_extensions` table generates with no `uid` in its context).
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorGitHubUsername" value="zwass">
|
||||
<meta name="authorFullName" value="Zach Wasserman">
|
||||
<meta name="publishedOn" value="2021-05-06">
|
||||
<meta name="articleTitle" value="Osquery: Consider joining against the users table">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/osquery-consider-joining-against-the-users-table-cover-700x437@2x.jpeg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/osquery-consider-joining-against-the-users-table-cover-700x437@2x.jpeg">
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ Fleet also lets you [assign users different levels of access](https://fleetdm.co
|
|||
Fleet policies, teams, and permissions empower employees at every level of your organization to share the responsibility of measuring compliance. With more hands on deck, going after your goals will be a breeze.
|
||||
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorFullName" value="Chris McGillicuddy">
|
||||
<meta name="authorGitHubUsername" value="chris-mcgillicuddy">
|
||||
<meta name="publishedOn" value="2022-07-18">
|
||||
|
|
|
|||
|
|
@ -124,9 +124,9 @@ This will import the Index Pattern that allows Kibana to read the osquery data,
|
|||
|
||||
The dashboard created in this tutorial serves as a great starting point for monitoring the performance of osquery in your organization. Take the time to determine what your priorities are, and modify the dashboard to suit your needs.
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="guides">
|
||||
<meta name="authorFullName" value="Zach Wasserman">
|
||||
<meta name="authorGitHubUsername" value="zwass">
|
||||
<meta name="publishedOn" value="2021-05-26">
|
||||
<meta name="articleTitle" value="Using Elasticsearch and Kibana to visualize osquery performance">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/using-elasticsearch-and-kibana-to-visualize-osquery-performance-cover-700x393@2x.jpeg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/using-elasticsearch-and-kibana-to-visualize-osquery-performance-cover-700x393@2x.jpeg">
|
||||
|
|
|
|||
|
|
@ -45,9 +45,9 @@ A VPN (virtual private network) helps to protect your company’s data when acce
|
|||
|
||||
While it is common for companies to collect activity data, it’s rarely looked at manually, and even less so is it collected nefariously. So it’s probably OK to check your social media likes from time to time; your employer is not out to get you. Just remember to use proper judgment, be professional, and avoid sharing your personal information on your work computer.
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="category" value="security">
|
||||
<meta name="authorFullName" value="Mike Thomas">
|
||||
<meta name="authorGitHubUsername" value="mike-j-thomas">
|
||||
<meta name="publishedOn" value="2021-10-22">
|
||||
<meta name="articleTitle" value="Work may be watching, but it might not be as bad as you think.">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/work-may-be-watching-but-it-might-not-be-as-bad-as-you-think-cover-1600x900@2x.jpg">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/work-may-be-watching-but-it-might-not-be-as-bad-as-you-think-cover-1600x900@2x.jpg">
|
||||
|
|
|
|||
|
|
@ -41,15 +41,15 @@ parasails.registerPage('articles', {
|
|||
break;
|
||||
case 'guides':
|
||||
this.articleCategory = 'Guides';
|
||||
this.categoryDescription = 'Learn more about how to deploy and use Fleet.';
|
||||
this.categoryDescription = 'Learn more about how to use Fleet to accomplish your goals.';
|
||||
break;
|
||||
case 'announcements':
|
||||
this.articleCategory = 'Announcements';
|
||||
this.categoryDescription = 'The latest news from Fleet.';
|
||||
break;
|
||||
case 'use-cases':
|
||||
this.articleCategory = 'Product';
|
||||
this.categoryDescription = 'Learn how you can use Fleet to accomplish your goals.';
|
||||
case 'deploy':
|
||||
this.articleCategory = 'Deployment guides';
|
||||
this.categoryDescription = 'Learn more about how to deploy Fleet.';
|
||||
break;
|
||||
case 'podcasts':
|
||||
this.articleCategory = 'Podcasts';
|
||||
|
|
|
|||
8
website/config/routes.js
vendored
8
website/config/routes.js
vendored
|
|
@ -68,15 +68,15 @@ module.exports.routes = {
|
|||
}
|
||||
},
|
||||
|
||||
'r|/((device-management|securing|releases|engineering|guides|announcements|use-cases|podcasts|report)/(.+))$|': {
|
||||
'r|/((device-management|securing|releases|engineering|guides|announcements|podcasts|report|deploy)/(.+))$|': {
|
||||
skipAssets: false,
|
||||
action: 'articles/view-basic-article',
|
||||
locals: {
|
||||
currentPage: 'articles',
|
||||
}
|
||||
},// handles /device-management/foo, /securing/foo, /releases/foo, /engineering/foo, /guides/foo, /announcements/foo, /use-cases/foo, /podcasts/foo, /report/foo
|
||||
},// Handles /device-management/foo, /securing/foo, /releases/foo, /engineering/foo, /guides/foo, /announcements/foo, /deploy/foo, /podcasts/foo, /report/foo
|
||||
|
||||
'r|^/((device-management|securing|releases|engineering|guides|announcements|use-cases|articles|podcasts|report))/*$|category': {
|
||||
'r|^/((device-management|securing|releases|engineering|guides|announcements|articles|podcasts|report|deploy))/*$|category': {
|
||||
skipAssets: false,
|
||||
action: 'articles/view-articles',
|
||||
locals: {
|
||||
|
|
@ -203,6 +203,8 @@ module.exports.routes = {
|
|||
'GET /try-fleet': '/get-started',
|
||||
'GET /docs/deploying/fleet-public-load-testing': '/docs/deploying/load-testing',
|
||||
'GET /handbook/customer-experience': '/handbook/customers',
|
||||
'GET /guides/deploy-fleet-on-hetzner-cloud': '/deploy/deploy-fleet-on-hetzner-cloud',
|
||||
'GET /use-cases/stay-on-course-with-your-security-compliance-goals': '/guides/stay-on-course-with-your-security-compliance-goals',
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
4
website/scripts/build-static-content.js
vendored
4
website/scripts/build-static-content.js
vendored
|
|
@ -407,7 +407,7 @@ module.exports = {
|
|||
if(embeddedMetadata.category) {
|
||||
// Throwing an error if the article has an invalid category.
|
||||
embeddedMetadata.category = embeddedMetadata.category.toLowerCase();
|
||||
let validArticleCategories = ['product', 'security', 'engineering', 'success stories', 'announcements', 'guides', 'releases', 'podcasts', 'report' ];
|
||||
let validArticleCategories = ['deploy', 'security', 'engineering', 'success stories', 'announcements', 'guides', 'releases', 'podcasts', 'report' ];
|
||||
if(!validArticleCategories.includes(embeddedMetadata.category)) {
|
||||
throw new Error(`Failed compiling markdown content: An article page has an invalid category meta tag (<meta name="category" value="${embeddedMetadata.category}">) at "${path.join(topLvlRepoPath, pageSourcePath)}". To resolve, change the meta tag to a valid category, one of: ${validArticleCategories}`);
|
||||
}
|
||||
|
|
@ -442,7 +442,7 @@ module.exports = {
|
|||
// If the article is categorized as 'product' we'll replace the category with 'use-cases', or if it is categorized as 'success story' we'll replace it with 'device-management'
|
||||
rootRelativeUrlPath = (
|
||||
'/' +
|
||||
(embeddedMetadata.category === 'product' ? 'use-cases' : embeddedMetadata.category === 'success stories' ? 'device-management' : embeddedMetadata.category === 'security' ? 'securing' : embeddedMetadata.category) + '/' +
|
||||
(embeddedMetadata.category === 'success stories' ? 'device-management' : embeddedMetadata.category === 'security' ? 'securing' : embeddedMetadata.category) + '/' +
|
||||
(pageUnextensionedLowercasedRelPath.split(/\//).map((fileOrFolderName) => encodeURIComponent(fileOrFolderName.replace(/^[0-9]+[\-]+/,''))).join('/'))
|
||||
);
|
||||
}
|
||||
|
|
|
|||
14
website/views/layouts/layout.ejs
vendored
14
website/views/layouts/layout.ejs
vendored
|
|
@ -168,10 +168,8 @@
|
|||
<a href="https://github.com/fleetdm/fleet/releases">Releases</a>
|
||||
<a href="/queries">Query library</a>
|
||||
<span>GUIDES</span>
|
||||
<a class="pl-3" href="/guides/deploying-fleet-on-aws-with-terraform">Deploy on AWS with Terraform</a>
|
||||
<a class="pl-3" href="/guides/deploying-fleet-on-render">Deploy on Render</a>
|
||||
<a class="pl-3" href="/guides/deploy-fleet-on-hetzner-cloud">Deploy on Hetzner Cloud with Cloud-init & Docker</a>
|
||||
<a class="pl-3" href="/guides">See more</a>
|
||||
<a class="pl-3" href="/deploy">Deployment guides</a>
|
||||
<a class="pl-3" href="/guides">How-to guides</a>
|
||||
</div>
|
||||
</div>
|
||||
<hr>
|
||||
|
|
@ -185,7 +183,6 @@
|
|||
<a href="/securing">Security</a>
|
||||
<a href="/engineering">Engineering</a>
|
||||
<a href="/announcements">Announcements</a>
|
||||
<a href="/articles">See more</a>
|
||||
<span>RESOURCES</span>
|
||||
<a href="/handbook">Handbook</a>
|
||||
<a href="/logos">Logos & artwork</a>
|
||||
|
|
@ -217,10 +214,8 @@
|
|||
<a class="dropdown-item mb-1" href="/queries">Query library</a>
|
||||
<div class="dropdown-divider"></div>
|
||||
<span class="muted dropdown-header">GUIDES</span>
|
||||
<a class="dropdown-item mb-1" href="/guides/deploying-fleet-on-aws-with-terraform">Deploy on AWS with Terraform</a>
|
||||
<a class="dropdown-item" href="/guides/deploying-fleet-on-render">Deploy on Render</a>
|
||||
<a class="dropdown-item" href="/guides/deploy-fleet-on-hetzner-cloud">Deploy on Hetzner Cloud with Cloud-init & Docker</a>
|
||||
<a class="dropdown-item" href="/guides">See more</a>
|
||||
<a class="dropdown-item" href="/deploy">Deployment guides</a>
|
||||
<a class="dropdown-item" href="/guides">How-to guides</a>
|
||||
</div>
|
||||
</div>
|
||||
<div purpose="dropdown-button" class="btn-group">
|
||||
|
|
@ -234,7 +229,6 @@
|
|||
<a class="dropdown-item mb-1" href="/securing">Security</a>
|
||||
<a class="dropdown-item mb-1" href="/engineering">Engineering</a>
|
||||
<a class="dropdown-item mb-1" href="/announcements">Announcements</a>
|
||||
<a class="dropdown-item mb-1" href="/articles">See more</a>
|
||||
<div class="dropdown-divider"></div>
|
||||
<span class="muted dropdown-header">RESOURCES</span>
|
||||
<a class="dropdown-item mb-1" href="/handbook">Handbook</a>
|
||||
|
|
|
|||
2
website/views/pages/articles/articles.ejs
vendored
2
website/views/pages/articles/articles.ejs
vendored
|
|
@ -4,7 +4,7 @@
|
|||
<div purpose="categories-and-search" class="d-flex flex-lg-row flex-column justify-content-lg-between justify-content-md-center justify-content-start" v-if="isArticlesLandingPage">
|
||||
<div purpose="categories" class="d-flex flex-md-row flex-column justify-content-start">
|
||||
<div purpose="category-filter" :class="[ filter === 'all' ? 'selected' : '']" @click="filterBy('all')">All</div>
|
||||
<div purpose="category-filter" :class="[ filter === 'product' ? 'selected' : '']" @click="filterBy('product')">Product</div>
|
||||
<div purpose="category-filter" :class="[ filter === 'deploy' ? 'selected' : '']" @click="filterBy('deploy')">Deploy</div>
|
||||
<div purpose="category-filter" :class="[ filter === 'engineering' ? 'selected' : '']" @click="filterBy('engineering')">Engineering</div>
|
||||
<div purpose="category-filter" :class="[ filter === 'security' ? 'selected' : '']" @click="filterBy('security')">Security</div>
|
||||
<div purpose="category-filter" :class="[ filter === 'announcements' ? 'selected' : '']" @click="filterBy('announcements')">Announcements</div>
|
||||
|
|
|
|||
Loading…
Reference in a new issue