Added page for ending the beta

.gitignore

@@ -36,4 +36,7 @@ target/
 
 # node modules
 node_modules/
-.env
+.env
+
+package-lock.json
+yarn.lock

modules/ROOT/content-nav.adoc

@@ -1,4 +1,4 @@
 * xref:index.adoc[Introduction]
 
 * *Getting started*
 
@@ -61,6 +61,8 @@
 ** xref:aura-graphql/deploy-and-operate.adoc[]
 ** xref:aura-graphql/authentication-providers.adoc[]
 ** xref:aura-graphql/using-your-api.adoc[]
+** xref:aura-graphql/ending-of-beta-phase.adoc[]
+
 
 * xref:introspector.adoc[Introspector]
 

modules/ROOT/pages/aura-graphql/end-of-beta-phase.adoc

@@ -0,0 +1,166 @@
+= End of beta phase
+
+The beta phase of GraphQL for Neo4j AuraDB will end on the 18th of April 2025.
+To prevent data loss and wrap up your beta experience we suggest you take the following steps:
+
+* Backup GraphQL Data API configuration
+* Remove the GraphQL Data API
+* Provide feedback 
+
+You are not required to take action.
+However, any running GraphQL Data API will be terminated after the 18th of April, resulting in the loss of its configuration information including type definitions.
+
+
+== Backup the GraphQL Data API configuration
+
+Backing up your GraphQL Data API configuration makes re-use much quicker if you decide to use this feature once it is released.
+If you want to run your own GraphQL service instead, the backup might still be useful since it includes the type definitions which can be used for that purpose.
+
+There are two ways to perform a backup:
+
+* Manually copy them one by one from the Aura Console
+* Using the Aura CLI to obtain everything in a single operation
+
+
+=== Console
+
+If you want to retain only parts of the configuration, this is a quick method to do so.
+If you are intent on backing up all of the configuration, use the xref:#_aura_cli[] instead.
+
+1. On Aura Console, select **Data API** from the left side navigation.
++
+image::aura-graphql/console_data_api_sidebar.png[]
++
+2. The table shows your GraphQL Data APIs. Use the three dots on the row with the GraphQL Data API that you wish to backup and select **Edit**.
++
+image::aura-graphql/console_data_api_edit_menu.png[]
++
+3. Expand each of the sections and then make a note of the setting or copy as necessary.
++
+image::aura-graphql/console_data_api_edit.png[]
+
+
+=== Aura CLI
+
+This section assumes that you have configured the Aura CLI.
+If you have not, follow the guidance provided in  xref:aura-graphql/prerequisites.adoc#_install_and_configure_the_aura_cli[].
+
+
+1. Look up the Aura instance ID that the GraphQL API is being used with.
++
+[source, bash, indent=0]
+----
+aura-cli instance list --output table
+----
++
+
+2. From the displayed table, make a note of relevant Aura ID. Use this ID to obtain the ID of the GraphQL API whose configuration you want to back up.
++
+[source, bash, indent=0]
+----
+aura-cli data-api graphql list --instance-id YOUR_AURA_INSTANCE_ID --output table
+----
++
+
+3. Finally, obtain the configuration of the GraphQL API itself in JSON format.
++
+[source, bash, indent=0]
+----
+aura-cli data-api graphql get  YOUR_GRAPHQL_DATA_API_ID  --instance-id YOUR_AURA_INSTANCE_ID 
+----
++
+4. Save the output for future use.
+
+[NOTE]
+====
+Type definitions are stored using Base64 encoding.
+Decode them to plain text before using with other systems.
+====  
+
+
+== Removing the GraphQL Data API
+
+Remove the GraphQL Data API either via Aura Console or with the Aura CLI.
+
+[WARNING]
+====
+Once the GraphQL Data API has been deleted, it cannot be recovered.  
+====
+
+
+=== Console
+
+1. In Aura Console, select **Data API** from the left side navigation.
++
+image::aura-graphql/console_data_api_sidebar.png[]
++
+2. The table contains your GraphQL Data APIs. Use the three dots on the row with the GraphQL Data API that you wish to remove and select **Delete**. 
++
+image::aura-graphql/console_data_api_delete_menu.png[]
++
+3. Type in the name of your GraphQL API and confirm with **Delete**.
++
+image::aura-graphql/console_data_api_confirm_delete_menu.png[]
+
+
+=== Aura CLI 
+
+This section assumes that you have configured the Aura CLI.
+If you have not, follow the guidance provided in  xref:aura-graphql/prerequisites.adoc#_install_and_configure_the_aura_cli[].
+
+1. Locate the Aura instance ID that the GraphQL API is being used with.
++
+[source, bash, indent=0]
+----
+aura-cli instance list --output table
+----
++
+2. From the displayed table, make a note of the relevant Aura ID. Use the ID to obtain the ID of the GraphQL API whose configuration you want to back up.
++
+[source, bash, indent=0]
+----
+aura-cli data-api graphql list --instance-id YOUR_AURA_INSTANCE_ID --output table
+----
++
+3. Delete the GraphQL API.  
++
+[WARNING]
+====
+The Aura CLI does not ask for confirmation and processes the command immediately.  
+====
++
+[source, bash, indent=0]
+----
+aura-cli data-api graphql delete YOUR_GRAPHQL_DATA_API_ID  --instance-id YOUR_AURA_INSTANCE_ID --output table
+----
+
+
+== Provide feedback 
+
+We encourage feedback because it directly impacts the final product. Here's why it matters:
+
+[square]
+* Shape the Product
++ 
+Your feedback helps us refine features, fix bugs, and improve usability based on real user experiences.
+
+
+* Get a Product That Works for You
++ 
+By sharing your thoughts, you influence the design and functionality to better meet your needs.
+
+
+* Catch Issues Early
++ 
+Beta testing allows early identification and resolution of problems before the full release, ensuring a smoother experience.
+
+
+* Improve Performance and Reliability
++ 
+We rely on real-world usage data to optimize speed, stability, and efficiency.
+
+
+By providing feedback, you're not just testing a product—you’re helping build a better one.
+
+Please take a few moments to do this in our GitHub repository by (https://github.com/neo4j/graphql/issues/new/choose)[creating an issue] or mailto:jon.giffard@neo4j.com[send an email]
+