Upgrade to latest theme version and enable local search

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Adobe Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language.
+* Being respectful of differing viewpoints and experiences.
+* Gracefully accepting constructive criticism.
+* Focusing on what is best for the community.
+* Showing empathy towards other community members.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances.
+* Trolling, insulting/derogatory comments, and personal or political attacks.
+* Public or private harassment.
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission.
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting.
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [https://contributor-covenant.org/version/1/4][version].
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -6,7 +6,7 @@ The following are a set of guidelines to follow when contributing to this projec
 
 ## Code Of Conduct
 
-This project adheres to the Adobe [code of conduct](../CODE_OF_CONDUCT.md). By participating,
+This project adheres to the Adobe [code of conduct](CODE_OF_CONDUCT.md). By participating,
 you are expected to uphold this code. Please report unacceptable behavior to
 [[email protected]](mailto:[email protected]).
 

.github/linters/.markdown-lint.yml

@@ -0,0 +1,51 @@
+---
+###########################
+###########################
+## Markdown Linter rules ##
+###########################
+###########################
+
+# Linter rules doc:
+# - https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md
+#
+# Note:
+# To comment out a single error:
+#   <!-- markdownlint-disable -->
+#   any violations you want
+#   <!-- markdownlint-restore -->
+#
+
+# Default state for all rules
+default: false
+
+#################
+# Rules by tags #
+#################
+blanks-around-fences: true    # Fenced code blocks should be surrounded by blank lines
+blanks-around-headings: true  # Headings should be surrounded by blank lines
+blanks-around-lists: true     # Lists should be surrounded by blank lines
+code-block-style:
+  style: "fenced"
+code-fence-style:
+  style: "backtick"
+emphasis-style:
+  style: "consistent"
+fenced-code-language: true    # Fenced code blocks should have a language specified
+heading-start-left: true      # Headings must start at the beginning of the line
+heading-style:
+  style: "atx"
+hr-style: true                # Horizontal rule style
+list-indent: true             # Inconsistent indentation for list items at the same level
+no-empty-links: true
+no-missing-space-atx: true    # No space after hash on atx style heading
+no-multiple-blanks: true      # Multiple consecutive blank lines
+no-reversed-links: true
+no-space-in-code: true
+no-space-in-emphasis: true
+no-space-in-links: true
+no-trailing-spaces: true
+single-trailing-newline: true   # Files should end with a single newline character
+strong-style:
+  style: "consistent"
+ul-style:
+  style: "consistent"

.github/linters/.yaml-lint.yml

@@ -0,0 +1,59 @@
+---
+###########################################
+# These are the rules used for            #
+# linting all the yaml files in the stack #
+# NOTE:                                   #
+# You can disable line with:              #
+# # yamllint disable-line                 #
+###########################################
+rules:
+  braces:
+    level: warning
+    min-spaces-inside: 0
+    max-spaces-inside: 0
+    min-spaces-inside-empty: 1
+    max-spaces-inside-empty: 5
+  brackets:
+    level: warning
+    min-spaces-inside: 0
+    max-spaces-inside: 0
+    min-spaces-inside-empty: 1
+    max-spaces-inside-empty: 5
+  colons:
+    level: warning
+    max-spaces-before: 0
+    max-spaces-after: 1
+  commas:
+    level: warning
+    max-spaces-before: 0
+    min-spaces-after: 1
+    max-spaces-after: 1
+  comments: disable
+  comments-indentation: disable
+  document-end: disable
+  document-start:
+    level: warning
+    present: true
+  empty-lines:
+    level: warning
+    max: 2
+    max-start: 0
+    max-end: 0
+  hyphens:
+    level: warning
+    max-spaces-after: 1
+  indentation:
+    level: warning
+    spaces: consistent
+    indent-sequences: true
+    check-multi-line-strings: false
+  key-duplicates: enable
+  line-length:
+    level: warning
+    max: 200
+    allow-non-breakable-words: true
+    allow-non-breakable-inline-mappings: true
+  new-line-at-end-of-file: disable
+  new-lines:
+    type: unix
+  trailing-spaces: disable

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

@@ -0,0 +1,49 @@
+// This script retrieves the pathPrefix from the gatsby-config.js file.
+// 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');
+
+  if (!pathPrefix) {
+    core.setFailed(
+      `The pathPrefix in the site's gatsby-config.js file is missing.
+
+      To fix this, open your gatsby-config.js file, and add it to the config object:
+
+      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.
+
+      To fix this, change the pathPrefix to include a name that starts and ends with "/":
+
+      pathPrefix: "/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 gatsby-config.js file does not start or end with "/".
+
+        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/.
+        `
+      );
+    }
+  }
+  core.setOutput('path_prefix', pathPrefix);
+};