Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Handbook: Fix broken links in marketing handbook (#12400)

Browse source 
Changes:
- Updated three broken links in the marketing handbook.
This commit is contained in:
Eric 2023-06-20 12:10:11 -05:00 committed by GitHub
parent b5e82da81b
commit 1764ad0909
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
handbook/marketing/editor-guide.md
View file

@ -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).

4
handbook/marketing/website-handbook.md
View file

@ -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..