惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

月光博客
月光博客
Martin Fowler
Martin Fowler
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Stack Overflow Blog
Stack Overflow Blog
C
Check Point Blog
阮一峰的网络日志
阮一峰的网络日志
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
B
Blog
O
OpenAI News
云风的 BLOG
云风的 BLOG
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
L
LangChain Blog
V
Vulnerabilities – Threatpost
P
Privacy & Cybersecurity Law Blog
Microsoft Azure Blog
Microsoft Azure Blog
H
Help Net Security
博客园 - 三生石上(FineUI控件)
C
Cyber Attacks, Cyber Crime and Cyber Security
N
News | PayPal Newsroom
The Register - Security
The Register - Security
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
T
Threat Research - Cisco Blogs
C
Cisco Blogs
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Vercel News
Vercel News
宝玉的分享
宝玉的分享
T
Tailwind CSS Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Attack and Defense Labs
Attack and Defense Labs
人人都是产品经理
人人都是产品经理
S
Security Affairs
爱范儿
爱范儿
Engineering at Meta
Engineering at Meta
T
Tor Project blog
大猫的无限游戏
大猫的无限游戏
L
Lohrmann on Cybersecurity
aimingoo的专栏
aimingoo的专栏
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
博客园 - 【当耐特】
V
V2EX
V
Visual Studio Blog
The GitHub Blog
The GitHub Blog
雷峰网
雷峰网
WordPress大学
WordPress大学
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
L
LINUX DO - 最新话题
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Schneier on Security
Schneier on Security
小众软件
小众软件
PCI Perspectives
PCI Perspectives

Sanity.io

A Board Game agent built using Sanity Context and Vercel's AI SDK | Sanity Build a prototype with Claude Code that your whole team can edit | Sanity What’s New - May 2026 | Sanity I built a London pub guide with v0 and the Sanity MCP in six hours. Here's what I learned. | Sanity Build a conference concierge with Agent Context and Anthropic | Sanity Build a content-aware Telegram agent with Vercel AI SDK and Chat SDK | Sanity How I used Agent API to generate photos for my family’s recipes | Sanity What’s New April - 2026 | Sanity Better context, better matches: An AI love story (for dogs) | Sanity How to write for an agent | Sanity Content Agent, meet Slack: AI content operations in your workflow | Sanity Structure powers intelligence | Sanity Your agent needs better content. Here's how to give it. | Sanity How to serve content to agents (a field guide) | Sanity Sanity TypeGen GA: Automatic TypeScript types for content and GROQ | Sanity Sanity is now available on the Vercel Marketplace | Sanity The logo soup problem (and how to solve it) | Sanity Content Releases: From scattered updates to coordinated publishing | Sanity What's New - February 2026 | Sanity How we solved the agent memory problem | Sanity v0 Builder Challenge: The winners | Sanity Introducing: Sanity Agent Skills | Sanity Content Agent: Days of work in one conversation | Sanity Our Sanity Values | Sanity Open Source Pledge 2025: Stepping up when it matters | Sanity v0 builder challenge: $3000 in prizes | Sanity Why AI Breaks Without Structured Content Operations | Sanity What’s New January - 2026 | Sanity BFCM 2025: What teams built when infrastructure stopped being the problem | Sanity How AI shaped holiday shopping and what it means for content in 2026 | Sanity Sanity Studio v5: Embracing React 19 | Sanity You’ll need a CMS eventually. Let your agent set it up. | Sanity “You should never build a CMS” | Sanity AI Content Operations: A 30-Day Implementation Guide | Sanity What’s New December - 2025 | Sanity Scheduled Drafts: Stop manually publishing content at midnight | Sanity What’s New November - 2025 | Sanity Everything *[NYC] 2025 recap: A day of AI, Content Operations, and Culture | Sanity Clankers and content operations | Sanity Content Agent: AI that understands your structured content is here | Sanity Why design-driven content modeling creates technical debt, not velocity | Sanity What's New October - 2025 | Sanity From studio to inbox: How Kevin Green eliminated email campaign friction | Sanity The content editor's guide to content operations [E-commerce edition] | Sanity styled-components maintenance mode: A 40% faster fork | Sanity From zero code to a live website in 7 hours (thanks, Cursor!) | Sanity First attempt will be 95% garbage: A staff engineer's 6-week journey with Claude Code | Sanity Internationalization is more than translating words | Sanity What's New - September 2025 | Sanity We just deleted our 35k-member community Slack | Sanity What's New - August 2025 | Sanity The engineer's guide to content operations [E-commerce edition] | Sanity SEO for AI: Evolving from Web Pages to the Content Lake | Sanity What's New - July 2025 | Sanity Sanity Studio v4: A major version bump for a minor reason | Sanity What's New - June 2025 | Sanity Dashboard and Insights: Your New Content HQ | Sanity Canvas: AI-accelerated, context-aware, freeform authoring | Sanity Agent Actions: AI building blocks for structured content | Sanity Functions: Life beyond pressing publish | Sanity A new era for content applications with Sanity App SDK | Sanity The end of CMS era and our $85M Series C. | Sanity What's New – May 2025 | Sanity Introducing the Sanity Model Context Protocol (MCP) server | Sanity What's New – April 2025 | Sanity Pushing all the envelopes with ambitious content | Sanity Self-hosting is only free if your time is worth nothing | Sanity Content that lasts: Scaling beyond your frontend | Sanity The Live Content API is now Generally Available | Sanity The future beyond AI chat bots | Sanity Learning the new skill of working with AI | Sanity What's New - March 2025 | Sanity Give it in plain text: Making your content AI-Ready | Sanity No More 'DO NOT PUBLISH': Introducing Content Releases | Sanity React in 2025, what's next? | Sanity The final boss of front-end: block editors | Sanity Introducing Sanity for Startups | Sanity A block content editor that loves you back | Sanity A Black Friday Snooze Fest: Massive Traffic, No Drama | Sanity How to make a recipe site that scales well | Sanity The Sanity Winter Release 2024 | Sanity AVIF Arrives, Sanity’s Promise Fulfilled | Sanity Sanity joins the Open Source Pledge | Sanity Your content is now Live by default | Sanity Begin Team to Join Sanity | Sanity Sanity Digest - September '24 Edition | Sanity Sanity partners with Google. Now live on the Google Cloud Marketplace. | Sanity Sanity Digest - August ‘24 Edition | Sanity Now playing: the latest Mux Video Input plugin for Sanity | Sanity Community Digest - June ‘24 Edition | Sanity Community Digest - May ‘24 Edition | Sanity Guide to Sanity's newest product announcements | Sanity AI and Content Creation: A Leader's Guide | Sanity Of course, you should be able to type your content quickly! | Sanity New to AI Assist: translation, reference suggestions, image generation | Sanity Speak the language of your editors: Sanity Studio UI localization | Sanity Introducing the new Sanity Growth plan to serve collaborative teams | Sanity Presentation: Work faster than ever with structured content | Sanity Goodbye Feedback Frenzy, Hello Sanity Studio Comments! | Sanity Easing into the App Router with the Sanity Toolkit for Next.js | Sanity
Where is your Code of Conduct? | Sanity
Lo Etheridge · 2021-12-11 · via Sanity.io

