Release S2 connect version 1.0.0

structured-documentation/ControlType.toml

@@ -4,7 +4,7 @@ Describes a resource's control type(s).
 
 Control types describe how a resource is flexible. Typically, an RM will implement one control type, while a CEM will implement all five control types.
 """
-see_also = [{ name = "Guide to S2 control types", link = "https://docs.s2standard.org/docs/concepts/control-types/" }]
+see_also = [{ name = "Guide to S2 control types", link = "https://docs.s2standard.org/docs/learn/concepts/control-types/" }]
 
 [variants.POWER_ENVELOPE_BASED_CONTROL]
 variant_name = "POWER_ENVELOPE_BASED_CONTROL"

structured-documentation/EnergyManagementRole.toml

@@ -2,7 +2,7 @@ type_name = "EnergyManagementRole"
 description = """
 Describes whether a resource is an RM or CEM.
 """
-see_also = [{ name = "Guide to the S2 architecture", link = "https://docs.s2standard.org/docs/concepts/architecture/"}]
+see_also = [{ name = "Guide to the S2 architecture", link = "https://docs.s2standard.org/docs/learn/concepts/architecture/"}]
 
 [variants.CEM]
 variant_name = "CEM"

structured-documentation/SelectControlType.toml

@@ -5,7 +5,7 @@ Activates a Control Type for this session.
 
 This message is sent by the CEM to activate a Control Type for this session. The activated control type must be supported by the Resource Manager (as indicated in `ResourceManagerDetails` received by the CEM).
 """
-see_also = [{ name = "Guide to S2 control types", link = "https://docs.s2standard.org/docs/concepts/control-types/" }]
+see_also = [{ name = "Guide to S2 control types", link = "https://docs.s2standard.org/docs/learn/concepts/control-types/" }]
 
 [fields.control_type]
 field_name = "control_type"

website/docs/background/intro-energy-flexibility.md → website/docs/learn/background/intro-energy-flexibility.md

@@ -32,7 +32,7 @@ On the other hand, there are many types of optimizations an energy management sy
 
 With a common protocol for energy flexibility, any device can work with any energy management system. With a common protocol for energy flexibility, you are free to choose which devices you buy *and* the energy management system that optimizes energy flexibility the way you want.
 
