Implement custom global header banner by pgayvallet · Pull Request #87438 · elastic/kibana

pgayvallet · 2021-01-06T08:46:08Z

Summary

This PR Implements the phase 1 of #17298. By adding a new banners plugin that allows users to define a static banner appearing on all page of Kibana.

Screenshots

Login

Stretch to height pages

Scrollable pages

Checklist

Documentation was added for features that require explanation or tutorials
Unit or functional tests were updated or added to match the most common scenarios
This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
This was checked for cross-browser compatibility

Technical implementation

During the discussions in #17298, we came to the agreement to use uiSettings as the underlying implementation of the banner's configuration.

However, I missed two important facts at this time:

user-overrides (TIL: even ones done via kibana.yml, I thought it was only the ones done via the UI), are not exposed on unauthenticated pages.
when a setting is overridden in kibana.yml, it will always be used. You can't do per-space overrides in that case. Meaning that a uiSettings-only implementation would not have been possible when we would be implementing stage 2.

Given that, I decided to go with a more classic plugin-configuration-based approach for phase1, as we don't need any way to set the global banner configuration via the UI.

Phase 2 will use uiSettings for the per-space banner overrides, which will also allow, with some logic in the middle, to fallback to the global banner configuration, which was not possible with uiSettings.

Also, xpack.banners.placement: 'header' is just a better end user experience than uiSettings.overrides.banner:placement: 'header' when it comes to configuring the banner imho.

Design implementation

There were 3 main tasks here:

