chore(gov): refine Content vs. Code guidelines

[avivkeller]

Ref: #7974 (comment)

---

This PR updates the Content vs. Code guidelines to give the Node.js Website Team editorial authority to review/block/approve on the basis of "content quality, structure, and presentation across the website", while delegating "technical accuracy" to the working groups.

@ovflowd Hopefully this is worded in a way that "protects" the Website Team, as you mentioned prior.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Jul 14, 2025 6:01pm

[Copilot]

Pull Request Overview

This PR refines the “Content vs. Code” guidelines by clarifying the Website Team’s editorial authority and delineating technical accuracy responsibilities.

• Introduces an “Editorial Responsibilities” section to define roles for the Website Team vs. Working Groups.
• Adds a “Content Ownership and Collaboration” section to explain how unowned areas are handled.
• Updates the summary to reflect the Website Team’s editorial authority alongside technical domain experts.

Comments suppressed due to low confidence (3)

docs/content-vs-code.md:13

• [nitpick] Capitalize 'Teams' in 'Working Groups and teams' for consistency (e.g., 'Working Groups and Teams').

- **Working Groups and teams** retain final authority over technical content within their areas of expertise

docs/content-vs-code.md:24

• [nitpick] This sentence is quite long; consider splitting into two sentences or formatting as a bullet for better readability.

The Website Team may review all content for correct usage of this repository's tooling and structure, and can make editorial decisions to improve content quality and user experience. For technical accuracy, the Website Team will collaborate with or defer to the appropriate Working Groups and subject matter experts.

docs/content-vs-code.md:28

• [nitpick] The summary paragraph is lengthy; consider converting it into bullet points to improve readability and match other sections.

The Website Team is responsible for creating, crafting and maintaining the Node.js Website. We have editorial authority to ensure content quality and presentation, while collaborating with Node.js Core Collaborators and Working Groups who maintain technical authority in their respective domains. The Website Team actively contributes content and takes editorial responsibility for improving the overall quality and user experience of the website.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.14%. Comparing base (8d8aeae) to head (aace2d1).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7978      +/-   ##
==========================================
- Coverage   73.15%   73.14%   -0.02%     
==========================================
  Files          95       95              
  Lines        8355     8355              
  Branches      218      218              
==========================================
- Hits         6112     6111       -1     
- Misses       2242     2243       +1     
  Partials        1        1              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[avivkeller]

For the sake of clarity to users who wish to participate in thoughtful discussion, the user above mentioned the following concern:

It gives them full control and what gets published and what doesn’t.

This changes does not give us "full control", but rather more control over what gets published. Specifically, we can control "content quality, structure, and presentation across the website". Everything else is deferred to the WGs.

[avivkeller]

This can be something we discuss in our first meeting, once that's scheduled.