From 1764ad0909103e5e10fb2c0d3d7e039f1fc3611c Mon Sep 17 00:00:00 2001 From: Eric Date: Tue, 20 Jun 2023 12:10:11 -0500 Subject: [PATCH] Handbook: Fix broken links in marketing handbook (#12400) Changes: - Updated three broken links in the marketing handbook. --- handbook/marketing/editor-guide.md | 2 +- handbook/marketing/website-handbook.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/handbook/marketing/editor-guide.md b/handbook/marketing/editor-guide.md index a59195901f..072ea5661e 100644 --- a/handbook/marketing/editor-guide.md +++ b/handbook/marketing/editor-guide.md @@ -51,7 +51,7 @@ We approach editing retrospectively for pull requests (PRs) to handbook pages. R Editing articles, release posts, and press releases usually comes in three flavors: a Google Docs draft, a new pull request, or an edit to an existing article. -* For unpublished articles, please read the review process in [How to submit and publish an article](./how-to-submit-and-publish-an-article#review-process). +* For unpublished articles, please read the review process in [How to submit and publish an article](https://fleetdm.com/handbook/marketing/how-to-submit-and-publish-an-article#review-process). * To edit an existing article, see [How to make edits with GitHub](#how-to-make-edits-with-github). diff --git a/handbook/marketing/website-handbook.md b/handbook/marketing/website-handbook.md index 87525a7ed0..1523f11908 100644 --- a/handbook/marketing/website-handbook.md +++ b/handbook/marketing/website-handbook.md @@ -22,7 +22,7 @@ See Marketing [intake](https://fleetdm.com/handbook/marketing#intake) for more i ## Wireframes -Before committing anything to code, we create wireframes (referred to as ["drafting"](http://localhost:2024/handbook/company/development-groups#making-changes)) to illustrate all changes that affect the layout and structure of the user interface, design, or APIs of fleetdm.com. +Before committing anything to code, we create wireframes (referred to as ["drafting"](https://fleetdm.com/handbook/company/development-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. @@ -110,7 +110,7 @@ Once you have the above follow these steps: 3. Once the script is complete, start the website server. From the `website/` folder: - **With Node.js:** start the server by running `node ./node_modules/sails/bin/sails lift` - **With Sails.js installed globally:** start the server by running `sails lift`. -4. When the server has started, the Fleet website will be availible at [http://localhost:2024](http://localhost:2024/admin/email-preview) +4. When the server has started, the Fleet website will be availible at [http://localhost:2024](http://localhost:2024) > **Note:** Some features, such as Fleet Sandbox, Self-service license dispenser, and account creation are not availible when running the website locally. If you need help testing features on a local copy, reach out to `@eashaw` in the [#g-website](https://fleetdm.slack.com/archives/C058S8PFSK0) channel on Slack..