From b29358437b7b7b0eeed5a26bc8000cd3e089d594 Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Fri, 21 Apr 2023 15:25:06 -0500 Subject: [PATCH] use consistent route prefix (#11275) --- handbook/company/why-this-way.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/handbook/company/why-this-way.md b/handbook/company/why-this-way.md index 9c52be0499..6d8cd68c42 100644 --- a/handbook/company/why-this-way.md +++ b/handbook/company/why-this-way.md @@ -38,7 +38,7 @@ Making changes to the handbook first [encourages](https://www.youtube.com/watch? > The Fleet handbook is inspired by the [GitLab team handbook](https://about.gitlab.com/handbook/about/). It shares the same [advantages](https://about.gitlab.com/handbook/about/#advantages) and will probably undergo a similar [evolution](https://about.gitlab.com/handbook/ceo/#evolution-of-the-handbook). -To contribute to the handbook, click "Edit this page" and make your [edits in Markdown](handbook/company/handbook.md). +To contribute to the handbook, click "Edit this page" and make your [edits in Markdown](https://fleetdm.com/handbook/company/handbook). ## Why the emphasis on training? @@ -100,9 +100,7 @@ Here's why Fleet uses a wireframe-first approach: - Wireframes created to describe individual changes are disposable and may have slight stylistic inconsistencies. Fleet's user interface styleguide in Figma is the source of truth for overarching design decisions like spacing, typography, and colors. - While the "wireframe first" practice is [still sometimes misunderstood](https://about.gitlab.com/handbook/product-development-flow/#but-wait-isnt-this-waterfall), today many modern high-performing teams now use a [wireframe-first methodology](https://speakerdeck.com/mikermcneil/i-love-apis), including [startups](https://www.forbes.com/sites/danwoods/2015/10/19/dont-get-ubered-apis-hold-key-to-digital-transformation/?sh=50112fea182c#:~:text=One%20recommendation%20that,deep%20experience) and [publicly-traded companies](https://about.gitlab.com/handbook/product-development-flow/#validation-phase-3-design). -_The only exception to the wireframe-first policy is for temporary pages and experiments not listed in the navigation or sitemap, and which are housed behind /landing ☁️🪟. You can read more about marketing's [experimentation process](https://fleetdm.com/handbook/marketing#experimentation)._ - -> Got a question about creating wireframes or the drafting process? Mention Noah Talerman or Luke Heath in `#help-product`. +> _**Note:** The only exception to the wireframe-first policy is for temporary pages and experiments not listed in the navigation or sitemap, and which are housed behind /imagine ☁️🪟. You can read more about marketing's [experimentation process](https://fleetdm.com/handbook/marketing#experimentation)._ ## Why do we use one repo?