From 56d4e596c74ddfc16dcf30539d2a2d735c3c3922 Mon Sep 17 00:00:00 2001 From: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com> Date: Wed, 16 Oct 2024 17:51:08 -0500 Subject: [PATCH] Create website-request.md (#22974) --- .github/ISSUE_TEMPLATE/website-request.md | 25 +++++++++++++++++++++++ handbook/company/communications.md | 2 +- 2 files changed, 26 insertions(+), 1 deletion(-) create mode 100644 .github/ISSUE_TEMPLATE/website-request.md diff --git a/.github/ISSUE_TEMPLATE/website-request.md b/.github/ISSUE_TEMPLATE/website-request.md new file mode 100644 index 000000000000..bd4a650ef0ad --- /dev/null +++ b/.github/ISSUE_TEMPLATE/website-request.md @@ -0,0 +1,25 @@ +--- +name: 🌐 Website request +about: Propose a new feature or enhancement to fleetdm.com. +title: 'Website request: _________________' +labels: '#g-digital-experience, ~website' +assignees: '' + +--- + +## Goal + +| User story | +|:---------------------------------------------------------------------------| +| As a _________________________________________, +| I want to _________________________________________ +| so that I can _________________________________________. + +>For help creating a user story, see ["Writing a good user story"](https://fleetdm.com/handbook/company/development-groups#writing-a-good-user-story) in the website handbook. + + +## How? + +- [ ] TODO + +### Context diff --git a/handbook/company/communications.md b/handbook/company/communications.md index 17c8ef69a5ce..49660fb744af 100644 --- a/handbook/company/communications.md +++ b/handbook/company/communications.md @@ -103,7 +103,7 @@ The docs are separated into four categories: ## Fleetdm.com -Any change to fleetdm.com follows the same process as [making changes](https://fleetdm.com/handbook/company/product-groups#making-changes) to the core product. To propose a change to Fleet's website [create a website request](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=%23g-digital-experience&projects=&template=website-request.md&title=Request%3A+__________________________) on the #g-digital-experience kanban board. +Any change to fleetdm.com follows the same process as [making changes](https://fleetdm.com/handbook/company/product-groups#making-changes) to the core product. To propose a change to Fleet's website [create a website request](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=%23g-digital-experience&projects=&template=website-request.md&title=Website%20request%3A+__________________________) on the #g-digital-experience kanban board. Before committing anything to code, we create wireframes (referred to as ["drafting"](https://fleetdm.com/handbook/company/product-groups#making-changes)) to illustrate all changes that affect the layout and structure of the user interface, design, or APIs of fleetdm.com. See [Why do we use a wireframe first approach](https://fleetdm.com/handbook/company/why-this-way#why-do-we-use-a-wireframe-first-approach) for more information.