diff --git a/COMMUNITY-MANAGER.md b/COMMUNITY-MANAGER.md
new file mode 100644
index 00000000..cbba0830
--- /dev/null
+++ b/COMMUNITY-MANAGER.md
@@ -0,0 +1,42 @@
+# Community Manager Role
+
+Community managers are responsible for managing many aspects of the JSON Schema community. The goal is to achieve and maintain a healthy and growing JSON Schema community where everyone feels welcome and is encouraged to share knowledge and learn from each other. This document outlines the responsibilities of a community manager and the process involved in becoming one.
+
+### Responsibilities
+
+A community manager has the following responsibilities:
+
+* Manage the JSON Schema Open Community Working Meetings:
+ * Host the call.
+ * Publish the community call recording to the YouTube channel.
+* Manage the Slack community:
+ * Organize and monitor Slack channels.
+ * Ensure community rules are being followed.
+ * Help new Slack users find the right channels & answers.
+ * Announce JSON Schema updates and events.
+* Review issues & pull requests in the community repository.
+* Review and publish JSON Schema blog posts submitted by the community.
+* Report on community health, growth trends, and top issues to maintainers and STC.
+* Propose new partnerships with other adjacent communities to STC and manage them.
+* Manage community analytics tools, including Plausible and CommonRoom.io.
+* Manage the social media accounts: [@jsonschema](https://twitter.com/jsonschema) Twitter and [@jsonschema](https://twitter.com/jsonschema) and [@jsonschema](https://www.linkedin.com/company/jsonschema) Linkedin:
+ * Asking the community for community call topics.
+ * Announcing community calls (one day before and one hour before the call).
+ * Announcing that the recording of the community call is available on YouTube.
+ * Announcing JSON Schema updates like tooling or adopters.
+ * Announcing new JSON Schema blog posts.
+ * Reposting relevant tweets from the community.
+* Manage the [@JSONSchemaOrgOfficial](https://www.youtube.com/@JSONSchemaOrgOfficial) YouTube account.
+* Launch and manage Community programs.
+
+### Duties that require STC approval
+
+* Add new analytics tools
+
+### Know more
+
+Please join the `#community-mgmt` slack channel using this [link](#community-mgmt) if you like to know more.
+
+### Atribution
+
+This document has been inspared by the [DAPR Community Manager document](https://github.com/dapr/community/blob/master/COMMUNITY-MANAGER.md).
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a583438a..5dbea1b8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,16 +1,34 @@
-# Guidelines for contributing to the JSON Schema project GitHub organisation
-
-🚨 Work in progress! (2021/07 - @relequestual)
+# Guidelines for contributing to the JSON Schema Community
We invite you to join us working on JSON Schema.
-The fastest way to get involved and become active in the community is to join our Slack server at https://json-schema.org/slack.
+The fastest way to get involved and become active in the community is to join the `#contribute` channel in our Slack server at https://json-schema.org/slack.
If you have suggestions on how to improve our community, please do check out our [Community Discussions](https://github.com/json-schema-org/community/discussions), and start a new discussion.
-# General
+### Types of contributions
+
+JSON Schema is a community that lives on its contributors. As we grow, we need more people to help others. You can contribute in many ways, either in the specification development or in the wider ecosystem.
+
+Here are some areas where you can contribute:
+ * 🌱 [Specification development](https://github.com/json-schema-org/json-schema-spec)
+ * 🐞 Reporting Bugs
+ * 💡 Issues and feature requests
+ * 🧐 Reviewing PRs
+ * ❓ Answer questions
+ * 🙏 Join discussions and provide feedback
+ * 🛠️ [Add new JSON Schema tooling](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#%EF%B8%8F-add-a-new-implementation)
+ * ✍️ [Publish a blog post](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#%EF%B8%8F-publish-a-blog-post)
+ * 📈 [Publish a case study](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-publish-a-case-study)
+ * 📋 [Improving The Documentation](https://github.com/orgs/json-schema-org/projects/16)
+ * 🏗 [Website development](https://github.com/orgs/json-schema-org/projects/11/views/1)
+ * 🎨 [Improving The Design](https://github.com/json-schema-org/website/blob/main/CONTRIBUTING.md#-improving-the-design)
+ * 😍 [Collaborating with Community Management tasks](#community-management-tasks)
+ * 🚀 [Adding a new Adopter](https://github.com/json-schema-org/community/blob/main/ADOPTERS.md)
-While each repository may have its own guidance for contributing, the following sections apply organisation wide.
+#### Community management tasks
+
+To get involved in the Community management tasks, please join the [`#community-mgmt` slack channel](https://json-schema.slack.com/archives/C0209BTU2UQ).
## Key "Architectural" decisions
@@ -45,6 +63,10 @@ Once an ADR is part of a pull request which is labelled with `adr-required`, the
The process is designed to be lightweight, and a template is provided for ease of use.
+### Triage
+
+Please check the [triage process](https://github.com/json-schema-org/.github/blob/main/TRIAGE.md) to learn how we review and label incoming issues .
+
### Feedback
Feedback on this process can be made informally through our [Slack server](https://json-schema.org/slack) and formally using our [Community Discussions](https://github.com/json-schema-org/community/discussions).
diff --git a/README.md b/README.md
index 7e7d9196..55b6ed08 100644
--- a/README.md
+++ b/README.md
@@ -1,48 +1,97 @@
-# JSON Schema Community
+[](https://json-schema.org)
+
+
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
+ 
+
+
-[](https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md)
-[](https://www.repostatus.org/#active)
-[](https://opencollective.com/json-schema)
+# JSON Schema Community
-[](https://adr.github.io)
-
+Welcome to the JSON Schema community! You've arrived at the perfect place to begin your journey as a contributor. Whether it's assisting with documentation, writing a blog post, enhancing the website, delivering presentations, or any other form of contribution, there's plenty of opportunities to get involved in the project. We are a friendly, collaborative group and look forward to working together.
-# What is this repo?
+- 👋 [Introduction](#introduction)
+- 💬 [Discussions and slack](#discussions-and-slack)
+- 🗓 [Community meetings](#community-meetings)
+- 🌱 [Getting involved](#getting-involved)
+## Introduction
This repo is a place to discuss and debate various aspects of running the JSON Schema organisation, how we work as a community, and our expectations.
-The discussions will primarily take place using [Github Discussions](https://github.com/json-schema-org/community/discussions) for this repo.
+### Discussions and Slack
+
+Reach out with any questions you may have and we'll make sure to answer them as soon as possible and as a community member feel free to jump in and answer questions.
+
+JSON Schema utilizes Slack and GitHub Discussions to facilitate our communications, each serving unique purposes to support our community effectively.
+
+Slack is the go-to for lively conversations, channel announcements, one-on-one support, and immediate assistance, making real-time communication seamless and efficient. However, Slack isn't ideal for housing detailed discussions, long-term planning, or tracking the evolution of ideas and decisions.
+
+For more in-depth discussions, planning, and documenting significant decisions, we use GitHub Discussions. It allows us to work together on significant decisions more effectively and provides long standing point of reference for our discussions.
-Initially Github issues will be disabled as we evaluate how we should use them in this repo (through Discussions).
+| Platforms | Link |
+|:----------|:-------------|
+| 💬 Slack (preferred) | https://json-schema.org/slack
+| 💬 Discussions | https://github.com/orgs/json-schema-org/discussions
-Once we have some links for the community, this readme will link to various locations, resources, and documents that are useful for the community.
+### Community meetings
+We hold monthly Office Hours and weekly Open Community Working Meetings. Office Hours are every first Tuesday of the month at 15:00 BST, and by appointment. Open Community Working Meetings are every Monday at 14:00 PT.
-# Who can use this repo?
+**Office Hours (Monthly):**
-Anyone who wants to learn about, be part of, or help improve the JSON Schema community is welcome here.
+**Office Hours** provide time for the community for questions, discussions, comments, or just to chat about JSON Schema.
-Anyone can start a discussion in any category. You can even start a discussion to suggest adding a new category!
+More details [here](https://github.com/orgs/json-schema-org/discussions/34/).
-# Why do we need this repo to have discussions?
+**Open Community Working Meeting (Weekly):**
-Slack is really great for chatting, working through tricky problems, having one-to-one support sessions.
+**Open Community Working Meetings** are a 1 hour, agenda'd only, with a focus on furthering the JSON Schema specification and organization.
-Slack is not so great for long running ideas, plans, or discussions, a point of reference for decisions, keeping a log of progress.
+More details [here](https://github.com/orgs/json-schema-org/discussions/35).
-Using Github Discussions, we can collaborate on important decisions over a longer period of time and have a long standing point of reference
+You can always catch up offline by watching the recordings on the JSON Schema YouTube channel.
-# Why not just use Github Issues?
+| Asset | Link |
+|:-----------|:------------|
+| 🔗 Office Hours Meeting Link | [**Zoom Link**](https://postman.zoom.us/j/85358817067?pwd=NmFXTG5oL1paK0VyTEdrNU9TR2RMUT09)
+| 🔗 Open Community Working Meeting Link | [**Zoom Link**](https://www.google.com/url?q=https://postman.zoom.us/j/89562933116?pwd%3DOWlsQ0RrcDY4S1JQU2d2Q2M0aFFlZz09&sa=D&source=calendar&ust=1708431911262691&usg=AOvVaw14JoRXk9cLLBT-_wngWROA)
+| 🎥 Meeting Recordings | https://www.youtube.com/@JSONSchemaOrgOfficial
-Github Issues are great for getting work done, but not so great at having threaded debates and discussions.
+## Getting involved
-Picking to use Github Discussions before creating an issue allows us to seek consensus in discussion and keep Issues as the space for tracking work product and its progress.
+JSON Schema is a community that lives on its contributors. As we grow, we need more people to help others. Do you like to get involved? You can contribute in many ways!
-# Who decided all this? Is it up for debate?
+Please check out our [Contribution guidelines](CONTRIBUTING.md) to know more.
-Ben Hutton (@relequestual) created this repo and initial readme on April 2021, based on the expectations of community and organisational needs having grown, supported, and observed the community over the past 5 years.
+### Contributors
-**None of this is set in stone. Humans are fallible. Everything is up for debate.**
+Thanks goes to these wonderful people who contributed to this communtiy space:
+
+ 
+
-While Ben has become the self-appointed core team lead at some point during those 5 years, we strive to work on a model of general consensus, which works well for specification development, and is something we rely on to move us forward.
+Made with [contributors-img](https://contrib.rocks).
-Ben acts in several ways as an executive for the organisation, and feels trusted enough to make organisational decisions like this with the expectation of change and with as much transparency as possible.
+## Code of Conduct
+To get involved with our Community, please make sure you are familiar with our [Code of Conduct](https://github.com/json-schema-org/.github/blob/main/CODE_OF_CONDUCT.md).
\ No newline at end of file
diff --git a/docs/blog-guidelines.md b/docs/blog-guidelines.md
index 16cbf572..ea8b97be 100644
--- a/docs/blog-guidelines.md
+++ b/docs/blog-guidelines.md
@@ -2,7 +2,7 @@
## JSON Schema Blog Overview ##
-The JSON Schema blog serves as a channel for JSON Schema maintainers and contributors, implementation maintainers, and [Community Champions](#note-on-json-champions) to share content with the JSON Schema Community.
+[The JSON Schema blog](https://json-schema.org/blog) serves as a channel for project maintainers and contributors, implementation maintainers, and JSON Schema Champions to share content with the JSON Schema Community.
The content on our blog consists of:
* Use cases and success stories