Some fixes that were destined for the new site, but...

Dockerfile

@@ -1 +1 @@
-FROM klakegg/hugo:0.82.1-ext-alpine-onbuild
+FROM klakegg/hugo:0.101.0-ext-asciidoctor-onbuild

config.toml

@@ -6,7 +6,7 @@ title = "Coalition for Content Provenance and Authenticity"
 
 defaultContentLanguage = "en" 
 paginate = 10
-sectionPagesMenu = "main" 
+# sectionPagesMenu = "main" 
 enableRobotsTXT = false
 googleAnalytics = "" 
 
@@ -323,7 +323,7 @@ weight = 20
 [[menu.main]]
 identifier = "spec"
 title = "Specification"
-url = "https://c2pa.org/specifications/specifications/2.1/index.html"
+url = "https://c2pa.org/specifications/specifications/2.2/index.html"
 weight = 25
 [[menu.main]]
 identifier = "membership"
@@ -341,12 +341,31 @@ title = "Contact"
 url = "/contact/"
 weight = 50
 [[menu.main]]
+identifier = "conformance"
+title = "Conformance"
+url = "/conformance/"
+weight = 60
+[[menu.main]]
 identifier = "_github"
 title = "GitHub"
-weight = 60
+weight = 70
 
 [build]
 writeStats = true
 
 [markup.goldmark.renderer]
   unsafe = true
+
+[security]
+enableInlineShortcodes = false
+
+[security.exec]
+allow = ["^dart-sass-embedded$", "^go$", "^npx$", "^postcss$", "^asciidoctor$"]
+osEnv = ["(?i)^(PATH|PATHEXT|APPDATA|TMP|TEMP|TERM|RUBYLIB)$"]
+
+[security.funcs]
+getenv = ["^HUGO_"]
+
+[security.http]
+methods = ["(?i)GET|POST"]
+urls = [".*"]

content/en/conformance/_index.md

@@ -0,0 +1,21 @@
+---
+title: "Conformance"
+featured_image: ''
+---
+
+## Introduction
+
+TBD
+
+## Checklist
+
+TBD
+
+## Program Details
+
+https://github.com/c2pa-org/conformance-public
+
+## Interested in participating?
+
+https://docs.google.com/forms/d/e/1FAIpQLSds0w9DHq_x9iFoQ3sM_a3n9-m_yPRkGEuInCDmc7FBbTCd4w/viewform
+

content/en/digitalsourcetype/_index.md

@@ -0,0 +1,7 @@
+---
+build:
+  list: never
+  render: never
+title: "Digital Source Types"
+featured_image: ''
+---

content/en/digitalsourcetype/empty.adoc

@@ -0,0 +1,22 @@
+---
+title: "Digital Source Type: Empty"
+featured_image: ''
+---
+
+
+[%noheader]
+[cols="1,1,1,1"]
+|===
+4+| *Concept* ID (QCode) = digsrctype:empty,  ID (URI) = http://c2pa.org/digitalsourcetype/empty
+
+| *Type*: cpnat:abstract
+| *Created*: 2025-06-15T19:58:50.916Z
+| *Modified*: 2025-06-15T19:58:50.916Z
+| *Retired*:
+
+4+| *Name* (en): Empty media
+
+4+| *Definition* (en): Media whose digital content is effectively empty, such as a blank canvas or zero-length video.
+
+4+| *Member of scheme*: http://c2pa.org/digitalsourcetype/
+|===

content/en/digitalsourcetype/trainedAlgorithmicData.adoc

@@ -0,0 +1,21 @@
+---
+title: "Digital Source Type: Trained Algorithmic Data"
+featured_image: ''
+---
+
+[%noheader]
+[cols="1,1,1,1"]
+|===
+4+| *Concept* ID (QCode) = digsrctype:trainedAlgorithmicMedia,  ID (URI) = http://c2pa.org/digitalsourcetype/trainedAlgorithmicData
+
+| *Type*: cpnat:abstract
+| *Created*: 2025-06-15T19:58:50.916Z
+| *Modified*: 2025-06-15T19:58:50.916Z
+| *Retired*:
+
+4+| *Name* (en): Data created using Generative AI
+
+4+| *Definition* (en): Data that is the result of algorithmically using a model derived from sampled content and data. Differs from http://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia in that the result isn’t a media type (e.g., image or video) but is a data format (e.g., CSV, pickle).
+
+4+| *Member of scheme*: http://c2pa.org/digitalsourcetype/
+|===

content/en/faq/_index.md

@@ -3,20 +3,92 @@ title: "FAQ"
 featured_image: ''
 ---
 
