People could collaborate on blogs on a shared google document. So, add instructions on how someone can convert the google doc to markdown in Writing a blog section of contributor's guide.

• Install Pandoc.
• Download the Google document in "Microsoft Word (.docx)" format.
• Then go to the folder for writing the blog:

export INPUT_FILE=""                        # This should be the file with .docx extension
export OUTPUT_FILE=""                       # This should be the file with .md extension
cd content/en/blog/2024

pandoc -t markdown_strict --extract-media . $INPUT_FILE -o $OUTPUT_FILE

Move this document to the website: https://github.com/confidential-containers/confidential-containers/blob/main/trust_model.md

As part of our ongoing effort to cncf/techdocs#198, we noticed that the website does not pass the trademark criteria on CLOMonitor.

To fix this:
Head to the source code of the website. In the <footer> section, add a disclaimer or link to the Linux foundation trademark disclaimer page:

Disclaimer

<footer>
   <p>The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, 
         please see our <a href="https://www.linuxfoundation.org/legal/trademark-usage">Trademark Usage page</a>.
   </p>
</footer>

Link

 <footer>
      <ul>
          <li><a href="https://www.linuxfoundation.org/legal/trademark-usage">Trademarks</a></li>
      </ul>
 </footer>

Once the first ever blog on coco website is published then clean up the "place holder" blogs.

https://github.com/confidential-containers/confidential-containers/blob/main/trust_model_personas.md

This video showcases how one can read the memory of an app if they have access to the worker node. So this video emphasizes the importance of the CoCo and what value it brings to the table: https://www.youtube.com/watch?v=zZsB8S24CU4

• Upload video to the CoCo channel https://www.youtube.com/@confidentialcontainers3845
• Add the video in a post (could be a demo / quick start / blog) something like that.

I'm not sure we need to reflect the repo structure or just list the individual components, I think the latter is better, but at the moment guest-components is split while kbs + attestation-service have individual entries

• General CAA docs

  • User facing: https://confidentialcontainers.org/docs/cloud-api-adaptor/ The corresponding GH markdown page is here: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/cloud-api-adaptor/_index.md

• AWS

  • User facing: https://confidentialcontainers.org/docs/cloud-api-adaptor/aws/ Corresponding GH markdown page: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/cloud-api-adaptor/aws/_index.md

• Azure

  • User facing: https://confidentialcontainers.org/docs/cloud-api-adaptor/azure/ Corresponding GH markdown page: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/cloud-api-adaptor/azure/_index.md
  • Building PodVM image: https://confidentialcontainers.org/docs/cloud-api-adaptor/azure/build-image/ Corresponding GH markdown page: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/cloud-api-adaptor/azure/build-image.md

• IBM Cloud

  • User facing: https://confidentialcontainers.org/docs/cloud-api-adaptor/ibm-cloud/ Corresponding GH markdown page: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/cloud-api-adaptor/ibm-cloud/_index.md

• Libvirt

  • User facing: https://confidentialcontainers.org/docs/cloud-api-adaptor/libvirt/ Corresponding GH markdown page: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/cloud-api-adaptor/libvirt/_index.md

• Website: https://confidentialcontainers.org/docs/overview/
• User facing: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/overview/_index.md

• Kata Containers landing page

  • Website: https://confidentialcontainers.org/docs/kata-containers/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/kata-containers/_index.md

• Kata Confidential Containers landing page:

  • Website: https://confidentialcontainers.org/docs/kata-containers/kata-confidential-containers/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/kata-containers/kata-confidential-containers.md

• Landing page:

  • Website URL: https://confidentialcontainers.org/docs/guest-components/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/guest-components/_index.md

• API Server Rest:

  • Website: https://confidentialcontainers.org/docs/guest-components/api-server-rest/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/guest-components/api-server-rest/_index.md

• Attestation Agent:

  • Website: https://confidentialcontainers.org/docs/guest-components/attestation-agent/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/guest-components/attestation-agent/_index.md

• CDH

  • Website: https://confidentialcontainers.org/docs/guest-components/confidential-data-hub/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/guest-components/confidential-data-hub/_index.md

• Image-RS

  • Website: https://confidentialcontainers.org/docs/guest-components/image-rs/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/guest-components/image-rs/_index.md

• OCICrypt-RS

  • Website: https://confidentialcontainers.org/docs/guest-components/ocicrypt-rs/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/guest-components/ocicrypt-rs/_index.md

The landing page has some info: https://confidentialcontainers.org/ and then the about page also has some info which kinda seem redundant: https://confidentialcontainers.org/about/ do we need both of them? Can we try and consolidate both of them into one?

GH Links:

• Landing Page: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/_index.md
  • The content here is mostly copied / adapted from: https://github.com/confidential-containers/.github/blob/main/profile/README.md. This page shows up when one goes to: https://github.com/confidential-containers/
• About: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/about/index.md
  • This page was copied from: https://github.com/confidential-containers/confidential-containers

Once added, add the id here:

• Landing page:
  • Website: https://confidentialcontainers.org/docs/key-broker-service/
  • GH: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/key-broker-service/_index.md

With the help of @Xynnn007 I have identified the following changes needed for the trustee repo:

• Move the KBS and AS under one subsection trustee https://confidentialcontainers.org/docs/attestation-service/ and https://confidentialcontainers.org/docs/key-broker-service/

Attestation Service

• Port some of the AS user docs from the main readme https://github.com/confidential-containers/trustee/tree/main/attestation-service to https://confidentialcontainers.org/docs/attestation-service/
• Port the quickstarts for AS to the website:
  • https://github.com/confidential-containers/trustee/blob/main/attestation-service/docs/restful-as.md
  • https://github.com/confidential-containers/trustee/blob/main/attestation-service/docs/grpc-as.md
  • https://github.com/confidential-containers/trustee/blob/main/attestation-service/docs/parsed_claims.md

Key Broker Service:

• Either remove / completely overhaul the documentation: https://confidentialcontainers.org/docs/key-broker-service/. Take inspiration from the actual KBS readme: https://github.com/confidential-containers/trustee/blob/main/kbs/README.md

• Port the KBS docs to the website:

  • https://github.com/confidential-containers/trustee/blob/main/kbs/quickstart.md
  • how to set up trustee(KBS/AS/RVPS) with docker-compose: https://github.com/confidential-containers/trustee/blob/main/kbs/docs/cluster.md

• KBS protocol: https://github.com/confidential-containers/trustee/blob/main/kbs/docs/kbs_attestation_protocol.md

• KBS storage backend / resource repository support: https://github.com/confidential-containers/trustee/blob/main/kbs/docs/resource_repository.md

• How to run KBS with self-signed https cert: https://github.com/confidential-containers/trustee/blob/main/kbs/docs/self-signed-https.md

The image on the landing page crops the text on phone like this:

But it works fine on larger screens:

Recreate the demo here and update the documentation accordingly.

• CCv0 Operator Demo

  • User facing link: https://confidentialcontainers.org/docs/demos/ccv0-operator-demo/
  • Markdown: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/demos/ccv0-operator-demo.md
  • Once updated add a redirect link to the demo doc instead of the actual demo here:
    https://github.com/confidential-containers/confidential-containers/tree/main/demos/operator-demo

• SSH Demo

  • User facing link: https://confidentialcontainers.org/docs/demos/ssh-demo/
  • Markdown: https://github.com/confidential-containers/confidentialcontainers.org/blob/main/content/en/docs/demos/ssh-demo/index.md
  • Once updated add a redirect link to the demo doc from the confidentialcontainers.org instead of the actual demo here: https://github.com/confidential-containers/confidential-containers/tree/main/demos/ssh-demo