Merge pull request #420 from Relequestual/home/community-links

Author: Relequestual

assets/logo-slack.svg

@@ -124,3 +124,56 @@ $content-width:    960px !default;
     font-size: 14px;
   }
 }
+
+// Minimal buttons https://github.com/vladocar/Simple-Button
+.button {
+  font-size: 1em;
+  display: block;
+  border: 0;
+  margin: 0 6px;
+  padding: 0.7em;
+  cursor: pointer;
+  text-align: center;
+  transition-duration: 0.1s;
+  transition-timing-function: linear;
+}
+.button:hover,
+.button:focus {
+  opacity: 0.8;
+}
+.btcolor {
+  background-color: red;
+  color: #fff;
+}
+.btcolor:hover,
+.btcolor:focus {
+  background: #ff6666;
+  color: #f0f0f0;
+}
+.round {
+  border-radius: 0.6em;
+}
+.pill {
+  border-radius: 1.1em / 50%;
+}
+.border {
+  border: 1px solid #1577ca;
+}
+
+// Other custom CSS
+
+.button-center {
+  display: inline-block;
+}
+.text-center {
+  text-align: center;
+}
+
+.small-svg-logo {
+  height: 1.3em;
+  width: 1.3em;
+}
+
+.wrapper.buttons {
+  margin-bottom: 10px;
+}

assets/main.scss

@@ -20,21 +20,48 @@ permalink: /
 
 </div>
 
-## New to JSON Schema?
+## What now?
 
-Learning a new specification can be daunting.
+Learn, Get help, Shape the Community, Chat, with the JSON Schema team and Community!
 
-You should read our [getting started guide](/learn/getting-started-step-by-step)!
+<div class="wrapper text-center buttons">
+    <a class="button border button-center" href="/learn/getting-started-step-by-step">👋 Getting Started</a>
+    <a class="button border button-center" href="/slack" target="_blank"><img class="small-svg-logo" src="/assets/logo-slack.svg" height="1.3em" width="1.3em"> Open JSON Schema Slack</a>
+    <a class="button border button-center" href="https://github.com/json-schema-org/community/discussions" target="_blank">💬 Community Discussions</a>
+</div>
+
+## Regular Activities
+
+We hold weekly Office Hours and twice monthly Open Community Working Meetings.
+
+<div class="wrapper text-center buttons">
+    <a class="button border button-center" href="https://github.com/json-schema-org/community/discussions/34" target="_blank">🧑‍💻 Office Hours</a>
+    <a class="button border button-center" href="https://github.com/json-schema-org/community/discussions/35" target="_blank">👷 Open Community Working Meetings</a>
+</div>
+
+Office Hours are every Tuesday at 15:00 UTC.
+
+Open Community Working Meetings follow two patterns:
+- First Friday of the month at 20:00 UTC.
+- Third Friday of the month at 15:00 UTC.
+
+## Need more?
+
+We have our other [learning resources](/learn), including the [Understanding JSON Schema documentation](/understanding-json-schema).
 
-You can also see our other [learning resources](/learn).
+## About Our Community
 
-### Got questions?
+We have an active and growing community. All are welcome to be part of our community, help shape it, or simply observe.
+
+We want to keep our community welcoming and inclusive, so please read our [JSON Schema Organizational Code of Conduct](https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md). (This is a combination of the Contributor Covenant and IETF BCP 54.)
 
 The JSON Schema team and community are here to help!
 
 At any point, feel free to join our [Slack server](/slack).
 
-We also monitor the `jsonschema` tag on StackOverflow.
+Our Slack server has limited history, so we also use [GitHub Discussions](https://github.com/json-schema-org/community/discussions).
+
+We monitor the `jsonschema` tag on StackOverflow.
 
 ## Project Status
 
@@ -47,7 +74,6 @@ so we will usually refer to `2020-12` (without the word "draft") on this web sit
 
 See the [Specification page](specification.html) for details about naming and numbering.
 
-
 ### The Path to Standardization
 
 The JSON Schema project intends to shepherd all three draft series to either: RFC status, the equivalent within another standards body, and/or join a foundation and establish self publication rules.
@@ -68,9 +94,10 @@ Internet-Drafts expire after six months, so our goal is to publish often enough
 </details>
 
 ### Use of the _draft_ designation
-
 Releases of the JSON schema specification and meta schemas use the _draft_ designation primarily for historical reasons stemming from the relationship of this specification to IETF ([explained here](https://json-schema.org/specification-links.html#understanding-draft-names-and-numbers)).
 The use of this designation is under review but will continue until this review process completes to avoid changing the designation style multiple times.
+<details markdown="1">
+<summary>Read more</summary>
 
 The JSON schema project recognizes, condones, and advocates for the use of the JSON schema standard in production.
 
@@ -79,7 +106,7 @@ Each release of the JSON schema specification is treated as a production release
 Similarly to most specifications, the JSON schema specification will continue to evolve, and not all releases will be backwards compatible. The intention, particularly for vocabularies such as validation which have been widely implemented, is to remain as compatible as possible from release to release. However, major changes can still occur given a clear enough need validated with the user community.
 
 When the _draft_ designation is dropped this may indicate that the frequency of releases and amount of changes in each release will decrease, but it won't indicate that no new releases will be made, or that all future releases will be backwards compatible.
-
+</details>
 ## Quickstart
 
 The JSON document being validated or described we call the *instance*, and the document containing the description is called the *schema*.
@@ -106,7 +133,7 @@ This allows the team to focus the little time they do donate on JSON Schema core
 
 We may revisit JSON Hyper-Schema at a later date.
 
-## More
+## More Links
 
 Interested? Check out: