Add community page to docs site

[nrichers]

Internal Notes for Reviewers

With our new main site still under development, I was looking for a suitable place to add the community sign-up form we can point people to. For now, this pull request adds a new "Community" page that embeds the form I demoed during the team weekly:

Behind the scenes, this is a single-line embedding of the form inside of an HTML codeblock so that Quarto passes it through. Tested and it works as expected.

External Release Notes

ValidMind is working to create a community designed to foster knowledge sharing, collaboration, and professional growth in the Model Risk Management (MRM) field. To this end, we added a new community page to our docs site where you can sign up for our MRM Community Slack space.

We invite you to join our Slack community channels, where you can discuss topics related to model risk management with others and get community support for our ValidMind products. Learn more ...

[nrichers]

@mehdi0501 this is the PR we discussed earlier today. If you could take a look, I would be much obliged. (Since our chat this morning, I moved the new "Community" section up a bit in the left sidebar, as shown in the updated screenshot.)

[mehdi0501]

Looks good. one small suggestion might be to call the page "Community Sign Up" or "Join our Community" (instead of "Community").

[nrichers]

Looks good. one small suggestion might be to call the page "Community Sign Up" or "Join our Community" (instead of "Community").

Yes, I will update the title along the lines suggested. In my mind, I was already thinking about expanding this section in the future for other community-specific activities (say, related to participating in GitHub discussions), but that's probably a bit premature. For now, let's just keep the title accurately scoped.

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation.

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation.

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation.

[github-actions]

Pull requests must include at least one of the required labels: internal, highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[github-actions]

Pull requests must include a description in the release notes section.

[github-actions]

Pull requests must include a description in the release notes section.

[nrichers]

@p-m-s-f I think there is a way to hide this bit about signing in:

The thing is, this is a CSS hack, as the CORS for the <iframe> we use to embed the form technically doesn't allow this. But you could enclose the form embed with something that essentially modifies this class. I looked into this and found some info: https://stackoverflow.com/questions/217776/how-to-apply-css-to-iframe.

Is this something we can do?

EDIT: The two classes to hide are likely these. One hides the extra horizontal line and the other hides the sign-in text.

[nrichers]

One other comment for you, @p-m-s-f : as mentioned during our standup, CORS will prevent cross-domain CSS injection, so whatever option we try out will need to modify the CSS on the fly as the form is being rendered. The challenge will be to come up with something that works across the major browsers.

[nrichers]

@p-m-s-f OK, one more comment and then I will stop meddling with your hacking. 😄 I was able to modify the form itself so that in an incognito window it doesn't show the sign-in. However, in a normal window it now says "Saving disabled" so we're still left with the need to modify the CSS on the fly to hide the associated class.

Incognito window:

Regular window:

[p-m-s-f]

@nrichers i don't see the Saving disabled text when previewing the page on my browser. i tried previewing it on an incognito window, and switching to microsoft edge, but in both cases i still didn't see it. have you tried re-rendering the page in quarto and seeing if the text persists?

[nrichers]

I see this message in FireFox, Safari, and Chrome when I am logged into my Google account, so it would affect anyone who is actively logged into Google. Here are the three browsers side by side:

have you tried re-rendering the page in quarto and seeing if the text persists?

This should have no effect on the rendering of the form, as we basically just embed the form via iframes into HTML. If the section is visible in the form, it will be visible in the rendered HTML output from the side, but the form is not rendered as part of building the site.

[p-m-s-f]

I see this message in FireFox, Safari, and Chrome when I am logged into my Google account, so it would affect anyone who is actively logged into Google.

it didn't show up when i was signed into my google account on firefox (or when i was signed out in incognito mode). i tried signing into google on microsoft edge but i'm still not seeing any change.

[nrichers]

I added a commit that lives the page available but hides it from the navigation. This way, we can enable OW sign-ups but without advertising that we have this option widely.