From 5222a67a2ee2f4e9cd763fdae24aeb4b1b4c1525 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Thu, 4 Nov 2021 11:03:59 +0000 Subject: [PATCH 1/4] Migrated content about draft notation inside an expandable details element --- index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/index.md b/index.md index 97269dce..ea8d289f 100644 --- a/index.md +++ b/index.md @@ -68,9 +68,10 @@ Internet-Drafts expire after six months, so our goal is to publish often enough ### 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. +
+Read more The JSON schema project recognizes, condones, and advocates for the use of the JSON schema standard in production. @@ -79,7 +80,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. - +
## Quickstart The JSON document being validated or described we call the *instance*, and the document containing the description is called the *schema*. From ea2ace2f18fee8d1f6401a9990e29381189cbc45 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Thu, 4 Nov 2021 13:42:41 +0000 Subject: [PATCH 2/4] Highlight and link to community discussions, regular calls, and our slack server. Resolves #98 Resolves #99 Resolves #100 --- assets/logo-slack.svg | 1 + assets/main.scss | 53 +++++++++++++++++++++++++++++++++++++++++++ index.md | 44 +++++++++++++++++++++++++++-------- 3 files changed, 89 insertions(+), 9 deletions(-) create mode 100644 assets/logo-slack.svg diff --git a/assets/logo-slack.svg b/assets/logo-slack.svg new file mode 100644 index 00000000..69a4eb6a --- /dev/null +++ b/assets/logo-slack.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/assets/main.scss b/assets/main.scss index 39e9a030..9e965232 100644 --- a/assets/main.scss +++ b/assets/main.scss @@ -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; +} \ No newline at end of file diff --git a/index.md b/index.md index ea8d289f..5392fa11 100644 --- a/index.md +++ b/index.md @@ -20,21 +20,48 @@ permalink: / -## 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)! +
+ 👋 Getting Started + Open JSON Schema Slack + 💬 Community Discussions +
+ +## Regular Activities + +We hold weekly Office Hours and twice monthly Open Community Working Meetings. + +
+ 🧑‍💻 Office Hours + 👷 Open Community Working Meetings +
+ +Office Hours are every Tuesday at 15:00 UTC. -You can also see our other [learning resources](/learn). +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. -### Got questions? +## Need more? + +We have our other [learning resources](/learn), including the [Understanding JSON Schema documentation](/understanding-json-schema). + +## About Our Community + +We have an active and growing community. All are welcome to be part of our community, help shape it, or simply observe. + +We want 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). +At any point, feel free to join our Slack server. [Slack server](/slack). + +Our Slack server has limited history, so we also use [GitHub Discussions](https://github.com/json-schema-org/community/discussions). -We also monitor the `jsonschema` tag on StackOverflow. +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. @@ -107,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: From b8146af7a811e1f54c70caeaef1a645f1efa3c01 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Tue, 9 Nov 2021 09:11:21 +0000 Subject: [PATCH 3/4] Undo accidental repetition Co-authored-by: Jason Desrosiers --- index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.md b/index.md index 5392fa11..e065360f 100644 --- a/index.md +++ b/index.md @@ -57,7 +57,7 @@ We want keep our community welcoming and inclusive, so please read our [JSON Sch The JSON Schema team and community are here to help! -At any point, feel free to join our Slack server. [Slack server](/slack). +At any point, feel free to join our [Slack server](/slack). Our Slack server has limited history, so we also use [GitHub Discussions](https://github.com/json-schema-org/community/discussions). From 46e2c5c14ec3b805548e9e701ce89b70ff215187 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Tue, 9 Nov 2021 09:12:22 +0000 Subject: [PATCH 4/4] Correct grammar Co-authored-by: Jason Desrosiers --- index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.md b/index.md index e065360f..7e4087dd 100644 --- a/index.md +++ b/index.md @@ -53,7 +53,7 @@ We have our other [learning resources](/learn), including the [Understanding JSO We have an active and growing community. All are welcome to be part of our community, help shape it, or simply observe. -We want 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.) +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!