Release new EDS platform (#170)

* updates with eds migration

* Update scripts

* Update Hero to HeroSimple

* testing on imports

* try import

* test with less content

* including everything except the table

* testing

* testing

* testing

* removing br

* update after remove br

* fixing guide/index.md

* update runtime-webhooks/index.md

* update amazon-eventbridge/index.md

* update runtime-webhooks/index.md

* Fix local Links with link checker

* fix links

* update error files

* update appbuilder/index

* update appbuilds

* update aoobuilder

* update

* update

* update

* update appbuilder/index

* update

* update

* update appbuilder from eds-migration

* update cli index.md

* update links

* update horizontal line

* update marketo-lead-activity-data-stream-setup

* update

* update

* update registration-api

* update sdk-signarture-verfication

* update marketo-lead-activity-data-stream-setup

* remove syntax

* remove syntax

* update check-links for headings.

* remove the old link checker

* update on the api document.

* update api.md

* update api to full page

* update checklinks

* update links for retry-doc

* update img link

* update retry doc

* update

* update link

* update common component

* update

* update link

* update

* update marketo links

* update link

* update link in common

* update link to relative page

* update relative paths in embed components

* update

* checking

* checking

* update skyline-install

* update files

* update outdated links

* update asset-events-configuration

* update scripts

* update redirects

Author: louisachu

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,12 @@
+---
+blank_issues_enabled: false
+contact_links:
+  - name: Help Center
+    url: https://helpx.adobe.com/support.html
+    about: Find help with issues unrelated to documentation here.
+  - name: Community resources
+    url: https://developer.adobe.com/open
+    about: Find more resources here.
+  - name: Adobe Developer Support
+    url: https://developer.adobe.com/developer-support
+    about: Ask and answer questions.

.github/ISSUE_TEMPLATE/incorrect_topic.yaml

@@ -0,0 +1,34 @@
+name: Incorrect or unclear topic
+description: "Unclear or incorrect documentation: ambiguous guidelines, wrong or obsolete examples, typos, etc."
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to report this issue!
+        This request should only relate to the content of the developer.adobe.com website.
+        Requests that do not comply with our Code of Conduct or do not contain enough information may be closed at the maintainers' discretion.
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the documentation you are requesting.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: input
+    attributes:
+      label: Which topic?
+      description: A link to the topic that needs clarification or correction
+      placeholder: "Example: https://developer.adobe.com/commerce/webapi/rest/use-rest/search-endpoint/"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What's wrong with the content?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What changes do you propose?
+  - type: textarea
+    attributes:
+      label: Anything else that can help to cover this?

.github/ISSUE_TEMPLATE/missing_content.yaml

@@ -0,0 +1,27 @@
+name: Missing content
+description: Undocumented feature, service, command, API, UI component, procedure, etc.
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to report this issue!
+        This request should only relate to the content of the developer.adobe.com website.
+        Requests that do not comply with our Code of Conduct or do not contain enough information may be closed at the maintainers' discretion.
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the documentation you are requesting.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: textarea
+    attributes:
+      label: What's missing?
+      placeholder: |
+        - In the <guide name> or <page link> ...
+        - Missing explanation of how ... works.
+        - Missing steps or guidelines for ....
+        - Missing code samples to demonstrate ....
+        - Something else ...
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/site_bug.yaml

@@ -0,0 +1,58 @@
+name: Site bug
+description: Something isn't working on developer.adobe.com or when building the website locally.
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to report this issue!
+        This bug report should only relate to the developer.adobe.com website itself or non-content issues such as rendering, 404 pages, or other unexpected behavior.
+        Issues that do not comply with our Code of Conduct or do not contain enough information may be closed at the maintainers' discretion.
+        SECURITY DISCLOSURE: If this is a security disclosure please follow the guidelines in CONTRIBUTING.md. This helps keep folks from accidentally releasing vulnerabilities before the maintainers get a chance to fix the issue.
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: |
+        Tell us what you expected to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Actual behavior
+      description: |
+        Tell us what happened. Include error messages and issues.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: |
+        Provide a set of clear steps to reproduce this bug.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Environment
+      description: |
+        Describe your environment such as platform, browser, and versions.
+        Provide all the details that will help us to reproduce the bug.
+      value: |
+        - Browser:
+        - OS:
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Sample code
+      description: Sample Code that illustrates the problem
+  - type: textarea
+    attributes:
+      label: Logs
+      description: Logs taken while reproducing problem

.github/ISSUE_TEMPLATE/site_feature.yaml

@@ -0,0 +1,34 @@
+name: Site feature request
+description: Propose a new functionality or an improvement of the developer.adobe.com website or of the local development tools.
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to report this issue!
+        This feature request should only relate to the developer.adobe.com website itself and its behavior.
+        Requests that do not comply with our Code of Conduct or do not contain enough information may be closed at the maintainers' discretion.
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the feature you are requesting.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: textarea
+    attributes:
+      label: What feature should be added?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What is the expected behavior?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: How will this feature improve the user experience?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What would a solution for this issue look like?

.github/scripts/deploy.js

@@ -0,0 +1,64 @@
+const { exec } = require('child_process');
+
+module.exports = async ({ core, changes, deletions, operation, siteEnv, branch, pathPrefix }) => {
+  let httpMethod, edsSiteEnv, codeRepoBranch, args;
+  if (operation.includes('cache') || operation.includes('preview') || operation.includes('live')) {
+    httpMethod = 'POST';
+  } else {
+    console.error('Unknown operation method');
+  }
+
+  if (siteEnv.includes('stage')) {
+    edsSiteEnv = "adp-devsite-stage";
+    codeRepoBranch = "stage";
+  } else if (siteEnv.includes('prod')) {
+    edsSiteEnv = "adp-devsite";
+    codeRepoBranch = "main";
+  } else {
+    console.error('Unknown env to deploy to');
+  }
+
+  // hacky way to do operations on our adp-devsite-stage env
+  if ((siteEnv.includes('stage') && operation.includes('preview')) || (siteEnv.includes('stage') && operation.includes('cache'))) {
+    args = `--header "x-content-source-authorization: ${branch}"`;
+  } else {
+    args = '';
+  }
+
+  changes.forEach((file) => {
+    // have to pop src/pages from the file path
+    file = file.replace('src/pages/', '');
+
+    const theFilePath = `${pathPrefix}/${file}`;
+    const url = `https://admin.hlx.page/${operation}/adobedocs/${edsSiteEnv}/${codeRepoBranch}${theFilePath}`;
+    const cmd = `curl -X${httpMethod} -vi ${args} ${url}`;
+
+    exec(cmd, (error, execOut, execErr) => {
+      if (error) {
+        console.error(`::group:: Error ${theFilePath} \n${execErr} \n::endgroup::`)
+        return;
+      }
+
+      console.log(`::group:: Running ${operation} on ${theFilePath} \nThe command: ${cmd} \n${execOut} \n::endgroup::`);
+    });
+  });
+
+  deletions.forEach((file) => {
+    // have to pop src/pages from the file path
+    file = file.replace('src/pages/', '');
+
+    const theFilePath = `${pathPrefix}/${file}`;
+    const deleteUrl = `https://admin.hlx.page/${operation}/adobedocs/${edsSiteEnv}/${codeRepoBranch}${theFilePath}`;
+    const deleteCmd = `curl -XDELETE -vi ${args} ${deleteUrl}`;
+
+
+    exec(deleteCmd, (deleteError, deleteExecOut, deleteExecErr) => {
+      if (deleteError) {
+        console.error(`::group:: Deleting error ${theFilePath} \n${deleteExecErr} \n::endgroup::`)
+        return;
+      }
+
+      console.log(`::group:: Deleting ${operation} on ${theFilePath} \nThe command: ${deleteCmd} \n${deleteExecOut} \n::endgroup::`);
+    });
+  });
+}

.github/scripts/get-path-prefix.js

@@ -1,49 +1,127 @@
-// This script retrieves the pathPrefix from the gatsby-config.js file.
+// This script retrieves the pathPrefix from the config.md file and validates it against the pathPrefix from devsite-paths.json.
 // It serves as an example for how to set up external javascript functions
 // outside workflow .yml files when they get too big or complex to keep them inline.
 
 // Documentation for the actions/github-script:
 // https://github.com/actions/github-script#run-a-separate-file
 
-module.exports = async ({ core }) => {
-  const { pathPrefix } = await require('../../gatsby-config.js');
+const CONFIG_PATH = `./src/pages/config.md`;
+const DEVSITE_STAGE_HOST = `https://main--adp-devsite-stage--adobedocs.aem.page`;
+const DEVSITE_PROD_HOST = `https://main--adp-devsite--adobedocs.aem.live`;
+const DEVSITE_PATHNAME = `/franklin_assets/devsitepaths.json`;
 
-  if (!pathPrefix) {
-    core.setFailed(
-      `The pathPrefix in the site's gatsby-config.js file is missing.
+module.exports = async ({ core, isStage, isProd }) => {
+    const fs = await require('fs');
+    if (!fs.existsSync(CONFIG_PATH)) {
+      core.setFailed(
+        `The site's config.md file is missing.
+  
+        To fix this, either create one in ./src/pages, or auto-generate one from the site's gatsby-config.md file by building navigation file.`
+      );
+      return;
+    }
 
-      To fix this, open your gatsby-config.js file, and add it to the config object:
+    const string = fs.readFileSync(CONFIG_PATH).toString() ?? "";
+    const lines = string.split('\n');
 
-      module.exports = {
-        pathPrefix: "/commerce/frontend-core/",
-        ...
-      }`
-    );
-  } else if (pathPrefix === '/') {
-    core.setFailed(
-      `The pathPrefix in the site's gatsby-config.js file is set to "/". This is not allowed.
+    // find the pathPrefix key
+    const keyIndex = lines.findIndex(line => line.includes("pathPrefix:"));
 
-      To fix this, change the pathPrefix to include a name that starts and ends with "/":
+    if (keyIndex < 0) {
+      core.setFailed(
+        `The pathPrefix in the site's config.md file is missing.
 
-      pathPrefix: "/commerce/frontend - core/"
+        To fix this, open your config.md file, and add it to the config object:
+
+        - pathPrefix:
+        ...`
+      );
+      return;
+    }
 
-      This name identifies the site within the developer.adobe.com domain:
-      https://developer.adobe.com/document-services/<PATH_TO_FILES>.
-      `
-    );
-  } else {
-    if (!pathPrefix.startsWith('/') || !pathPrefix.endsWith('/')) {
+    // find the pathPrefix value
+    const line = lines.slice(keyIndex + 1)?.find(line => line.trimStart().startsWith("-")) ?? "";
+  
+    // remove whitespace at start, remove dash (i.e. first non-whitespace character), and remove whitespace at start and end
+    const pathPrefix = line.trimStart().substring(1).trim();
+
+    if (!pathPrefix) {
       core.setFailed(
-        `The pathPrefix in the site's gatsby-config.js file does not start or end with "/".
+        `The pathPrefix in the site's config.md file is missing.
 
-        To fix this, change the pathPrefix to include a name that starts and ends with "/".
-        For example: "/document-services/" or "/commerce/cloud-tools/".
+        To fix this, open your config.md file, and add it to the config object:
 
-        This is required by convention because of the way we construct site URLs.
-        For example: https://developer.adobe.com + /document-services/ + path/to/files/.
-        `
+        - pathPrefix:
+            - /commerce/frontend-core/
+        ...`
       );
+    } else if (pathPrefix === '/') {
+        core.setFailed(
+            `The pathPrefix in the site's config.md file is set to "/". This is not allowed.
+
+            To fix this, change the pathPrefix to include a name that starts and ends with "/".
+
+            For example: "/commerce/frontend - core/"
+
+            This name identifies the site within the developer.adobe.com domain:
+            https://developer.adobe.com/document-services/<PATH_TO_FILES>.
+            `
+        );
+    } else if (!pathPrefix.startsWith('/') || !pathPrefix.endsWith('/')) {
+        core.setFailed(
+            `The pathPrefix in the site's config.md file does not start or end with "/".
+
+            pathPrefix: "${pathPrefix}"
+
+            To fix this, change the pathPrefix to include a name that starts and ends with "/".
+            For example: "/document-services/" or "/commerce/cloud-tools/".
+
+            This is required by convention because of the way we construct site URLs.
+            For example: https://developer.adobe.com + /document-services/ + path/to/files/.
+            `
+        );
+    }
+
+    // TODO: devsitepaths pathPrefix currently do not have a trailing slash
+    // will need to refactor all path prefix listings to include them
+    // but for now checked with a popped trailing slash
+
+    const poppedPathPrefix = pathPrefix.substring(0, pathPrefix.length-1);
+    // must convert values to boolean from string
+    if(isStage.toLowerCase() === 'true') {
+      const stageEntries = await (await fetch(`${DEVSITE_STAGE_HOST}${DEVSITE_PATHNAME}`)).json();
+      const stageEntry = stageEntries?.data?.find(entry => entry.pathPrefix === poppedPathPrefix);
+
+      if(!stageEntry) {
+        core.setFailed(
+          `The pathPrefix in the site's config.md file was not found in the STAGE gdrive's devsitepaths.json.
+
+          pathPrefix from config.md: "${pathPrefix}"
+          devsitepath.json location: "${DEVSITE_STAGE_HOST}${DEVSITE_PATHNAME}"
+
+          To fix this, make sure the pathPrefix listed in the config.md is in the devsitepath.json location.
+          `
+        );
+      }
     }
-  }
-  core.setOutput('path_prefix', pathPrefix);
-};
+
+    // must convert values to boolean from string
+    if(isProd.toLowerCase() === 'true') {
+      const prodEntries = await (await fetch(`${DEVSITE_PROD_HOST}${DEVSITE_PATHNAME}`)).json();
+      const prodEntry = prodEntries?.data?.find(entry => entry.pathPrefix === poppedPathPrefix);
+
+      if(!prodEntry) {
+        core.setFailed(
+          `The pathPrefix in the site's config.md file was not found in the PROD gdrive's devsitepaths.json.
+
+          pathPrefix from config.md: "${pathPrefix}"
+          devsitepath.json location: "${DEVSITE_PROD_HOST}${DEVSITE_PATHNAME}"
+
+          To fix this, make sure the pathPrefix listed in the config.md is in the devsitepath.json location.
+          `
+        );
+      }
+    }
+
+    core.setOutput('path_prefix', poppedPathPrefix);
+}