-For more information on why S2 was designed the way it was designed, take a look at [Why the S2 approach?](/docs/background/why-the-s2-approach.md).
+For more information on why S2 was designed the way it was designed, take a look at [Why the S2 approach?](//learn/background/why-the-s2-approach.md).
 
 ## How does S2 relate to other protocols for energy management?
 How S2 relates exactly to another protocol of course depends on the other protocol. But most protocols out there tend to pick a type of device (e.g. EV charger, white goods) or pick an optimization (e.g. tariffs, grid signals). S2 is unique in that it is agnostic to both aspects.

website/docs/communication-layer/accepted-crypto.md → website/docs/learn/communication-layer/accepted-crypto.md

@@ -5,15 +5,15 @@ sidebar_position: 4
 
 ## Introduction
 
-In the [discovery and pairing specification](./discovery-pairing-authentication.md) a description is given of the required communication layer. This layer includes a description of encryption requirements. Because the security levels given by different crypto algorithms change continuously, this page contains the accepted crypto algorithms for the S2 protocol. Keep in mind that this will change over time.
+The S2 Connect specification contains a description of encryption requirements. Because the security levels given by different crypto algorithms change continuously, this page contains the accepted crypto algorithms for S2 Connect. Keep in mind that this will change over time.
 
 At the moment, we refer to the Mozilla guidelines in: [Server Side TLS](https://wiki.mozilla.org/Security/Server_Side_TLS). In the future these Mozilla guidelines will change, and S2 might have it's own list of accepted algorithms.
 
 ## Accepted algorithms will change
 
 As mentioned in the introduction, due developments in crypto technologies, security levels of known crypto algorithms will change over time. Algorithms that were considered safe 10 years ago, are unsafe at the moment. And algorithms that are considered safe today, might be vulnerable to new attacks in 5 years, or even tomorrow. And as we prepare for the imminent transition to post-quantum cryptography, our perception of the security of algorithms will most likely change.
 
-Therefore, this list will continuously change, and kept up to date. However, to engineer future proof systems, S2-nodes **SHOULD** be able to update their used crypto libraries, and hardware **SHOULD** be over-dimensioned. So, if the used crypto becomes obsolete newer, and possibly heavier, algorithms can be installed on the S2-node. When changes are made to the list of accepted crypto libraries, all S2Nodes **MUST** follow these changes within half a year.
+Therefore, this list will continuously change, and kept up to date. However, to engineer future proof systems, S2 nodes **SHOULD** be able to update their used crypto libraries, and hardware **SHOULD** be over-dimensioned. So, if the used crypto becomes obsolete newer, and possibly heavier, algorithms can be installed on the S2 node. When changes are made to the list of accepted crypto libraries, all S2Nodes **MUST** follow these changes within half a year.
 
 ## Accepted algorithms
 

website/docs/communication-layer/introduction.md → website/docs/learn/communication-layer/introduction.md

@@ -14,4 +14,6 @@ S2 was designed as a semantic protocol, which can have multiple, mutually compat
 * communication between a device endpoint in the cloud and an energy management system in the building
 * communication between different modules inside an energy management system
 
-S2 Connect specifies the discovery, pairing, communication and unpairing process between two S2 Connect capable devices.
+S2 Connect specifies the discovery, pairing, communication and unpairing process between two S2 Connect capable devices.
+
+Refer to [specification](/s2-connect/1.0.0/discovery-pairing-authentication) to read the S2-Connect specification.

website/docs/communication-layer/why-not-oauth.md → website/docs/learn/communication-layer/why-not-oauth.md

@@ -31,7 +31,7 @@ The device code flow of OAuth 2.0 ([RFC 8628](https://www.rfc-editor.org/rfc/rfc
 
 The end result is that the client has an access token (and potentially an refresh token) that would be used to authenticate when establishing a WebSocket connection.
 
-![image](../../static/img/communication-layer/oauth2-s2.png)
+![image](../../../static/img/communication-layer/oauth2-s2.png)
 <details>
 <summary>Image generated using the following PlantUML code:</summary>
 

website/docs/examples/ev.md → website/docs/learn/examples/ev.md

@@ -3,7 +3,7 @@ title: "Example: Electric Vehicle"
 hide_title: true
 ---
 
-![image not found](../../static/img/example-ev-header.png)
+![image not found](@site/static/img/example-ev-header.png)
 
 This page serves as a guide for implementing a S2 RM for an electric vehicle (charge point), or to give a CEM developer a better understanding of what to expect when controlling the energy flexibility of electric vehicles. It provides some example S2 messages for a (fictional) EV as well.
 
@@ -19,7 +19,7 @@ The battery management system in the EV consists of hardware and software that u
 In principle, the RM can be implemented either on EV level or on the charge point level. However, the availability of the required data for the RM depends on the interfaces between EV and charge point (so both the EV and the charge point need to support right interfaces). For example, some EVs do not share State-of-Charge (SoC) information with the charge point and, on the other hand, the EV typically doesn't know where it is connected in the grid. Depending on the energy flexibility use case and as long as the RM has the required data, it can be implemented both on EV or on charge point level. However, in a specific situation, there should only be one RM for the charger-EV combination.
 
 ## Choosing the right Control Type
-S2 is a language for conveying energy flexibility to the CEM without making any assumptions on what the CEM is optimizing for. Although there are multiple [Control Type(s)](/docs/concepts/control-types.md) that can be used for an EV, it is preferred to pick the one that conveys the most information and control options to the CEM, so the CEM can do the best optimization that adds the most value. In the ideal situation, the RM has access to the following data points:
+S2 is a language for conveying energy flexibility to the CEM without making any assumptions on what the CEM is optimizing for. Although there are multiple [Control Type(s)](learn/concepts/control-types.md) that can be used for an EV, it is preferred to pick the one that conveys the most information and control options to the CEM, so the CEM can do the best optimization that adds the most value. In the ideal situation, the RM has access to the following data points:
  - Minimum charging power (and discharging power, only relevant for V2G)
  - Maximum charging power (and discharging power, only relevant for V2G)
  - SoC at arrival
@@ -62,7 +62,7 @@ We cover the situation in which the RM has access to the following data:
 
 Furthermore, the RM can control the charging power of the EV such that it can set the power at any value between the minimum and maximum value.
 
-The following sequence diagram is an example of how a message exchange between the CEM and RM could look like, but messages could also be sent in a different order (see also [State of communication](/docs/communication-layer/discovery-pairing-authentication/#state-of-communication)). `ReceptionStatus` messages are omitted for readability.
+The following sequence diagram is an example of how a message exchange between the CEM and RM could look like, but messages could also be sent in a different order (see also [State of communication](/s2-connect/1.0.0/discovery-pairing-authentication/#state-of-communication)). `ReceptionStatus` messages are omitted for readability.
 
 ![cem_rm_interactions](https://www.plantuml.com/plantuml/png/VP7DJiCm3CVlUOey0F007D1W0x539TI2E9lKWcYf7MndQ3mzeI0HMCNLF_y_BA_KGAnCoH4RUjwZ-FLrT-Bxxjm_ujF0OOVc0nDXC1oTgzIVNipy5cZK5zYXw-TPHUrmQRD7pKoARYblIz4YfFXUSrhBAk8Y0JiWU4RPe45CsleFc33Ocic4q_qXB_itt4Emk0VxatJJNwtFXeCQJXlK835RP78kCMSVoHFx368nb0JYMKQKLdx7RoWTWXR12ScElI-35J2MmS2A7aTNL4_yfks5CzwIcfGmTsgapVXB-P17C7H8e_zi_gl6WAfriSVNWchk_x-FKNzUlwf-PKeV)
 <details>