# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
- For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).
Changes:
- Changed the name of the `type` prop of the `<call-to-action>`
component to `preset`
- Updated `<call-to-action>` components in articles to use the new prop
name
- Updated the article formatting guide in the Handbook to document how
to use a `<call-to-action>` preset and added examples of our two
presets.
Added Jarod as the DRI for review.
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
- For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).
Changes:
- Updated the `<call-to-action>` component example in the article
formatting guide handbook page to use the correct quotation marks (`”` »
`"`)
* Updated Fleet style guide
Updated style guide and added it to a subpage.
* Fixed a couple of blockquote formatting issues
* removed h4 example
* Implementing Mike's revisions.md
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* update navigation
## The problem
After consolidating Growth, Community, and Digital Experience (Brand) under "Marketing", the side navigation has become overwhelming and unclear what sections falls into each category.
## How to fix
Since the navigation can only display top-level sections, I propose splitting the navigation as follows:
- Marketing
- Community
- Brand
- Rituals
- Slack channels
Navigating to each of these sections will then display a content table for each, labeled "In this section" (as currently exists).
To do this, I made the following changes:
- Changed heading hierarchy throughout page
- added styling to h3 to include border-top
## Caveat
Since h2 is used to define the three categories on this page (Marketing, Community, Brand), h3 tag is now utilized to define sub-sections for each of the main categories. However, this styling is specific to the Marketing page of the handbook, and should not be applied to the other pages – which I do not know how to achieve.
* add page title to purpose, add marketing page-specific styles
Co-authored-by: Eric <eashaw@sailsjs.com>
* Handbook: Marketing page edits
* Marketing pass first iteration
* Handbook: adding community support to engineering
1st iteration
* Handbook:removing community support from marketing
1st iteration
* Handbook: new section for community support
* Handbook: Marketing second pass
Added sections with section links per team.
Ask @chris-mcgillicuddy if he wants to remove the style guide sections and editing sections on this page
Updating digital experience to brand - ask @eashaw for help with link redirects
TODO: Charlie: need to check the handbook links before merging.
* Consolidating style guide
Several sections of the handbook have their own styles guides with redundant content. I'm consolidating that content into one central location.
* Update README.md
* Update README.md
* Update README.md
* Creating Marketing division of the handbook
Marketing is comprised of Community, Digital Experience, Growth, and Handbook.
* Update marketing.md
* Update and rename handbook/company/marketing.md to handbook/marketing/README.md
* Update README.md
* Rename handbook/growth/README.md to handbook/marketing/growth.md
* Rename handbook/digital-experience/README.md to handbook/marketing/digital-experience.md
* Rename handbook/digital-experience/article-formatting-guide.md to handbook/marketing/article-formatting-guide.md
* Rename handbook/digital-experience/commonly-used-terms.md to handbook/marketing/commonly-used-terms.md
* Rename handbook/digital-experience/how-to-submit-and-publish-an-article.md to handbook/marketing/how-to-submit-and-publish-an-article.md
* Rename handbook/digital-experience/markdown-guide.md to handbook/marketing/markdown-guide.md
* Rename handbook/community/README.md to handbook/marketing/community.md
* Update markdown-guide.md
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
