diff --git a/app/_meta.js b/app/_meta.js
index 5a9170e..fcc5dc9 100644
--- a/app/_meta.js
+++ b/app/_meta.js
@@ -1,16 +1,15 @@
export default {
index: {
- display: "hidden"
+ display: "hidden",
},
-
// Welcome Report URL redirect, never show in nav
five_safes_tes: {
- display: "hidden"
+ display: "hidden",
},
// exclude routes until content published
- "journeys": {
- display: "hidden"
+ journeys: {
+ display: "hidden",
},
// TODO: restructure content and move "connect" journey page
diff --git a/app/journeys/learn/what-is-five-safes/page.mdx b/app/journeys/learn/what-is-five-safes/page.mdx
deleted file mode 100644
index 5ba0197..0000000
--- a/app/journeys/learn/what-is-five-safes/page.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-# TODO: move to correct structure when content added
----
-
-import { UnderConstruction } from "@/components/UnderConstruction";
-
-
\ No newline at end of file
diff --git a/app/learn/_meta.js b/app/learn/_meta.js
new file mode 100644
index 0000000..f4d0e12
--- /dev/null
+++ b/app/learn/_meta.js
@@ -0,0 +1,4 @@
+export default {
+ "what-is-five-safes-tes": "What is Five Safes TES?",
+ personas: "Personas",
+};
diff --git a/app/journeys/learn/personas/page.mdx b/app/learn/page.mdx
similarity index 50%
rename from app/journeys/learn/personas/page.mdx
rename to app/learn/page.mdx
index 5ba0197..bc12f61 100644
--- a/app/journeys/learn/personas/page.mdx
+++ b/app/learn/page.mdx
@@ -1,7 +1,10 @@
---
-# TODO: move to correct structure when content added
+title: Learn
+asIndexPage: true
---
import { UnderConstruction } from "@/components/UnderConstruction";
-
\ No newline at end of file
+
+
+# Learn
diff --git a/app/learn/personas/page.mdx b/app/learn/personas/page.mdx
new file mode 100644
index 0000000..1d7a0ed
--- /dev/null
+++ b/app/learn/personas/page.mdx
@@ -0,0 +1,67 @@
+---
+title: Personas
+readingTime: PT5M
+audiences: everyone
+docType: explanation
+---
+
+import { DocMetadata } from "@/components/doc-metadata/DocMetadata";
+import { Table } from "nextra/components";
+
+
+
+# Overview
+
+Key to the successful adoption and implementation of Five Safes TES is understanding who will interact with the solution. To characterise our users we have identified the following personas:
+
+- TRE operators
+- Federation operators
+- Researchers
+- Developers (emerging)
+- Innovators (emerging)
+
+## TRE operators
+
+TREs operators are responsible for the management of the Trusted Research Environments (TREs) IT infrastructure. TRE operators are inclusive of governance, data management, and infrastructure management roles.
+
+This description has been adopted from [SATRE](https://satre-specification.readthedocs.io/en/stable/roles.html#infrastructure-management-roles).
+
+The responsibilities of TRE operators are defined through the [SATRE specification](https://satre-specification.readthedocs.io/en/latest/index.html):
+
+- [Information Governance](https://satre-specification.readthedocs.io/en/stable/specification.html#information-governance): Quality management, risk management, training delivery, member accreditation, and governance procedures that ensure TREs operate safely and ethically.
+- [Computing Technology](https://satre-specification.readthedocs.io/en/stable/specification.html#computing-technology-and-information-security): End-user computing experience, infrastructure management, information security, and configuration management for secure data analysis environments.
+- [Data Management](https://satre-specification.readthedocs.io/en/stable/specification.html#data-management): Data lifecycle management, identity and access management, output management, information discovery, and research metadata capabilities.
+- [Supporting Capabilities](https://satre-specification.readthedocs.io/en/stable/specification.html#supporting-capabilities): Financial management, public engagement and involvement, project management, procurement, and other essential operational functions.
+
+## Federation operators
+
+Federation operators provide oversight, policy and decision-making for a federation of TREs, ensuring consistent standards and accountability.
+
+This description has been adopted from [SATRE](https://satre-specification.readthedocs.io/en/stable/roles.html#infrastructure-management-roles).
+
+The responsibilities of Federation operators are defined through the [SATRE specification](https://satre-specification.readthedocs.io/en/latest/index.html):
+
+- Federation governance, member accreditation, study management, information security, infrastructure management, data management, and financial management across multiple federated TRE partners.
+
+## Researchers
+
+Researchers are provided access to data via a TRE, who intend to carry out analysis or conduct research using the data.
+
+The responsibilities of a Researcher have been adopted from the [UK Data Service](https://ukdataservice.ac.uk/learning-hub/research-data-management/ethical-issues/ethical-obligations/):
+
+- Research should maximise benefits for individuals and society and minimise risk and harm.
+- The rights and dignity of individuals and groups should be respected.
+- Wherever possible, participation should be voluntary and appropriately informed.
+- Research should be conducted with integrity and transparency.
+- Lines of responsibility and accountability should be clearly defined.
+- Independence of research should be maintained and where conflicts of interest cannot be avoided they should be made explicit.
+
+{/* TODO: when we have pages about Developers and Innovators, we need to add the content for them here */}
+
+## What's next?
+
+Depending on your interests, you may want to read the following pages:
+
+- TRE operators - [Connect](/connect)
+- Federation operators - [Co-ordinate](/co-ordinate)
+- Researchers - [Analyse](/analyse)
diff --git a/app/learn/what-is-five-safes-tes/page.mdx b/app/learn/what-is-five-safes-tes/page.mdx
new file mode 100644
index 0000000..5fa0535
--- /dev/null
+++ b/app/learn/what-is-five-safes-tes/page.mdx
@@ -0,0 +1,61 @@
+---
+title: What is 5S-TES?
+readingTime: PT5M
+audiences: everyone
+docType: explanation
+---
+
+import { DocMetadata } from "@/components/doc-metadata/DocMetadata";
+
+
+
+## Prerequisites
+
+- Basic understanding of the definition of a [TRE](https://glossary.uktre.org/en/stable/#term-trusted-research-environment--tre-)
+- Basic understanding of the definition of a [federation](https://glossary.uktre.org/en/stable/#term-federation)
+
+## Overview
+
+Five Safes TES (5S-TES) enables secure cross-TRE federated analytics, where data remains in place and only analysis code is sent to the data.
+Building upon the Five Safes framework and the Task Execution Service (TES) standards, it is specifically designed to meet technical and governance constraints of TREs by separating the stages of a federated project.
+
+## The Five Safes framework
+
+
+
+A set of principles that guide a data services provision of safe research access to data, These interlocking principles include:
+
+- Safe Data
+- Safe Project
+- Safe People
+- Safe Settings
+- Safe Outputs
+
+To learn more, visit the resources at [UK Data Services](https://ukdataservice.ac.uk/help/secure-lab/what-is-the-five-safes-framework/).
+
+## Global Alliance for Genomics & Health - Task Execution Service (GA4GH TES)
+
+
+
+Developed by the Global Alliance for Genomics & Health (GA4GH), the Task Execution Service provides a standard mechanism for orchestrating complex analyses across different compute environments.
+
+To learn more, visit the [GA4GH TES product page](https://www.ga4gh.org/product/task-execution-service-tes/).
+
+## Bringing it together
+
+Five Safes TES (5S-TES) is a collaboration between Swansea University and the University of Nottingham, focused on delivering new capability to existing research data infrastructure.
+
+By combining international standards, 5S-TES:
+
+- enhances GA4GH TES to receive and process federated analysis requests from multiple TREs.
+- supports Safe Data through configuration of specific and timebound data access for users.
+- performs analyses only for a project that has been approved by the TRE, deeming them a Safe Project.
+- only permits research users that have been accredited and established, indicating them as Safe People.
+- maintains Safe Setting with execution of analysis occurring within a TRE.
+- provides manual disclosure control functionality within TREs, adhering to Safe Outputs.
+
+This solution is foundational to the various programmes, including [HDR UK Federated Analytics](https://www.hdruk.ac.uk/research/research-data-infrastructure/federated-analytics/), [DARE UK TREvolution programme](https://dareuk.org.uk/trevolution/), and [EOSC-ENTRUST](https://www.eosc-entrust.eu/).
+
+## What's next?
+
+- [System Context overview](/learn/system-context)
diff --git a/app/page.mdx b/app/page.mdx
index 0bc06c0..192e2c5 100644
--- a/app/page.mdx
+++ b/app/page.mdx
@@ -5,7 +5,7 @@ import {
Share2,
Microscope,
Boxes,
- ChevronRight
+ ChevronRight,
} from "lucide-react";
import CustomCard from "@/components/CustomCard";
@@ -16,53 +16,86 @@ import CustomCard from "@/components/CustomCard";
title="Learn"
description="Understand the core concepts, standards, and users of Five Safes TES"
links={[
- { title: "What is Fives Safes TES ", href: "/journeys/learn/what-is-five-safes" },
+ { title: "What is Fives Safes TES ", href: "/learn/what-is-five-safes-tes" },
{ title: "OMOP", href: "/journeys/learn/omop" },
- { title: "Personas", href: "/journeys/learn/personas" },
+ { title: "Personas", href: "/learn/personas" },
{ title: "System Architecture", href: "/journeys/learn/system-architecture" },
]}
CTA={{ text: <>Learn >, href: "/journeys/learn" }}
icon={}
/>
- Connect >, href: "/journeys/connect" }}
- icon={}
- />
+
+ Connect
+ >
+ ),
+ href: "/journeys/connect",
+ }}
+ icon={}
+/>
- Research >, href: "/journeys/research" }}
- icon={}
- />
+
+ Research
+ >
+ ),
+ href: "/journeys/research",
+ }}
+ icon={}
+/>
- Co-ordinate >, href: "/journeys/co-ordinate" }}
- icon={}
- />
+
+ Co-ordinate
+ >
+ ),
+ href: "/journeys/co-ordinate",
+ }}
+ icon={}
+/>
Integrate >, href: "/journeys/integrate" }}
icon={}
- />
+/>