Signatures update: expand introduction

src/pages/signatures/getting-started/index.mdx

@@ -40,7 +40,19 @@ export const pageQuery = gatsbyGraphql`
   }
 `;
 
-Below you will find a list of topics to get you started with Idura Signatures:
+<Highlight icon="info">
+
+**How to set up a basic signing flow with Idura Signatures API:**
+
+0. _Prerequisite:_ create an Idura Signatures application to get a set of client credentials.
+1. Create a signature order with one or more PDFs for signing.
+2. Add one or more signatories.
+3. Redirect each signatory to their unique signing link and wait for them to sign.
+4. Close the signature order to retrieve the signed PDFs.
+
+</Highlight>
+
+Choose a topic below to get started:
 
 <ul>
   {props.data.pages.edges

src/pages/signatures/index.mdx

@@ -1,12 +1,30 @@
 ---
 product: signatures
 title: Idura Signatures
-subtitle: Sign documents with national eIDs and the PAdES standard
+subtitle: Sign documents with national eIDs and the PAdES standard.
 ---
 
-Idura Signatures allows you to sign any PDF document using all the [national eIDs](/verify/e-ids/) supported by Idura Verify.
+Idura Signatures allows you to sign any PDF document using the [national eIDs](/verify/e-ids/) supported by Idura Verify.
+The signed documents are compliant with the [PAdES-LTA standard](https://www.idura.eu/blog/pades-signature-levels-explained).
 
-Documents will be produced according to the [PAdES-LTA standard](https://www.idura.eu/blog/pades-signature-levels-explained).
+<Highlight icon="info">
 
-- **Getting Started**. If you are new to GraphQL or have not yet registed a Idura Signatures application, please follow our [Getting Started guide](/signatures/getting-started/register-application).
+Idura Signatures is designed to be embedded into your application. This means there is no _signing portal_ where you run the process from.
+Instead, you create a signing process using the Signatures GraphQL API, then redirect each user to a unique signing link in the Idura-hosted signatory UI.
+Once all users have signed, you retrieve the signed documents via the API.
+
+</Highlight>
+
+### Terms and definitions
+
+- **Signature order**: a basic building block of the Signatures API. Contains documents and the signatories you intend to sign them.
+- **Document(s)**: PDF(s) included in the signature order.
+- **Signatory**: a person invited to sign the document. Each signatory gets a unique signing link.
+- **Signature seal**: a visual representation of the signature placed on the document. It can contain details such as document ID, time of signing, and other information that can be found in the claims (via templating).
+
+- [**Webhooks**](/signatures/webhooks/): a tool for receiving near real-time events in your signature orders (e.g., when a signatory has signed).
+
+### How to get started
+
+- **Getting Started**. If you are new to GraphQL or have not yet registered an Idura Signatures application, please follow our [Getting Started guide](/signatures/getting-started).
 - **GraphQL**. The Idura Signatures API is built with GraphQL, enabling you to create unique workflows tailored to your needs. Have a look at our [GraphQL Examples](/signatures/graphql/examples) to see how it works in practice.