From 130d4fe7e95374fa10261b75710d478c94b5179e Mon Sep 17 00:00:00 2001
From: Pierre Terree <pierre.terree@calypsonet.org>
Date: Sat, 9 Nov 2024 22:19:53 +0400
Subject: [PATCH] fix intro

---
 config/_default/menus.yaml       |  4 ++++
 content/home/hero.md             | 15 +++------------
 content/specifications/_index.md | 12 +++++++++---
 3 files changed, 16 insertions(+), 15 deletions(-)

diff --git a/config/_default/menus.yaml b/config/_default/menus.yaml
index 52096f1..893371e 100644
--- a/config/_default/menus.yaml
+++ b/config/_default/menus.yaml
@@ -27,6 +27,10 @@ main:
     parent: Community
     url: '/project-dashboard/'
     weight: 30
+  - name: Support
+    parent: Community
+    url: 'https://keyple-support.calypsonet.org/keyple-support/introduction/'
+    weight: 35
   - name: Archives
     parent: Community
     url: '/archives/'
diff --git a/content/home/hero.md b/content/home/hero.md
index a1aa188..08f6834 100644
--- a/content/home/hero.md
+++ b/content/home/hero.md
@@ -15,19 +15,10 @@ hero_media = "hero-image.svg"
   #text_color_light = true
 
 +++
-In order to facilitate the design of terminals processing smartcard readers (user card, security module), CNA (the [Calypso Networks Association](https://calypsonet.org/)) has standardized [software interfaces for ticketing terminals](https://calypsonet.org/calypso-for-terminals/#section-interoperability-and-portability-of-ticketing-terminal-solutions).
+To facilitate the design of terminals processing smartcard readers (user card, security module), CNA (the [Calypso Networks Association](https://calypsonet.org/)) has standardized [software interfaces for ticketing terminals]({{< relref "specifications" >}}).
+
 This solution enables:
 - _any_ **smart card reader solution** to be operated _independently_ of the **terminal architecture**,
 - and _any_ **ticketing applications** to be ported _independently_ of the **terminal products** supplied by manufacturers.
 
-First solutions translating these interface definitions into programming languages, or implementing these interfaces, are [available](https://terminal-api.calypsonet.org/implementations/).
-
-<br>2 levels of APIs are offered, from the lowest to the highest:
-- at the bottom the ['reader layer'](https://terminal-api.calypsonet.org/specifications/reader-layer/) _generic_ interfaces:
-  - the [**Reader**](https://terminal-api.calypsonet.org/specifications/reader-layer/reader-api/) **API** to control any reader solution and manage the application selection on a smart card,
-  - the [**Card**](https://terminal-api.calypsonet.org/specifications/reader-layer/card-api/) **API** for interfacing a card processing library specific to a smart card solution.
-- Just below 'smartcard solution layer' _specific_ interfaces:
-  - several interfaces to integrate [Calypso processing](https://terminal-api.calypsonet.org/specifications/calypso-layer/) support:
-    - [**Card**](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-card-api/) and **[Legacy SAM](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-legacysam-api/) API**s to perform secure transactions with Calypso cards or with Calypso security modules such as SAM-S1 or SAM-C1.
-    - [**Symmetric Crypto**](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-symmetric-crypto-api/) and **[Asymmetric Crypto](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-asymmetric-crypto-api/) API**s to interface Calypso SAM or Calypso PKI processing libraries.
-
+[First solutions]({{< relref "implementations" >}}) translating these interface definitions into programming languages, or implementing these interfaces, are available.
\ No newline at end of file
diff --git a/content/specifications/_index.md b/content/specifications/_index.md
index 1eaeadb..458c568 100644
--- a/content/specifications/_index.md
+++ b/content/specifications/_index.md
@@ -6,7 +6,13 @@ weight: 0
 toc: false
 search: false
 ---
+This section lists the specifications associated to the [Reader]({{< relref "reader-layer" >}}) & [Calypso]({{< relref "calypso-layer" >}}) layers.
 
-<br>
-
-This section lists the specifications associated to the [Reader]({{< relref "reader-layer" >}}) & [Calypso]({{< relref "calypso-layer" >}}) layers.
\ No newline at end of file
+<br>2 levels of APIs are offered, from the lowest to the highest:
+- at the bottom the ['reader layer'](https://terminal-api.calypsonet.org/specifications/reader-layer/) _generic_ interfaces:
+    - the [**Reader**](https://terminal-api.calypsonet.org/specifications/reader-layer/reader-api/) **API** to control any reader solution and manage the application selection on a smart card,
+    - the [**Card**](https://terminal-api.calypsonet.org/specifications/reader-layer/card-api/) **API** for interfacing a card processing library specific to a smart card solution.
+- Just below 'smartcard solution layer' _specific_ interfaces:
+    - several interfaces to integrate [Calypso processing](https://terminal-api.calypsonet.org/specifications/calypso-layer/) support:
+        - [**Card**](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-card-api/) and **[Legacy SAM](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-legacysam-api/) API**s to perform secure transactions with Calypso cards or with Calypso security modules such as SAM-S1 or SAM-C1.
+        - [**Symmetric Crypto**](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-symmetric-crypto-api/) and **[Asymmetric Crypto](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-asymmetric-crypto-api/) API**s to interface Calypso SAM or Calypso PKI processing libraries.