30. May 2023

[dimakuv]

Agenda

(please write your proposed agenda items in comments under this discussion)

• Michal, Dmitrii, Mona, Benny: discuss and finalize the documentation structure

Documentation reorg

Two separate discussions:

1. Do we stick to "Gramine as SGX framework" (as done now), or do we make it more generic "Gramine as compatibility framework".
2. How do we set up the Table of Contents (ToC)? What do we do with pages that fit in both "Protect your container" and "Protect your application"?

Mona: What about we re-add the "Configure Gramine" section at the very top, with subsections "Set up the environment" (and then SGX, TDX, signing key), "Manifest syntax", "Attestation", and so on.

Woju: We need a landing/introduction page. It will describe first the SGX/Confidential Computing concepts, otherwise people shouldn't even try Gramine (if they don't know about SGX, attestation, etc., then they shouldn't start working on Confidential Computing workloads).

Woju doesn't like imperative titles "Protect ...", "Develop ...". This style is called "Call To Action" and used in more marketing-oriented situations, but this doesn't fit into the technical documentation.

Woju's proposal of the structure:

Tutorials (quickstarts)
  Deploy ready-made SGX images
  Deploy your SGX images on Azure
  Deploy your SGX images with GSC (locally)
  Deploy your app on Azure
  Deploy your app on bare metal Debian/Ubuntu
  ...

Set up the environment
  SGX configuration
  <  e.g. TDX configuration in the future >
  Signing key

Install Gramine
  Official Docker image
  Packages

Configure Gramine
  Manifest
  Attestation
  Performance tuning

... and the rest as currently is ...

After long discussions, final agreed upon structure:

Protect your container
  ...

Protect your app
  ...

Configure Gramine
  Set up host environment
    SGX configuration
    <  e.g. TDX configuration in the future >
    ...
  Manifest
  Attestation
  Performance tuning
  
... and the rest as currently is ...