Merge branch 'develop' into doc/fix/stopthemissinglanguageshellerror

.github/workflows/deploy-develop.yml

@@ -42,6 +42,16 @@ jobs:
         run: |
           npm rebuild
 
+      - name: Checking Gatsby cache
+        id: gatsby-cache-build
+        uses: actions/cache@v3
+        with:
+          path: |
+            public/*
+            !public/pdfs
+            .cache
+          key: ${{ runner.os }}-gatsby-build-develop
+
       - uses: actions/setup-python@v4
         with:
           python-version: "3.x"

.github/workflows/deploy-draft.yml

@@ -56,9 +56,12 @@ jobs:
         uses: actions/cache@v3
         with:
           path: |
-            public
+            public/*
+            !public/pdfs
             .cache
           key: ${{ runner.os }}-gatsby-build-draft-${{ github.head_ref }}
+          restore-keys: |
+            ${{ runner.os }}-gatsby-build-develop
 
       - name: Fix mtimes
         run: npm run fix-mtimes

.husky/post-checkout

@@ -1,3 +1,3 @@
 #!/bin/sh
-command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting '.git/hooks/post-checkout'.\n"; exit 2; }
+command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-checkout' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
 git lfs post-checkout "$@"

.husky/post-commit

@@ -1,3 +1,3 @@
 #!/bin/sh
-command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting '.git/hooks/post-commit'.\n"; exit 2; }
+command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-commit' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
 git lfs post-commit "$@"

.husky/post-merge

@@ -1,3 +1,3 @@
 #!/bin/sh
-command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting '.git/hooks/post-merge'.\n"; exit 2; }
+command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-merge' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
 git lfs post-merge "$@"

.husky/pre-push

@@ -1,3 +1,3 @@
 #!/bin/sh
-command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting '.git/hooks/pre-push'.\n"; exit 2; }
+command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'pre-push' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
 git lfs pre-push "$@"

CODEOWNERS

@@ -0,0 +1,4 @@
+# First pass basic codeowners file
+
+product_docs/docs/pgd/ @djw-m
+product_docs/docs/epas/ @nidhibhammar

README.md

@@ -367,18 +367,18 @@ Content is indexed for search when the production site builds.
 
 To contribute content to this site submit as a pull request (PR). There are two options for this:
 
-Option 1: locally
+Option 1: Making changes locally
 
 1. [Clone](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) this repository.
 2. [Make a new branch.](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging)
 3. Add commits to branch and [push to GitHub](https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches).
 4. Create a new PR on GitHub.
 
-Option 2: on GitHub
+Option 2: Editing files on GitHub
 
 1. Edit a file on GitHub.
 2. Submit changes as a PR on a new branch.
 
 ### Style Guide for EDB contributors
 
-See [EDB documentation style guide](https://enterprisedb.atlassian.net/wiki/spaces/DCBC/pages/2387870239/Documentation+Style+Guide).
+See [EDB documentation style guide](https://www.enterprisedb.com/docs/community/contributing/styleguide/).

advocacy_docs/community/contributing/index.mdx

@@ -1,25 +1,27 @@
 ---
-title: We love feedback!
-navTitle: Feedback
+title: Contributing Feedback and More
+navTitle: Contributing
 description: Guidelines for offering feedback to EDB Docs.
 iconName: IdeaSharing
 ---
 
 All feedback is welcome:
 
-1. an idea for something new
-2. you feel there's something missing
-3. a mistake
+Is it a simple edit for a typo? Use the **Suggest Edits** button and you can make a change to the docs which we'll review before including in the next docs update.
 
-Github Issues is the fastest way to get that feedback in front of us.
+If, on the other hand you:
 
-[Open an issue on Github →](https://github.com/rocketinsights/edb_docs_advocacy/issues)
+1. have an idea for something new
+2. you feel there's something missing
+3. you can see a mistake thats more than a typo
 
----
+Then Github Issues is the fastest way to get that feedback in front of us.
 
-### Have code or content to contribute?
+[Open an issue on Github →](https://github.com/EnterpriseDB/docs/issues)
 
-The only things we love more than feedback are pull requests. Check out [the README on Github](https://github.com/EnterpriseDB/docs) to get started. 
+### Have code or content to contribute?
 
+The only things we love more than feedback are pull requests. 
 
+Check out [the README on Github](https://github.com/EnterpriseDB/docs) to get started. 
 

advocacy_docs/community/contributing/repo.mdx

@@ -88,4 +88,4 @@ You'll make edits and additions via your IDE (VS Code). We recommend using [Gith
 
 ## Further reading
 
-- [Format & Style](/community/contribute/style)
+- [Format & Style](/community/contributing/styleguide)