From 146e081d490578a6c7e7ca6e9256a4010fcb3bac Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Sat, 29 Apr 2023 23:27:23 -0500 Subject: [PATCH] Improve link (#11442) Skip past the CRUD stuff, which might not be as obviously relevant to all contributors. --- handbook/company/why-this-way.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/company/why-this-way.md b/handbook/company/why-this-way.md index b560568fd3..8b1999ecb8 100644 --- a/handbook/company/why-this-way.md +++ b/handbook/company/why-this-way.md @@ -80,7 +80,7 @@ To check out the right person to review a given piece of content or source code ## Why do we use a wireframe-first approach? -Wireframing (usually as part of what Fleet calls ["drafting"](https://fleetdm.com/handbook/company/development-groups#making-changes)) provides a clear overview of page layout, information architecture, user flow, and functionality. The [wireframe-first approach](https://speakerdeck.com/mikermcneil/i-love-apis) extends beyond what users see on their screens. Wireframe-first is also excellent for drafting APIs, config settings, CLI options, and even business processes. +Wireframing (usually as part of what Fleet calls ["drafting"](https://fleetdm.com/handbook/company/development-groups#making-changes)) provides a clear overview of page layout, information architecture, user flow, and functionality. The [wireframe-first approach](https://speakerdeck.com/mikermcneil/i-love-apis?slide=28) extends beyond what users see on their screens. Wireframe-first is also excellent for drafting APIs, config settings, CLI options, and even business processes. It's design thinking, applied to software development.