You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repo contains the source code and content to generate the <https://opensource.contentauthenticity.org/> website. This site is built using [Docusaurus 2](https://docusaurus.io/), a modern static site generator, and deployed on [Netlify](https://www.netlify.com/).
7
+
This repo contains the source code and content to generate the <https://opensource.contentauthenticity.org/> website. This site is built using [Docusaurus 3](https://docusaurus.io/), a modern static site generator, and deployed on [Netlify](https://www.netlify.com/).
8
8
9
9
### Directory structure
10
10
11
11
The `docs` sub-directory contains documentation content (in markdown or `.mdx` format) in the following sub-directories:
12
-
-[`js-sdk/api`](./docs/js-sdk/api): [API documentation](https://opensource.contentauthenticity.org/docs/js-sdk/api/) for the JavaScript library generated from the source code; see [Generating JavaScript API docs](#generating-javascript-sdk-api-docs).
13
-
-[`js-sdk`](./docs/js-sdk/): [Other documentation](https://opensource.contentauthenticity.org/docs/js-sdk/getting-started/overview) for the JavaScript library.
14
-
(./scripts/generate-api-docs/index.js)
12
+
15
13
-`includes`: Markdown content imported (transcluded) into other files.
16
-
-`manifest`: Content for the [Understanding manifests](https://opensource.contentauthenticity.org/docs/manifest/understanding-manifest) section.
17
14
-`static`: Additional assets such as images.
15
+
-`manifest`: Content for the [Understanding manifests](https://opensource.contentauthenticity.org/docs/manifest/understanding-manifest) section.
16
+
- Various other sub-directories for content sections, e.g. `durable-cr`, `manifest`, `signing`, etc.
18
17
19
18
Additionally, the [scripts/fetch-readme.js](./scripts/fetch-readme.js) script dynamically downloads documentation files (sometimes just the `README.md` but often other markdown files, too) from other repos in the SDK. See [Running the fetch script](#running-fetch-script).
20
19
@@ -23,17 +22,16 @@ This table summarizes the content that this script fetches from other repos.
The [Manifest store reference](https://opensource.contentauthenticity.org/docs/manifest/manifest-ref) is an HTML file generated by the [json-manifest-reference](https://github.com/contentauth/json-manifest-reference) repository and imported manually.
**Prerequisite**: To build the site locally, you must first check out the JavaScript library in a sibling directory and build the API docs there. In the parent directory of the `opensource.contentauth.org` directory, enter these commands:
Then you can build and run the doc site with this command:
58
-
59
-
```
60
52
$ npm start
61
53
```
62
54
@@ -72,14 +64,6 @@ npm run docs:fetch-readme
72
64
73
65
NOTE: If you need to get markdown files from a **new** repo that you added, then you need to manually add the sub-directory, add a `.gitkeep` file to it, and then commit it to this repository.
74
66
75
-
### Generating JavaScript SDK API docs
76
-
77
-
The `/scripts/generate-api-docs/index.js` script generates API docs for the JS SDK (assuming you've checked it out in a sibling directory). To run this script for local build, enter this command:
Copy file name to clipboardExpand all lines: docs/community.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Participants are required to follow the [Adobe Code of Conduct](https://github.c
29
29
30
30
### Verify
31
31
32
-
The code for the [C2PA Verify website](https://verify.contentauthenticity.org/) is open source. For general information on using it, see [Using the Verify tool](verify.mdx).
32
+
The code for the [C2PA Verify website](https://verify.contentauthenticity.org/) is open source. For general information on using it, see [Using the Verify tool](getting-started/verify.mdx).
33
33
34
34
### Related projects
35
35
@@ -55,8 +55,8 @@ The CAI maintains a [Discord server](https://discord.gg/CAI) for open technical
55
55
## Other resources
56
56
57
57
-**Read the [CAI blog](https://contentauthenticity.org/blog)** to get the latest news and updates about CAI.
58
-
-**Follow [CAI on Twitter](https://twitter.com/ContentAuth)** for the latest general announcements and information.
59
-
-**[The FAQ](./faqs)** address a number of high-level questions.
58
+
-**Follow [CAI on X](https://twitter.com/ContentAuth)** for the latest general announcements and information.
59
+
-**[The FAQs](getting-started/faqs.mdx)** address a number of high-level questions.
Copy file name to clipboardExpand all lines: docs/conformance.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ For more information, see [C2PA Conformance Program Documents](https://github.co
49
49
50
50
#### Preliminary certificate check
51
51
52
-
To confirm all the settings in your signing certificate, you can follow the [preliminary certificate check](trust-list.mdx#checking-your-certificate) for the interim trust list to help ensure everything is as expected.
52
+
To confirm all the settings in your signing certificate, you can follow the [preliminary certificate check](getting-started/trust-list.mdx#checking-your-certificate) for the interim trust list to help ensure everything is as expected.
53
53
54
54
#### Security requirements
55
55
@@ -85,9 +85,9 @@ C2PA maintains two trust lists:
85
85
86
86
### Interim trust list retirement
87
87
88
-
With the introduction of the C2PA trust list, the existing [interim (temporary) trust list](trust-list.mdx) is being retired on the following timeline:
88
+
With the introduction of the C2PA trust list, the existing [interim (temporary) trust list](getting-started/trust-list.mdx) is being retired on the following timeline:
89
89
90
-
-**Through December 31, 2025**: The [interim trust list](trust-list.mdx) will remain operational. During this time:
90
+
-**Through December 31, 2025**: The [interim trust list](getting-started/trust-list.mdx) will remain operational. During this time:
91
91
- The [Verify site](https://verify.contentauthenticity.org) will continue to display manifests signed by certificates on the interim trust list as trusted, but with a disclaimer that the manifests were made with an older version of the trust model.
92
92
- New certificates will continue to be added to the interim trust list when requested.
93
93
- Product developers are strongly encouraged to apply to the C2PA conformance program and use the official C2PA trust list.
Copy file name to clipboardExpand all lines: docs/getting-started/faqs.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Notable implementations using blockchain:
33
33
34
34
No; Content Credentials do not enforce permissions for access to content. In many cases, the name displayed on the [Verify website](https://verify.contentauthenticity.org) is the name of the exporter of the content, not the rights owner.
35
35
36
-
The ["Produced by" section](verify.mdx#produced-by) in Verify refers to the name of the exporter. If the image was created with an Adobe Product such as Photoshop with Content Credentials (Beta) enabled, the "Produced by" section shows the name of the Adobe ID associated with the user who exported the image.
36
+
The [Title and signgin information](verify.mdx#title-and-signing-information) in Verify refers to the name of the exporter. If the image was created with an Adobe Product such as Photoshop with Content Credentials (Beta) enabled, the "Produced by" section shows the name of the Adobe ID associated with the user who exported the image.
37
37
38
38
### Do Content Credentials indicate if an image is fake or altered?
This is a technical introduction to the Content Authenticity Initiative (CAI) open-source SDK that provides initial context and an overview of the technical aspects of implementing CAI solutions.
13
12
@@ -29,7 +28,7 @@ Now, let's drill down a bit to clarify some of these terms.
29
28
30
29
**Actor**: A human or hardware or software product. For example, a camera, image editing software, cloud service, or the person using such tools.
31
30
32
-
**Asset**: A digital media file or stream of data of [certain specific image, video, or audio formats](rust-sdk/#supported-file-formats). In the future, the types of supported assets will expand. A _composed asset_ generalizes this concept, for example an image superimposed on top of another image.
31
+
**Asset**: A digital media file or stream of data of [certain specific image, video, or audio formats](../rust-sdk/docs/supported-formats.md). A _composed asset_ generalizes this concept, for example an image superimposed on top of another image.
33
32
34
33
**Action**: An operation that an _actor_ performs on an _asset._ For example, "create," "embed," or "change contrast."
35
34
@@ -92,7 +91,7 @@ For more information on getting and using certificates, see [Signing and certifi
The C2PA [Verify tool](https://verify.contentauthenticity.org) uses a list of _known certificates_ (sometimes referred to as a "trust list") to determine whether a Content Credential was issued by a known source. Currently, it uses the [interim trust list](verify-known-cert-list) but it will be updated soon to use the official [C2PA trust list](conformance.mdx#c2pa-trust-lists).
The process described on this page is deprecated. The C2PA has released its official trust lists, and Verify will be updated to use them soon. See [Deprecation timeline](#deprecation-timeline) for more information.
@@ -37,7 +37,7 @@ For more information about conformance, see [C2PA conformance program](conforman
37
37
The Verify site hosts the following files that it uses to [validate signing certificates](https://c2pa.org/specifications/specifications/2.0/specs/C2PA_Specification.html#_c2pa_signers). Together, these files form the _interim known certificate list_:
38
38
39
39
-[**The interim end-entity certificate list**](https://github.com/contentauth/verify-site/blob/main/static/trust/allowed.pem) consists of end-entity certificates. If the certificate is on this list, it is considered "known." To reduce bandwidth consumption, a version with SHA-256 hashes of the certificates is also available.
40
-
-[**The interim known anchor list**](https://github.com/contentauth/verify-site/blob/main/static/trust/anchors.pem) contains the list of known anchor certificates. If an end-entity [certificate's chain](getting-started.mdx#signing-and-certificates) can be traced back to an anchor certificate on this list, the certificate is considered "known."
40
+
-[**The interim known anchor list**](https://github.com/contentauth/verify-site/blob/main/static/trust/anchors.pem) contains the list of known anchor certificates. If an end-entity [certificate's chain](index.mdx#signing-and-certificates) can be traced back to an anchor certificate on this list, the certificate is considered "known."
41
41
-[**The configuration file**](https://github.com/contentauth/verify-site/blob/main/static/trust/store.cfg) specifies the [Extended Key Usage (EKU)](https://datatracker.ietf.org/doc/html/rfc9336) values accepted for end-entity certificates. An end-entity certificate must have at least one of the EKUs in this list to be valid.
The C2PA **[Verify tool](https://verify.contentauthenticity.org)** (often referred to as simply "Verify") is useful both for consumers and for CAI application developers.
9
9
@@ -54,7 +54,7 @@ To use Verify on an asset URL, the URL must not require any authentication and t
54
54
55
55
### Example assets
56
56
57
-
The [example-assets](https://contentauth.github.io/example-assets/) repository contains some sample assets that demonstrate Content Credentials, including links to view the corresponding manifest reports from the [C2PA Tool](c2patool) and to inspect the assets using Verify. See [the README as rendered in GitHub Pages](https://contentauth.github.io/example-assets/).
57
+
The [example-assets](https://contentauth.github.io/example-assets/) repository contains some sample assets that demonstrate Content Credentials, including links to view the corresponding manifest reports from the [C2PA Tool](../c2patool/readme.md) and to inspect the assets using Verify. See [the README as rendered in GitHub Pages](https://contentauth.github.io/example-assets/).
58
58
59
59
### Source code
60
60
@@ -71,7 +71,7 @@ Once you've uploaded an asset or entered an asset URL, if the asset:
71
71
- Does not have an associated manifest store, Verify displays the message **No Content Credential**.
72
72
- Does have an associated manifest store, Verify displays information from it in the three vertical panels, for example as shown below.
@@ -176,7 +176,7 @@ For example, suppose you downloaded a file from Adobe Stock and renamed it `my_s
176
176
177
177
If the Content Credential was signed by a certificate that is NOT on the [known certificate list](verify-known-cert-list), such as one of the SDK's [test certificates](signing/test-certs.md), then Verify displays "Unrecognized" at the top of this section with this notice:
If one or more of the asset's ingredients was generated by artificial intelligence, as specified by the [generative AI action](manifest/assertions-actions#generative-ai-action), then a **Content summary** is shown and the **Process** section will also show the **AI tool used**, as shown in the example above.
336
+
If one or more of the asset's ingredients was generated by artificial intelligence, as specified by the [generative AI action](../manifest/writing/assertions-actions.md#generative-ai-action), then a **Content summary** is shown and the **Process** section will also show the **AI tool used**, as shown in the example above.
337
337
338
338
### About this Content Credential
339
339
340
340
This section displays the same information as described in [Title and singing information](#title-and-signing-information).
341
341
342
342
### Camera capture details
343
343
344
-
If the active manifest includes [Exif metadata assertions](manifest/assertions-actions#exif-assertion), then an additional **Camera capture details** section shows information about the device used to create the asset, as illustrated below:
344
+
If the active manifest includes [Exif metadata assertions](../manifest/writing/assertions-actions.md#cawg-metadata-assertions), then an additional **Camera capture details** section shows information about the device used to create the asset, as illustrated below:
0 commit comments