-## What is the Coalition for Content Provenance and Authenticity (C2PA)?
-The C2PA is a [Joint Development Foundation](https://www.jointdevelopment.org/) project to collectively build an end-to-end open technical standard to provide publishers, creators, and consumers with opt-in, flexible ways to understand the authenticity and provenance of different types of media. C2PA opposes efforts to make content provenance measures mandatory.
+## What are Content Credentials?
 
-## What is content provenance?
-Provenance refers to the basic, trustworthy facts about the origins of a piece of digital content (image, video, audio recording, document). It may include information such as who created it and how, when, and where it was created or edited. The content author always has control over whether provenance data is included as well as what data is included. Included information can be removed in later edits. Provenance also allows for anonymous content.
+Content provenance refers to the recorded history of a piece of digital content—such as an image, video, audio recording, or document—from the moment it is created through all subsequent modifications or uses. Content Credentials provide a cryptographically secure way to capture and express content provenance. They can include information about how the content was created, what tools or processes were used, when and where it was made, and how it has changed over time.
 
-## What makes content provenance a better solution to address misinformation?
-Detecting whether or not digital content is fake is currently impossible at internet scale and speed because manipulation software is increasingly more sophisticated, metadata can easily be manipulated and provides no proof of its origins. 
+In the context of C2PA, content provenance is captured and preserved using Content Credentials, the technical standard the C2PA produces, providing tamper-evident, cryptographically signed data structures that travel with the asset. This ensures that users can verify the authenticity and integrity of digital media, helping to build trust and transparency across the content ecosystem.
 
-## Which companies are part of C2PA?
-The C2PA was founded February 2021 by Microsoft and Adobe and includes Arm, BBC, Intel, and Truepic.
+## What makes Content Credentials a key component to helping users make sense of what they see online? 
 
-## When will C2PA deliver the technical standard?
-C2PA delivered version 1.0 of its technical standard for content provenance and authenticity in 2021.  It has since updated that with version 1.1 and then 1.2 in 2022. Work continues to support new file formats, alignment with Generative AI, Live Video & Audio and more.
+People are increasingly concerned about being able to identify content that has been generated or edited by generative AI systems, or conversely, content that is generally unadulterated since its capture by e.g. a camera. Content provenance enables them to answer that question, which empowers them to decide how useful or reliable a piece of content is for their use case.
 
-## How can we join C2PA?
-To apply, please contact [email protected].
+## How can consumers of C2PA data be assured the data was captured correctly?
+
+Consumers can trust that C2PA data was captured correctly because each Content Credential (also known as a C2PA Manifest) is digitally signed by a trusted implementation. These credentials include cryptographic hashes of both the asset and the provenance data. Any modification—intentional or accidental—will break this cryptographic linkage, signalling tampering.
+
+Additionally, the C2PA Conformance Program ensures that products creating Content Credentials meet stringent technical and security requirements and are vetted by the Administering Authority. These products are then listed in the C2PA Conforming Products List, providing visibility into which implementations are trusted.
+
+## How are signing certificates issued to implementers of the C2PA specification?
+
+Signing certificates are issued by Certification Authorities (CAs) listed on the C2PA Trust List. To obtain one, a conforming Generator Product must undergo a conformance and security evaluation, be accepted into the program, and may need to present dynamic evidence (e.g. hardware-backed attestation) during the certificate enrollment process.
+
+The certificate issued (the C2PA Claim Signing Certificate) includes a field denoting the product’s Assurance Level, which corresponds to the level of scrutiny it passed during evaluation.
+
+## Does validation of C2PA data ensure that the entire chain of provenance is known, including ingredients?
+
+C2PA supports multi-source provenance by including “ingredient” metadata—references to other assets used to compose the current asset. Each ingredient can include its own Content Credential.
+
+While the primary asset’s Content Credential can validate that the ingredients were checked at the time of use, the full verification of each ingredient's provenance requires access to its data. Without it, only the presence of prior validation (not the complete ingredient chain) can be confirmed.
+
+## Are Content Credentials a form of DRM? How do they differ?
+
+No, Content Credentials are not a form of DRM (Digital Rights Management). DRM restricts how users can access or use content. In contrast, Content Credentials are about transparency and integrity—they record and preserve the provenance of digital media without limiting its use.
+
+Content Credentials are open, tamper-evident, and user-verifiable. They focus on enabling trust rather than enforcing control.
+
+## Is the C2PA data model complementary to IPTC metadata?
+
+Yes. The C2PA model is designed to interoperate with standard metadata formats like IPTC, XMP, and EXIF. It can encapsulate these metadata types as assertions within a Content Credential, making them tamper-evident and cryptographically verifiable.
+
+This interoperability ensures continuity for existing metadata workflows while enhancing security and trust.
+
+## What happens if C2PA metadata is stripped from the media it represents?
+
+While C2PA Manifests are typically embedded in the asset, they can be separated. To address this, C2PA supports durable credentials via soft bindings—such as invisible watermarking or fingerprinting—that can help rediscover the associated Content Credential even if it's removed from the file.
+
+This is often referred to as “Durable Content Credentials,” providing resilience in cases where metadata is accidentally or intentionally stripped.
+
+## Can the C2PA technology be used in offline contexts? For example, with a camera device that is often not connected to the internet.
+
+Yes. C2PA is designed to support offline workflows. Devices like cameras can securely generate and sign Content Credentials using locally stored cryptographic keys, without needing to be connected to the internet. Certificates can be provisioned in advance or renewed later when connectivity resumes.
+
+## Is licensing required to use the C2PA technology? Are there patents associated with it?
+
+No license fees are required. The C2PA specification is released as an open standard under a royalty-free license, enabling implementation by both open-source and proprietary products. There are no patents associated with the techniques of the C2PA specification, and C2PA members have committed to make their contributions freely available under the terms of the specification.
+
+## What is the C2PA Trust List, and how does it ensure trustworthiness in the ecosystem?
+
+The C2PA Trust List is a curated list of Certification Authorities (CAs) that are authorized to issue signing certificates for Generator Products. Only products evaluated and approved by the Conformance Program are eligible to receive certificates from these trusted CAs.
+
+This ensures that any signed Content Credential can be cryptographically verified against a known and approved trust anchor.
+
+## How much does it cost to obtain a C2PA conforming certificate?
+
+Costs may vary depending on the Certification Authority issuing the certificate and the product’s desired Assurance Level. While the C2PA Conformance Program defines technical and policy requirements, the actual fees are set by individual CAs and subject to their commercial terms.
+
+## Do we need to join the C2PA to use the specification in our products or services?
+
+No. You can implement the C2PA specification without joining the organization. However, to receive a Claim Signing Certificate and be listed on the official Conforming Products List, your product must undergo evaluation and legal onboarding through the C2PA Conformance Program.
+
+## How secure is C2PA? Can it be easily removed or faked?
+
+C2PA is built on strong cryptographic foundations: SHA-256 hashes, X.509 certificates, and digital signatures. Any tampering with the asset or its metadata invalidates the cryptographic hash and signature, making alterations immediately detectable.
+
+While metadata can be removed inadvertently or intentionally, it is vital information for consumers, and recovery mechanisms such as soft bindings and cloud retrieval can be used to restore provenance data. Faking Content Credentials would require breaking current cryptographic standards—an infeasible task with today's technology.
+
+## Does the presence of Content Credentials or C2PA data in a piece of digital content increase its size?
+
+Yes, but only modestly. A typical Content Credential adds a small amount of data to the digital asset—often measured in kilobytes—depending on the number and complexity of assertions. For most images, videos, audio recordings, and documents, the size increase is negligible relative to the asset itself and is a reasonable tradeoff for added security and trust.
+
+## Can organizations or individuals use Content Credentials to achieve attribution of their content?
+
+The core C2PA Content Credentials specification does not support attribution of content to individuals or organizations, so that it can remain maximally privacy-preserving. However, a few user communities are developing extensions to the core specification that do allow for attribution to individuals or organizations, where the risks of disclosing creator identity are well-understood. 
+
+## Are Content Credentials available globally?
+
+Yes, Content Credentials are freely available everywhere, with implementations coming from around the world.
+
+## How can we join the C2PA?
+
+To apply, please visit [https://c2pa.org/membership/](https://c2pa.org/membership/) or contact [email protected].

docs/404.html

@@ -6,12 +6,12 @@
   <meta name="viewport" content="width=device-width, initial-scale=1" />
   <title>
     404 Page not found - C2PA
-  </title><meta name="generator" content="Hugo 0.82.1" />
+  </title><meta name="generator" content="Hugo 0.101.0" />
 
   <link rel="stylesheet" href="https://use.typekit.net/tsb3xic.css" /><link
       rel="stylesheet"
-      href="/css/styles.min.b2383f1736ae10bf2df5eb323868f6f030d1d2db1e6ca7eae8785c2c01dae273.css"
-      integrity="sha256-sjg/FzauEL8t9esyOGj28DDR0tsebKfq6HhcLAHa4nM="
+      href="/css/styles.min.c02c16b613868668e51e6a93f1fde6cf09359f047174520b04093196ef970cab.css"
+      integrity="sha256-wCwWthOGhmjlHmqT8f3mzwk1nwRxdFILBAkxlu+XDKs="
     />
   </head>
 
@@ -132,7 +132,7 @@
 
             <li>
               <a
-                href="https://c2pa.org/specifications/specifications/2.1/index.html"
+                href="https://c2pa.org/specifications/specifications/2.2/index.html"
                 class="text-gray-600 hover:text-blue-600 cursor-pointer no-underline"
                 >Specification</a
               >
@@ -170,6 +170,16 @@
 
 
 
+            <li>
+              <a
+                href="/conformance/"
+                class="text-gray-600 hover:text-blue-600 cursor-pointer no-underline"
+                >Conformance</a
+              >
+            </li>
+
+
+
             <li>
               <a
                 href="https://github.com/c2pa-org"

docs/about/about/index.html

@@ -6,12 +6,12 @@
   <meta name="viewport" content="width=device-width, initial-scale=1" />
   <title>
     About - C2PA
-  </title><meta name="generator" content="Hugo 0.82.1" />
+  </title><meta name="generator" content="Hugo 0.101.0" />
 
   <link rel="stylesheet" href="https://use.typekit.net/tsb3xic.css" /><link
       rel="stylesheet"
-      href="/css/styles.min.b2383f1736ae10bf2df5eb323868f6f030d1d2db1e6ca7eae8785c2c01dae273.css"
-      integrity="sha256-sjg/FzauEL8t9esyOGj28DDR0tsebKfq6HhcLAHa4nM="
+      href="/css/styles.min.c02c16b613868668e51e6a93f1fde6cf09359f047174520b04093196ef970cab.css"
+      integrity="sha256-wCwWthOGhmjlHmqT8f3mzwk1nwRxdFILBAkxlu+XDKs="
     />
   </head>
 
@@ -103,7 +103,7 @@
             <li>
               <a
                 href="/about/"
-                class="text-gray-900 border-b border-gray-300 pb-1 cursor-default no-underline"
+                class="text-gray-600 hover:text-blue-600 cursor-pointer no-underline"
                 >About</a
               >
             </li>
@@ -132,7 +132,7 @@
 
             <li>
               <a
-                href="https://c2pa.org/specifications/specifications/2.1/index.html"
+                href="https://c2pa.org/specifications/specifications/2.2/index.html"
                 class="text-gray-600 hover:text-blue-600 cursor-pointer no-underline"
                 >Specification</a
               >
@@ -170,6 +170,16 @@
 
 
 
+            <li>
+              <a
+                href="/conformance/"
+                class="text-gray-600 hover:text-blue-600 cursor-pointer no-underline"
+                >Conformance</a
+              >
+            </li>
+
+
+
             <li>
               <a
                 href="https://github.com/c2pa-org"

docs/about/charter/index.html

@@ -6,12 +6,12 @@
   <meta name="viewport" content="width=device-width, initial-scale=1" />
   <title>
     Charter - C2PA
-  </title><meta name="generator" content="Hugo 0.82.1" />
+  </title><meta name="generator" content="Hugo 0.101.0" />
 
   <link rel="stylesheet" href="https://use.typekit.net/tsb3xic.css" /><link
       rel="stylesheet"
-      href="/css/styles.min.b2383f1736ae10bf2df5eb323868f6f030d1d2db1e6ca7eae8785c2c01dae273.css"
-      integrity="sha256-sjg/FzauEL8t9esyOGj28DDR0tsebKfq6HhcLAHa4nM="
+      href="/css/styles.min.c02c16b613868668e51e6a93f1fde6cf09359f047174520b04093196ef970cab.css"
+      integrity="sha256-wCwWthOGhmjlHmqT8f3mzwk1nwRxdFILBAkxlu+XDKs="
     />
   </head>
 
@@ -103,7 +103,7 @@
             <li>
               <a
                 href="/about/"
-                class="text-gray-900 border-b border-gray-300 pb-1 cursor-default no-underline"
+                class="text-gray-600 hover:text-blue-600 cursor-pointer no-underline"
                 >About</a
               >
             </li>
@@ -132,7 +132,7 @@
 
             <li>
               <a
-                href="https://c2pa.org/specifications/specifications/2.1/index.html"
+                href="https://c2pa.org/specifications/specifications/2.2/index.html"
                 class="text-gray-600 hover:text-blue-600 cursor-pointer no-underline"
                 >Specification</a
               >
@@ -170,6 +170,16 @@
 
 
 
+            <li>
+              <a
+                href="/conformance/"
+                class="text-gray-600 hover:text-blue-600 cursor-pointer no-underline"
+                >Conformance</a
+              >
+            </li>
+
+
+
             <li>
               <a
                 href="https://github.com/c2pa-org"