Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/pricing update #20191

Open
2 of 3 tasks
mike-j-thomas opened this issue Jul 3, 2024 · 3 comments
Open
2 of 3 tasks

/pricing update #20191

mike-j-thomas opened this issue Jul 3, 2024 · 3 comments
Assignees
Labels
#g-digital-experience https://fleetdm.com/handbook/digital-experience ~website Issues related to fleetdm.com

Comments

@mike-j-thomas
Copy link
Member

mike-j-thomas commented Jul 3, 2024

Goal

In the feature comparison, lead with features Mac admins care about the most.

How

  • Mike T will work with @nonpunctual to re-order device management features to lead with those that Mac Admins care about the most
  • Feel free to rename features as you see fit. Make Noah aware via PR review
  • Eric to re-order features in the view action

Changes

Figma: https://www.figma.com/design/3he8e72251IEnF6dBafKq1/%F0%9F%9A%A7-fleetdm.com-(scratchpad)?node-id=14837-274930

@mike-j-thomas mike-j-thomas added the #g-digital-experience https://fleetdm.com/handbook/digital-experience label Jul 3, 2024
@mike-j-thomas mike-j-thomas self-assigned this Jul 3, 2024
@mike-j-thomas mike-j-thomas added the ~website Issues related to fleetdm.com label Jul 3, 2024
@mike-j-thomas
Copy link
Member Author

@eashaw, can you please help us re-order the device management section in pricing the view action? Order as shown in the wireframe. The branch that we are working on: https://github.com/fleetdm/fleet/tree/website-pricing-page-update

@mike-j-thomas
Copy link
Member Author

Hey @eashaw, I talked to Mike about re-ordering the YAML file to align with the agnostic version of the pricing page (e.g., leading with device management features and then using the YAML as the baseline for ordering the HTML). I started to re-order the file but realized that it might be hard for @noahtalerman to review the proposed name changes and consolidation of some of the features. So I'm thinking that we should split this into two parts. I'll finish the PR on the branch above, annotate the proposed name changes for Noah, and get his approval. Thereafter, we can submit another PR to re-order. Let me know if you think this is a good idea or not necessary.

@eashaw
Copy link
Contributor

eashaw commented Jul 18, 2024

@mike-j-thomas, we should reorder the YAML in a follow-up PR to make it easier to review. I can make that change once the feature consolidation and name changes are approved/merged.

mike-j-thomas added a commit that referenced this issue Jul 23, 2024
As part of our Q2 OKR to list features that Mac Admins care about first,
we have also renamed features to make them easier to understand.

Style guide for the naming convention:
- Features should be clear, easy to read, and consistent (parallel
construction)
- Meta information should go in tooltips
- Adjectives should be avoided in the feature name and reserved for the
tooltips

More context for this PR: #20191.
Once these name changes are approved, we will follow up with the
re-ordering.

---------

Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Co-authored-by: Noah Talerman <noahtal@umich.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#g-digital-experience https://fleetdm.com/handbook/digital-experience ~website Issues related to fleetdm.com
Projects
None yet
Development

No branches or pull requests

2 participants