* generating a trial license key
* use H4s for this section
Co-authored-by: eashaw <eashaw@sailsjs.com>
* use H4s for this section
Co-authored-by: eashaw <eashaw@sailsjs.com>
Co-authored-by: eashaw <eashaw@sailsjs.com>
- Fix a broken link in the summary of the "Osquery logs" documentation
- Update instructions for linking to a specific section within a page in the Fleet documentation in product handbook
- Add outline for when a feature is placed behind a feature flag in the Fleet product
- Add items to consider when deciding if feature flags should be leveraged
* Updated product section of handbook
• Changed section heading Fleet EE to "UI design".
• Added sub-section "Design conventions" under UI design.
• Re-ordered content. I felt that QA and release process was of more importance than UI design.
* Update README.md
* add_criteria
adds agreed upon criteria for
1. version support and troubleshooting
2. freeze period definition
3. Some adjustment to the Manual QA section based on the creation of Release QA ticket templates and smoke tests.
* Update handbook/product.md
Co-authored-by: eashaw <eashaw@sailsjs.com>
Co-authored-by: eashaw <eashaw@sailsjs.com>
* addred cropped images to replace images in configuration.md, fixed duplicated alt text, added box-shadow to images
* more cropping
* reduce padding on ordered lists, point urls in markdown to where images will be
* Update 02-Configuration.md
* Update build-static-content.js
* remove box-shadow on images
* Update 02-Configuration.md
* Added handbook entry about images
* changed img tags to markdown links to be consistent
* undo small style change
* Update build-static-content.js
* Update handbook/product.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Update growth.md
Added a section for Fleet blog post authors about how to promote their blog posts to our social media.
Some thoughts. Including an assignee is not very future proof, in case roles change etc. Maybe best to leave that out, and we can add an assignee when we see the issue in Growth meetings.
HackerNews reserved for release posts only. Added that based on recent recommendation, due to HackerNew's strict policies. Are we happy with that, or should promoting on HackerNews be treated case-by-case?
* Update growth.md
* Update growth.md
* Update growth.md
* Update growth.md
* uncomment handbook route, disable redirect, add link to top nav
* Handbook page, note: most of this is directly copied from the docs, build handbook
* added maintainer <meta> tags
* handbook styles
* handbook broken up into different files
* update handbook layout
* updating markdown files
* handbook layout, adjusted header margins to make room for handbook
* handling links to specific sections in markdown compilation
* lint fixes
* commented out search bar for now
* cleaned up page script
* update handbook and clean up styles
* Delete handbook.md
* updated product content from latest version
* clean up styles, remove hardcoded image widths
* markdown updates
* title and description for /handbook, removed commented out route
* fix styles on firefox, remove commented logs
* lint fix
* update class name
* fix broken link
* updated how hashes are handled in links, adjusted links in handbook
* lint fix
* updated function names, removed comments, small markdown syntax fix
* move handbook link into footer
* Pack location
Future-proofing instructions for ease of onboards by adding location information.
* Label queries are immutable (addition)
Previous document made it seem users should be able to edit label queries.
* removal of all non-preview tasks
Non-preview tasks will be moved to /docs/3-Contributing/2-Testing.md. Additional changes include clarifications to the testing steps.
* update link
* Update manual-qa.md
* Handbook - Adding links to Fleet docs
Instructions for how to add, and fix links in the Fleet docs.
* Update handbook/README.md
* Update handbook/README.md
typo fix.
* Update handbook/README.md
Added paragraph about linking to other docs pages using relative paths.
* Update handbook/README.md
- Commented out the following e2e tests because they're consistently failing in the GitHub CI:
- Delete a host from the **Host details** page
- Query a host from the **Host details** page
- As a global maintainer, delete a host
- Add coverage for the commented out tests in the manual QA doc
- Add item and link to all "Reported bugs" (GitHub issues with the "bug" and ":reproduce" label). This way, the individual on call can navigate to a list of bugs that need reproduction.
- Add a link to the open pull requests. This way, the individual on call can identify any PRs that have been opened by the community.
* Updated to handbook
Added "Communicating design changes to Engineering" section to the handbook.
* Review changes
Blockquote for note. Header for unplanned changes.
* Add safe mkdirall and open
* Use secure as much as possible and merge gomodules for orbit to fleet
* Improve openfile and mkdirall to check for permissiveness instead of equality
* Don't shift
* Fix links
* Address review comments
- Remove changes files that were collected during the 4.1.0 release cycle
- Add removing changes files step to release process documentation
- Update support process docs to reflect the change to discussing the last on-call rotation at 🍽️ Daily standup meeting
