In https://github.com/fleetdm/fleet/pull/7399 we accidentally:
1. added a condition to `.github/workflows/fleet-and-orbit.yml` that always evaluates to `false` making this workflow always fail
2. modified the condition of `.github/workflows/fleetctl-preview-latest.yml`
This reverts those changes.
* Copy tweak
Not sure this is the right language, but just something to get it started, up to Chris
Feedback/reasoning:
- "to over" or "into over"?
- "over" + specific number seems overly marketing-ish
- maybe "gives visibility to Fortune 1000 companies, and is powering over 1 million…"
* Update homepage.ejs
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
- Removed mention of "Fortune 1000 companies" in copy to keep "1.65 million" figure
- Logos at the bottom of hero banner convey that Fleet is used by Fortune 1000 companies
- Remove note about vulnerability processing being enabled by default. This message is outdated
- Update first sentence to be explicit that "Vulnerability processing" in Fleet detects vulnerable software
- Add sentence about vulnerability date for Fleet Premium (CVSS, EPSS, CISA).
* Update register.ejs
Updated register message with the second of three versions to test.
* Update sandbox-login.ejs
Updated login message with second of three versions.
* Add video modal to sandbox signup and login pages
Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Changed "endpoints" to "computers" per @mikermcneil's suggestion. Changed "devices" to "servers and workstations" in the sentence below for clarification.
* Adding first draft of security awareness
WIP
DO NOT merge as the website will need to be edited to ignore this directory.
Uploading so finalized draft can be reviewed by Des.
* Completing draft
Ready for a first pass by Des!
* Update 2022-05-security-awareness-slides.md
This has been edited for content and copy.
* Moved to a resources folder
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
I made the following changes:
- updated "click here" link on /register and /sandbox-login to point to /deploy (our deployment guides), for a friendlier user experience.
- removed padding-top: 120px which was forcing an awkward scroll to get to the form on register, sandbox-login, and sandbox-expired (I think the original intent was to vertically center the form and graphic on the page)
- I added some margin right to space out the CTAs on the hompage.
Co-authored-by: Eric <eashaw@sailsjs.com>
This adjusts functions related to applying team specs to make sure the `features` key works as expected, this is:
1. Create Team flow
1. if no features are provided, we copy whatever features are set in the global config
2. otherwise, we generate a new config merging whatever is provided with the defaults for new installs.
2. Edit Team flow: we always generate a new config merging whatever is provided with the defaults for new installs.