Adapt the styles of the Kibana header when the banner is enabled to add an appropriate top offset. This is done in src/core/public/chrome/ui/header/_banner.scss
Adapt the usages of euiHeaderAffordForFixed to add the banner's height to the body/container offset when the banner is present. Done (mostly) in src/core/public/rendering/_base.scss
Adapt all the hardcoded height: calc(100vh - #{$headerHeightOffset}); in various scss files to use a new banner-aware mixin instead.

Release Note

The new banners plugin allows to display a static banner at the top of every page of Kibana. The plugin can be configured via the kibana.yml config file

xpack.banners:
  placement: 'header'
  textContent: 'Production environment - Proceed with **special** levels of caution'
  textColor: '#FF0000'
  backgroundColor: '#CC2211'

This is a gold+ feature, and is disabled on lower license levels.

…banners

pgayvallet

Self review (please read the technical implementation section of this issue first)

pgayvallet · 2021-02-05T17:17:23Z

src/core/public/_mixins.scss

+/* stylelint-disable-next-line length-zero-no-unit -- need consistent unit to sum them */
+@mixin kibanaFullBodyHeight($additionalOffset: 0px) {


The linter complains about units on zero values, but AFAIK you cannot sum non consistent values in sass, so I had to disable the rule for the two mixin signatures.

We could probably maneuver around this to avoid the need for the disable line, but then we end up with more 'stuff' for a very minimal gain. I prefer the clarity here of what is implied by the default value, as well.

pgayvallet · 2021-02-05T17:30:22Z

src/core/public/chrome/types.ts

+  /**
+   * Set the banner that will appear on top of the chrome header.
+   *
+   * @remarks Using `undefined` when invoking this API will remove the banner.
+   */
+  setHeaderBanner(headerBanner?: ChromeUserBanner): void;
+}
+


I moved the chrome types to their own file. The only addition is ChromeStart.setHeaderBanner and InternalChromeStart.getBodyClasses$

pgayvallet · 2021-02-05T17:52:07Z

src/core/public/chrome/ui/header/_banner.scss

+.kbnBody--hasHeaderBanner .header__bars {
+  .header__firstBar {
+    top: $kbnHeaderBannerHeight;
+  }
+  .header__secondBar {
+    top: $kbnHeaderBannerHeight + $euiHeaderHeightCompensation;
+  }
+}


This overrides the .euiHeader--fixed and .euiHeader--fixed + .euiHeader--fixed styles when the banner is present

We can also revisit this once the page layout service is available.

pgayvallet · 2021-02-05T17:53:51Z

src/core/public/chrome/ui/header/header.tsx

+      <>
+        <LoadingIndicator loadingCount$={observables.loadingCount$} showAsBar />
+        <HeaderTopBanner headerBanner$={observables.headerBanner$} />
+      </>


We need to display the banner even when chrome is hidden. I did not override the LoadingIndicator styles in this situation, so the loader appears on the banner in chromeless pages, but I think this is alright.

pgayvallet · 2021-02-05T17:56:29Z

src/core/public/rendering/_base.scss

+.coreSystemRootDomElement {
+  @include euiHeaderAffordForFixed($kbnHeaderOffset);
+
+  &.kbnBody--hasHeaderBanner {
+    @include euiHeaderAffordForFixed($kbnHeaderOffsetWithBanner);
+  }
+}


Linter forbid to use tagName based rules. .coreSystemRootDomElement is just body

pgayvallet · 2021-02-05T18:06:17Z

src/plugins/advanced_settings/public/management_app/lib/to_editable_config.ts

-    readonly: !!def.readonly,
+    readOnly: !!def.readonly,


There was an undetected typo here, as conf was not explicitly typed and as readOnly is optional.

Note that this didn't have any effect because the fields are already filtered by !readonly in an earlier stage anyway.

pgayvallet · 2021-02-05T18:08:28Z

src/plugins/home/public/application/components/_home.scss

+@import '../../../../../core/public/mixins';
+
 .homWrapper {
+  @include kibanaFullBodyMinHeight();
  background-color: $euiColorEmptyShade;
  display: flex;
  flex-direction: column;
-  min-height: calc(100vh - #{$euiHeaderHeightCompensation});
 }


I went with explicit imports because this is imho the way to go. But if @elastic/kibana-design thinks it's better to have these mixins in src/core/public/core_app/styles/_mixins.scss instead and use implicit imports, I can change it.

I think it's good that we exercise caution before adding to the ...public/core_app/styles/ directory since that stuff all gets built and prepended to .scss imports, but the stuff being added by this PR feels appropriate given it's global nature.

If I'm following correctly, this means we could move the _core.scss and _variables.scss files and combine the _mixins.scss files from .../public/ to .../public/core_app/styles/ and remove all the direct imports? I think the import of the header variables atop the _variables.scss file could also then be removed.

Let me know if I'm missing other pitfalls in doing this, but it seems like a cleaner way to go and I sense it will reduce the likelihood of redundant variable imports and such in the future.

Any thoughts on my prior comment? Overall, a minor item that I wouldn't block merging on.

Sorry, I missed that one.

If I'm following correctly, this means we could move the _core.scss and _variables.scss files and combine the _mixins.scss files from .../public/ to .../public/core_app/styles/ and remove all the direct imports?

Yea. I need to confirm the consequences of doing that regarding core internal scss imports / hierarchy, but that would be the idea.

I will take a shot at it, and if it's too complicated, I will do it during phase 2

pgayvallet · 2021-02-05T18:13:06Z

x-pack/plugins/banners/public/plugin.tsx

+    if (this.config.placement !== 'disabled') {
+      getBannerInfo(http).then(
+        ({ allowed, banner }) => {
+          if (allowed) {
+            chrome.setHeaderBanner({


I expose placement to the client-side config to avoid performing an http call when the feature is soft-disabled (which would be 99.9% of our customers, realistically)

This may have to change with stage 2, at least when within a space, as we'll need the space-relative configuration, but that was an easy optimisation for now, and we can change that later if we need to

pgayvallet · 2021-02-05T18:16:14Z

x-pack/plugins/banners/server/routes/info.ts

+      return res.ok({
+        body: {
+          allowed,
+          banner: config,
+        } as BannerInfoResponse,
+      });


TIL: license info is now available when security is on and user is not authenticated. I need to have my own unauthenticated endpoint to return to the client the info about the license level.

To minimize info leak, I'm just returning a boolean, so I think it's ok (and we don't really have any other option anyway to display that thing on all pages).

pgayvallet · 2021-02-05T18:16:55Z

x-pack/plugins/banners/server/ui_settings.ts

+// Note: unused for now, will be used for v2 (see https://github.com/elastic/kibana/issues/17298)
+
+export const registerSettings = (uiSettings: UiSettingsServiceSetup) => {
+  uiSettings.register({
+    'banner:placement': {
+      name: i18n.translate('xpack.banners.settings.placement.title', {


I kept them in the PR, even if those will not be used until stage 2. I can revert these files if we really want to.

I'd vote for removing them for now until we need them in stage 2. since we might want to change some details anyways.

pgayvallet · 2021-02-09T08:37:03Z

@alexfrancoeur

Were the changes on the height of the banner applied? Did we land on a "compact mode" option or a smaller default?

No, waiting on input here. Realistically if we want to have a chance to see this lands in 7.12, the smaller default is the only option, but I need to know the expected banner height and text-size.

(adding the option for the user to choose between regular and compact could be done later, even if tbh this is adding an extra layer of complexity in an already global-impacting niche feature)

Not a deal breaker for me, but is markdown meant to be supported? We discussed early on, and I thought we landed on yes, but it doesn't seem to be working

Totally forget to implement that. There should be a markdown component already existing somewhere, so it may be trivial.

EDIT: done, 094223e

Full screen mode persists the banner, I would think that's what we want for expected behavior. Right @mbarretta ?

I'll let him answer, but I guess it would be a yes. However I see that in fullscreen mode, the banner is overlapping on the content. I guess I need to fix that.

Technically, this is because in fullscreen mode, we no longer have the euiBody--headerIsFixed class on body. I think we will need to totally get rid of the EUI mixin and copy/adapt our own to also support the banner presence when the EUI header is not present / not fixed.

I tried to break it. A long latin paragraph. Should we limit a certain amount of text and provide a warning?

Can do that. Not sure how to display the warning though? I don't think we can do better than in the server logs at startup.

An exported report does not have the banner persisted

I honestly have no idea what reporting is altering when navigating with their headless. It could even be a distinct media target. This one may be hard if we want to display the banner here.

…banners

pgayvallet · 2021-02-09T11:15:49Z

Markdown added 094223e
Overlap in fullscreen mode fixed ca0babc

…banners

alexfrancoeur · 2021-02-09T13:46:23Z

No, waiting on input here. Realistically if we want to have a chance to see this lands in 7.12, the smaller default is the only option, but I need to know the expected banner height and text-size.

++ on a smaller default without any config for 7.12. @ryankeairns any thoughts / suggestions?

Totally forget to implement that. There should be a markdown component already existing somewhere, so it may be trivial.

Woah, awesome! Thanks Pierre

I'll let him answer, but I guess it would be a yes. However I see that in fullscreen mode, the banner is overlapping on the content. I guess I need to fix that.

++ I agree that it should probably be there, thanks for fixing the overlapping content.

Can do that. Not sure how to display the warning though? I don't think we can do better than in the server logs at startup.

Yeah, server logs feel like the only option here. I wonder if it's worth it though. Maybe we just add a recommended character limit in the docs?

I honestly have no idea what reporting is altering when navigating with their headless. It could even be a distinct media target. This one may be hard if we want to display the banner here.

Yeah, let's not worry about this now and see if folks ask for this later.

mbarretta · 2021-02-09T14:36:07Z

No, waiting on input here. Realistically if we want to have a chance to see this lands in 7.12, the smaller default is the only option, but I need to know the expected banner height and text-size.

++ on a smaller default without any config for 7.12. @ryankeairns any thoughts / suggestions?

Been slow to respond, but I'm also happier with the smaller default. I just mentioned in this comment that we've been giving people a plugin with the height set to 24px. Not suggesting this must be the value, but generally smaller is better for my users' use case

Totally forget to implement that. There should be a markdown component already existing somewhere, so it may be trivial.

Woah, awesome! Thanks Pierre

++ nice!

I'll let him answer, but I guess it would be a yes. However I see that in fullscreen mode, the banner is overlapping on the content. I guess I need to fix that.

++ I agree that it should probably be there, thanks for fixing the overlapping content.

Yes, agree that it should be present when in full screen mode. If LOE is high, and implementing it risks kicking this out of the next release, I'd be ok with it being marked as a known issue.

Can do that. Not sure how to display the warning though? I don't think we can do better than in the server logs at startup.

Yeah, server logs feel like the only option here. I wonder if it's worth it though. Maybe we just add a recommended character limit in the docs?

Considering much depends on the client's screen size, a general note in the docs about the wrapping behavior and implications is probably enough.

...maybe even white-space: nowrap?

I honestly have no idea what reporting is altering when navigating with their headless. It could even be a distinct media target. This one may be hard if we want to display the banner here.

Yeah, let's not worry about this now and see if folks ask for this later.

++
This is the same as full screen mode. The banner should be displayed everywhere, even on printed reports, but think we can push forward, mark it as a known issue, and tackle in the future.

ryankeairns · 2021-02-09T15:28:24Z

Replied about the height here: #87438 (comment)
The smaller default is all good by me. Let's compromise and make it 32px, so $euiSizeXL

VijayDoshi · 2021-02-09T19:39:58Z

This is great, many customers will be happy!

…banners

pgayvallet · 2021-02-10T07:09:40Z

Changed the banner height to $euiSizeXL. Just wondering if the text doesn't look 'too fat' now? It's currently 16px, is that alright or should we decrease it a little?

Only waiting for a review from @elastic/kibana-design now

mbarretta · 2021-02-10T14:27:53Z

It's currently 16px, is that alright or should we decrease it a little?

Looks good to me, but I'm not renowned for my aesthetic eye

ryankeairns · 2021-02-10T14:31:28Z

Changed the banner height to $euiSizeXL. Just wondering if the text doesn't look 'too fat' now? It's currently 16px, is that alright or should we decrease it a little?

Yeah, let's make it a bit smaller. Try $euiFontSizeS (14px).

ryankeairns

I ran through the apps in left nav, clicked through the header, opened any flyouts I could find, etc. Everything work as expected although I don't have 100% everything enabled and am using only sample data. I feel comfortable with where things stand and only left a couple of comments.

Great work @pgayvallet !

ryankeairns · 2021-02-10T15:25:44Z

src/core/public/_mixins.scss

+/* stylelint-disable-next-line length-zero-no-unit -- need consistent unit to sum them */
+@mixin kibanaFullBodyHeight($additionalOffset: 0px) {


We could probably maneuver around this to avoid the need for the disable line, but then we end up with more 'stuff' for a very minimal gain. I prefer the clarity here of what is implied by the default value, as well.

ryankeairns · 2021-02-10T15:26:47Z

src/core/public/chrome/ui/header/_banner.scss

+.kbnBody--hasHeaderBanner .header__bars {
+  .header__firstBar {
+    top: $kbnHeaderBannerHeight;
+  }
+  .header__secondBar {
+    top: $kbnHeaderBannerHeight + $euiHeaderHeightCompensation;
+  }
+}


We can also revisit this once the page layout service is available.

ryankeairns · 2021-02-10T15:30:34Z

src/plugins/home/public/application/components/_home.scss

+@import '../../../../../core/public/mixins';
+
 .homWrapper {
+  @include kibanaFullBodyMinHeight();
  background-color: $euiColorEmptyShade;
  display: flex;
  flex-direction: column;
-  min-height: calc(100vh - #{$euiHeaderHeightCompensation});
 }


Any thoughts on my prior comment? Overall, a minor item that I wouldn't block merging on.

…banners

alexfrancoeur · 2021-02-10T17:54:30Z

Dropping a note here. When we merge this we'll want to open an issue in the Cloud repo to whitelist the config.

…banners

kibanamachine · 2021-02-11T09:07:37Z

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`advancedSettings`	56	57	+1
`banners`	-	18	+18
`core`	444	446	+2
total			+21

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`advancedSettings`	919.5KB	920.1KB	+625.0B
`discover`	420.8KB	424.6KB	+3.9KB
`home`	182.9KB	184.9KB	+2.1KB
`security`	724.4KB	724.9KB	+560.0B
`spaces`	41.2KB	41.5KB	+268.0B
total			+7.3KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
`banners`	-	13.6KB	+13.6KB
`core`	467.9KB	475.6KB	+7.7KB
`kibanaOverview`	45.0KB	46.9KB	+1.8KB
`maps`	139.0KB	140.5KB	+1.5KB
`painlessLab`	22.2KB	24.0KB	+1.8KB
`searchprofiler`	45.7KB	47.4KB	+1.7KB
total			+28.1KB

History

💚 Build #105626 succeeded 3548954
💚 Build #105479 succeeded b11b1a9
💛 Build #105140 was flaky 52993f0
💔 Build #105095 failed ca0babc
💚 Build #105074 succeeded 4cfbea7

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

* first draft * update plugin list * fix tsproject * update bundle limits file * remove unused start dep * adapt imports * POC of footer banner * update styles, mostly * plug banner to uiSettings * adding some unit tests * add tests on sort_fields * cleanup sums in sass mixins * some self review stuff * update generated doc * add tests for color field * update chrome header test snapshots * retrieve license info from the server * switch from uiSettings to plugin config * update plugin list description * update default colors * NIT * add markdown support * fix banner overlap in fullscreen mode * change banner height to 32px * change banner's font size to 14 * delete unused uiSettings

* master: (44 commits) [APM] Add experimental support for Data Streams (elastic#89650) [Search Session] Control "Kibana / Search Sessions" management section by privileges (elastic#90818) [Lens] Median as default function (elastic#90952) Implement custom global header banner (elastic#87438) [Fleet] Reduce permissions. (elastic#90302) Update dependency @elastic/charts to v24.5.1 (elastic#89822) [Create index pattern] Can't create single character index without wildcard (elastic#90919) [ts/build_ts_refs] add support for --clean flag (elastic#91060) Don't clean when running e2e tests (elastic#91057) Fixes track_total_hits in the body not having an effect when using search strategy (elastic#91068) [Security Solution][Detections] Adds list plugin Saved Objects to Security feature privilege (elastic#90895) Removing the code plugin entirely for 8.0 (elastic#77940) chore(NA): move the instruction to remove yarn global bazelisk package into the first place on install bazel tools (elastic#91026) [jest/ci] remove max-old-space-size override to use 4gb default (elastic#91020) [Fleet] Restrict integration changes for managed policies (elastic#90675) [CI] Fix auto-backport condditions so that it doesn't trigger for other labels (elastic#91042) [DOCS] Uses variable to refer to query profiler (elastic#90976) [App Search] Relevance Tuning logic listeners (elastic#89461) [Metrics UI] Fix saving/loading saved views from URL (elastic#90216) Limit cardinality of transaction.name (elastic#90955) ...

* first draft * update plugin list * fix tsproject * update bundle limits file * remove unused start dep * adapt imports * POC of footer banner * update styles, mostly * plug banner to uiSettings * adding some unit tests * add tests on sort_fields * cleanup sums in sass mixins * some self review stuff * update generated doc * add tests for color field * update chrome header test snapshots * retrieve license info from the server * switch from uiSettings to plugin config * update plugin list description * update default colors * NIT * add markdown support * fix banner overlap in fullscreen mode * change banner height to 32px * change banner's font size to 14 * delete unused uiSettings

m-adams · 2021-03-05T13:31:04Z

Great to see this, looking forward to the settings being whitelisted so we can try it in staging.

first draft

e6c632b

pgayvallet mentioned this pull request Jan 6, 2021

Customizable Header and Footer Banners #17298

Open

4 tasks

pgayvallet added 10 commits January 6, 2021 10:05

update plugin list

39c6859

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

e344a9b

…banners

fix tsproject

acbfc71

update bundle limits file

0a4b19d

remove unused start dep

f01e496

adapt imports

e5764f0

POC of footer banner

a927ee4

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

9599686

…banners

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

fd76c9f

…banners

update styles, mostly

b8c99c5

pgayvallet changed the title ~~Implement custom footer and header banners~~ Implement custom global header banner Feb 5, 2021

plug banner to uiSettings

e2fc491

pgayvallet added Team:Core Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t// v7.12.0 release_note:feature Makes this part of the condensed release notes labels Feb 5, 2021

pgayvallet added 11 commits February 5, 2021 09:30

adding some unit tests

f00a2d9

add tests on sort_fields

5076d7c

cleanup sums in sass mixins

a6421fd

some self review stuff

1e7ba75

update generated doc

863da69

add tests for color field

2ff7d47

update chrome header test snapshots

b2d8405

retrieve license info from the server

fe4ac8f

switch from uiSettings to plugin config

01e7739

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

331a3f9

…banners

update plugin list description

a9fadd2

pgayvallet commented Feb 5, 2021

View reviewed changes

pgayvallet marked this pull request as ready for review February 5, 2021 18:31

pgayvallet added 3 commits February 9, 2021 11:46

add markdown support

094223e

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

4cfbea7

…banners

fix banner overlap in fullscreen mode

ca0babc

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

52993f0

…banners

pgayvallet added 2 commits February 10, 2021 08:05

change banner height to 32px

e28b881

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

b11b1a9

…banners

ryankeairns self-requested a review February 10, 2021 15:24

change banner's font size to 14

d289b6e

ryankeairns approved these changes Feb 10, 2021

View reviewed changes

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

3548954

…banners

pgayvallet added 2 commits February 11, 2021 07:59

Merge remote-tracking branch 'upstream/master' into kbn-17298-kibana-…

4c76c96

…banners

delete unused uiSettings

3eb712e

pgayvallet merged commit 570dcc0 into elastic:master Feb 11, 2021

pgayvallet mentioned this pull request Feb 11, 2021

[7.x] Implement custom global header banner (#87438) #91089

Merged

alexfrancoeur mentioned this pull request Mar 15, 2021

[Documentation] Custom Global Header Banners #94635

Closed

		/* stylelint-disable-next-line length-zero-no-unit -- need consistent unit to sum them */
		@mixin kibanaFullBodyHeight($additionalOffset: 0px) {

Conversation

pgayvallet commented Jan 6, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Screenshots

Checklist

Technical implementation

Design implementation

Release Note

Uh oh!

pgayvallet left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ryankeairns Feb 5, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ryankeairns Feb 10, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pgayvallet commented Feb 9, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pgayvallet commented Feb 9, 2021

Uh oh!

alexfrancoeur commented Feb 9, 2021

Uh oh!

mbarretta commented Feb 9, 2021

Uh oh!

ryankeairns commented Feb 9, 2021

Uh oh!

VijayDoshi commented Feb 9, 2021

Uh oh!

pgayvallet commented Feb 10, 2021

Uh oh!

mbarretta commented Feb 10, 2021

Uh oh!

ryankeairns commented Feb 10, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ryankeairns left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ryankeairns Feb 10, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pgayvallet commented Jan 6, 2021 •

edited

Loading

ryankeairns Feb 5, 2021 •

edited

Loading

ryankeairns Feb 10, 2021 •

edited

Loading

pgayvallet commented Feb 9, 2021 •

edited

Loading

ryankeairns commented Feb 10, 2021 •

edited

Loading

ryankeairns Feb 10, 2021 •

edited

Loading