* Renamed Brand to be Digital experience
@eashaw and I changed this to be titled Digital experience.
* Capitalized Digital Experience in handbook/digital-experience/README.md
* Capitalized Digital Experience in handbook/digital-experience/README.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Done as per @mikermcneil's request in Slack
mikermcneil
@Desmi Dizney
can you update this slack channel in the relevant handbook to reflect this? https://fleetdm.slack.com/archives/C03MMC90MNU/p1658798689913439
mikermcneil
has renamed the channel from "help-operations" to "help-operations-and-contract-reviews"
A timeboxed workaround for an intermittent issue where the mergefreeze API reports that a repo is frozen: false, when the mergefreeze UI says that it is actually truly frozen.
Turns out the issue being debugged in https://github.com/fleetdm/fleet/pull/6906 was in the API itself-- somehow it can get stuck on frozen: false. If that happens, the solution is to freeze/unfreeze everything in the dashboard
* Tool: Bring back mergefreeze API integration
Context: https://github.com/fleetdm/fleet/pull/5628#issuecomment-1196175485
Unfortunately, the API doesn't work.
* Lay out how this would work in the database - but instead, do it ephemerally for now
* Remove model
* Maintain state (the easy way for now)
* create a MainContent and SidePanelContent containers for layout
this creates these two new components for handling layout more cleanly. It also allows us to put in common components into main layout, like sandbox expiration notification
* use MainContent and SidePanelContent in current pages
this brings in the two new components and wraps the page contents in these. This also allowed us to clean up and remove unused/no needed styling code
* add MainContent component to user settings page and clean up user settings component
this cleans up the user settings page to follow the panel convention we have as well as adds the MainContent component to this page
* add MainContent component to team pages
* update Sandbox gate to render optional component when in sandbox mode and add to MainContent
* add call to sandbox api to get expiry time
this adds a conditional call when the user is in sandbox mode to get the expiry time of the instance
* fix sticky elements on settings pages to work with sandbox expiry message
* fix e2e test after MainContent refactor
It's been a few months now and, while neat to share the story, some visitors report experiencing it as an indicator that Fleet is an earlier stage company than it actually is, which is misleading.
We're not THAT hip.
This updates the documentation of orbit/pkg/packaging mainly to note that the exported functions are not safe for concurrent usage (subject to change.)
* Website: add support for excludePageFromSectionIndex meta tag in Markdown content
* revert articles and docs changes
* move handbook pages into subfolders, rename brand to digital experience, update links
* update page script, add pages in same section to generated index
* remove newline
* add redirect for renamed handbook page (/handbook/brand -> /handbook/digital-experience)
* handbook: update relative page links
* update comment
* Update basic-handbook.page.js
* Revert .sailsrc change
* Update basic-handbook.ejs
* Update basic-handbook.page.js
* Update basic-handbook.page.js
* Update security.md
I added an example of how second-level sections could be introduced (linked to).
* update links on security.md, remove related pages
* change top level files filenames to README.md
* remove handbookSection
* Update basic-handbook.page.js
* only include top level pages in handbook index
* update relative links
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
* Website: Follow up to strip leading slashes
re https://github.com/fleetdm/fleet/pull/6796#issuecomment-1193054810
* remove log
* Verified: whitespace trim not needed
And leading slash trim is only needed if using a regex route (not something I recommend most of the time). But since we are using one, I included it, and put it in all three places for consistency. (It doesn't ever hurt)
* update image on podcast ep3
- Updated image on the-future-of-device-management-ep3.md
- Updated title for consistency on the-future-of-device-management-ep1.md
* Fixed meta name article title to "episode 3"
Co-authored-by: Tim Kern <tim@fleetdm.com>
Gabriel Hernandez