It is time to rethink how we handle codes of conduct and become more action-based in our approach. It is not enough to show a document if we are aiming to set the overall behavior and communication tone for the organization or community. A code of conduct (CoC) should be a living document with realistic scenarios that reinforce the underlying organizational or community values. Community guidelines are not about making people follow rules but are the first step and introduction to what it means to be a part of a community that is attempting to recognize every member's value. After all, isn't the point of a community to grow, learn, and share with one another?

What is a Code of Conduct?

The common definition for code of conduct is a central guide and reference for members to support day-to-day decision making, communication, behavior, and actions. When was the last time you looked at the code of conduct of the company you work for or the community you are a part of? If a code of conduct is meant to set the ethical tone for how people should operate within an organization, we should do more than write them down and point to their location once. Ethical decision-making, mutual respect, and empathy are not only learned behaviors but they function as muscles; the more you use them the stronger they become.

It should be a living document

If we want employees or community members to communicate and behave in a certain way, it is time to stop storing the code of conduct in Google drive or GitHub and only refer to it when there is a problem after we show it during the onboarding process. When this kind of document is not readily visible, it communicates that its contents are not important. It needs to be integrated into your regular community interaction. It needs to be a living thing.

People are diverse and come into organizations and virtual communities having a wide range of life experiences. We know this is true. If we know that a person's background, life experience, culture, age, gender, ethnicity, and many other aspects can influence the way someone communicates and makes decisions; why would we assume that everyone holds the same knowledge or communicates and makes decisions in the same way?

It's not fair to assume that everyone learns from reading a static document of rules and guidelines. We can't even assume that everyone relates to it in the first place. There might even be good reasons too. Maybe they aren't super proficient in the language your code of conduct is written in. Maybe they don't have the time or attention to deal with it right then. Hence, it's on you to make the contents of the code of conduct accessible in different ways.

A practical example

Showing a written code of conduct to new community members without supplying foundational knowledge, scenario-based learning, and contextualizing the significance of the contents is making the assumption that everyone “gets it” from reading a document once (that assumption is wrong).

In practice, this could look like developing a framework for continuous learning that includes foundational knowledge, scenario-based learning, and impact. Making sure the community has a shared language for inclusive and empathetic behavior and communication is a great first step. This can look like regular messaging in your spaces about the concepts that reinforce the values of your community.

At Sanity, we lead with empathy and mutual respect, so it is up to us to make sure everyone who enters the community understands these concepts. Providing your community whether it's on Slack, Discord, or your social media accounts with brief and frequent messaging like the above greatly increases awareness about the expectations for behavior and communication in these spaces. Once you have a steady rhythm of this messaging, you can use the same bite-sized messaging to introduce scenario-based learning and impact.

Keeping it real

Scenario-based learning (SBL) uses scenarios to support active learning strategies such as problem-based or case-based learning. SBL works because learning best takes place in the context in which it is going to be used. In other words, providing real-world examples of the application of your values deepens the understanding of everyone in the community. Example scenarios also help you illustrate the impact and importance of expected communication and behavior.

Remember, the reason why you want a code of conduct is to create a welcoming space. It's to have a common point of reference for values. You can exemplify this by creating scenarios that emphasize action, behavior, and consequences. Keep your scenario objective so that you can focus on the behavior and the consequences of the behavior and the choices made in the scenario. This is how you introduce impact. After the scenario, provide a mini point of reflection that gives constructive ways to respond or communicate in the given scenario that reflect the values of your community.

A code of conduct is a necessary document to embody the values of your community, but it's your plan and ongoing repetitive initiatives that will actually impact how safe and inclusive it is when growing.

Have you done something to get your communities' code of conduct more relevant? Let us know!