divided into different sections

e-gov · Mar 3, 2025 · 145e3ee · 145e3ee
1 parent 668dec6
commit 145e3ee
Show file tree

Hide file tree

Showing 5 changed files with 31 additions and 13 deletions.
diff --git a/Integrating.md b/Integrating.md
@@ -0,0 +1,19 @@
+---
+permalink: Integrating
+---
+
+# Documentation for the developer implementing the integration with Pääsuke
+
+## Main ways to integrate with Pääsuke:
+1) The most common integration pattern is that integrator keeps authorisations (in payloads referred to as mandates) in Pääsuke and the integrator queries X-Road services [offered by Pääsuke](#specification-of-the-x-road-services-that-pääsuke-provides-to-other-parties).
+2) It is also possible to keep authorisations in Pääsuke, but use GovSSO service to access the authorisations. More info can be found from [GovSSO documentation](https://e-gov.github.io/GOVSSO/Representee).
+3) integrator keeps authorisations on their information system and Pääsuke queries X-Road services [offered to Pääsuke](#specification-of-the-x-road-services-that-pääsuke-queries-from-other-parties) by the integrator
+
+## Specification of the X-road services that Pääsuke provides to other parties
+
+[Oraakel](Oraakel) is the name of the service responsible for serving authorisations other parties
+
+## Specification of the X-road services that Pääsuke queries from other parties
+
+How to integrate [remote](Remote) systems that keep authorisations on their side but make them manageable from the Pääsuke user interface.
+
diff --git a/README.md b/README.md
@@ -0,0 +1,8 @@
+# Keskne volituste haldamise süsteem Pääsuke
+
+Vt lähemalt: [https://e-gov.github.io/PH-Doku/](https://e-gov.github.io/PH-Doku/)
+
+
+
+
+
diff --git a/_data/Riba.yml b/_data/Riba.yml
@@ -1,5 +1,7 @@
 - title: "Tutvustus"
   url: "/"
+- title: "Integrating"
+  url: "/Integrating"
 - title: "Oraakel"
   url: "/Oraakel"
 - title: "Remote authorisations"

diff --git a/_includes/Jalus.html b/_includes/Jalus.html
@@ -1,6 +1,6 @@
 <div class='jalus'>
   <p>
-    <a href='https://www.ria.ee'>Riigi Infosüsteemi Amet</a> · 2023-2024 ·
+    <a href='https://www.ria.ee'>Riigi Infosüsteemi Amet</a> · 2024 - 2025 ·
     <a href='{{site.repo }}'>{{ site.repo }}</a>
   </p>
 </div>
diff --git a/index.md b/index.md
@@ -5,18 +5,7 @@
 
 # Documentation for the developer implementing the integration with Pääsuke
 
-## Main ways to integrate with Pääsuke:
-1) The most common integration pattern is that integrator keeps authorisations (in payloads referred to as mandates) in Pääsuke and the integrator queries X-Road services [offered by Pääsuke](#specification-of-the-x-road-services-that-pääsuke-provides-to-other-parties).
-2) It is also possible to keep authorisations in Pääsuke, but use GovSSO service to access the authorisations. More info can be found from [GovSSO documentation](https://e-gov.github.io/GOVSSO/Representee).
-3) integrator keeps authorisations on their information system and Pääsuke queries X-Road services [offered to Pääsuke](#specification-of-the-x-road-services-that-pääsuke-queries-from-other-parties) by the integrator
-
-## Specification of the X-road services that Pääsuke provides to other parties
-
-[Oraakel](Oraakel) is the name of the service responsible for serving authorisations other parties
-
-## Specification of the X-road services that Pääsuke queries from other parties
-
-How to integrate [remote](Remote) systems that keep authorisations on their side but make them manageable from the Pääsuke user interface.
+Instructions for [integrating](Integrating) any system with Pääsuke.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,8 @@
		# Keskne volituste haldamise süsteem Pääsuke

		Vt lähemalt: [https://e-gov.github.io/PH-Doku/](https://e-gov.github.io/PH-Doku/)