Add development status note, document goals, and fix overstated CG claims

[Copilot]

Feedback in solidproject.org#951 identified that the page overstates Solid26's relationship to the W3C Solid CG and misrepresents ODI's authority over the Solid Protocol.

Changes

• Development status banner — Added prominent note that Solid26 is under development and spec documents have not yet been through the CG process
• Explicit document goals — States the two purposes: (1) written reference for what's been discussed in CG calls, (2) future announcement page once docs are finalized
• Corrected framing — "first annual release of the Solid specification" → "planned collection of Solid specification versions"; rolling release model described as aspirational and subject to CG discussion
• Stewardship language — Clarifies that ODI stewards the Solid Project (not the CG), with link to the ODI project page; removed phrasing that implied ODI/CG normative endorsement
• Proposal attribution — Clarifies that the current contents of Solid26 have been proposed by members of the CG, including the ODI
• Draft qualifiers — Spec versions marked as subject to CG confirmation; Primer labeled as draft

Applied consistently across both content.md and index.html.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Clarifications</issue_title>
<issue_description>Please address clarifications identified in solid/solidproject.org#951 (comment) -- including explicitly identifying the goals of the document as listed in that comment.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Clarifications #5

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[jeswr]

@copilot please also clarify the following:

• The ODI stewards the Solid Project, not the CG specifically (https://theodi.org/insights/projects/odi-and-solid-building-a-future-where-data-works-for-everyone/)
• The current contents of Solid26 are proposed by members of the CG, incuding the ODI

[Copilot]

@copilot please also clarify the following:

• The ODI stewards the Solid Project, not the CG specifically (https://theodi.org/insights/projects/odi-and-solid-building-a-future-where-...

Updated in 6417cd0:

• Changed intro to: "The current contents have been proposed by members of the W3C Solid Community Group, including the Open Data Institute"
• Changed stewardship language to: "The Open Data Institute stewards the Solid Project" with link to https://theodi.org/insights/projects/odi-and-solid-building-a-future-where-data-works-for-everyone/
• Updated footer to: "Proposed by members of the Solid Community Group. The Open Data Institute stewards the Solid Project."

Applied consistently across both content.md and index.html.

[Copilot]

Pull request overview

Updates the Solid26 landing page copy to better reflect its in-development status, clarify the document’s goals, and correct/soften statements about the W3C Solid Community Group process and ODI’s role.

Changes:

• Adds an explicit development-status note and states two goals for the page/document.
• Reframes Solid26 as a proposed/planned collection (not an “annual release”) and marks versions/primer as draft/subject to CG confirmation.
• Clarifies stewardship/attribution language around ODI and the Solid Community Group.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
index.html	Adds dev-status/goals callout and adjusts page copy to avoid overstating CG/ODI authority and to better qualify draft status.
content.md	Mirrors the dev-status/goals and reframed language updates in the Markdown version.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This development-status callout uses multiple inline styles on the

and

elements. Since the page already has a central <style> block with reusable classes, moving these styles into a CSS class (e.g., a "banner"/"notice" class) would make the design easier to maintain and keep consistent across future updates.

[Copilot]

Using a

without a heading is semantically discouraged (sections are intended to represent a standalone, titled region). Since this block is a callout/note, consider using an (optionally with role="note") or a

instead, to improve document structure for assistive technologies.

Suggested change

	<section style="background: #fff3cd; border: 1px solid #ffc107; border-radius: 8px; padding: 1.5rem; margin-bottom: 2rem;">
	<p style="color: #664d03; margin-bottom: 0.75rem;"><strong>Note:</strong> Solid26 is currently under development. The primer and some specification documents referenced here have not yet been put through the W3C Solid Community Group process. We are working to have this done by the end of April 2026.</p>
	<p style="color: #664d03; margin-bottom: 0;"><strong>Goals of this page:</strong> (1) To capture and communicate the goals and planned contents of Solid26, based on discussions in W3C Solid Community Group calls — providing a written reference for what has so far been discussed verbally. (2) To serve as an announcement and landing page once the documents included in Solid26 have been finalised through the Community Group process.</p>
	</section>
	<aside role="note" style="background: #fff3cd; border: 1px solid #ffc107; border-radius: 8px; padding: 1.5rem; margin-bottom: 2rem;">
	<p style="color: #664d03; margin-bottom: 0.75rem;"><strong>Note:</strong> Solid26 is currently under development. The primer and some specification documents referenced here have not yet been put through the W3C Solid Community Group process. We are working to have this done by the end of April 2026.</p>
	<p style="color: #664d03; margin-bottom: 0;"><strong>Goals of this page:</strong> (1) To capture and communicate the goals and planned contents of Solid26, based on discussions in W3C Solid Community Group calls — providing a written reference for what has so far been discussed verbally. (2) To serve as an announcement and landing page once the documents included in Solid26 have been finalised through the Community Group process.</p>
	</aside>