Revert the test-pull-request workflow (#79)

.github/workflows/test-pull-request.yml

@@ -0,0 +1,85 @@
+---
+###########################
+###########################
+## Pull request testing ##
+###########################
+###########################
+name: Latest Pull Request
+
+# Documentation:
+# - Workflow: https://help.github.com/en/articles/workflow-syntax-for-github-actions
+# - SuperLinter: https://github.com/github/super-linter
+# - Link validation: https://github.com/remarkjs/remark-validate-links
+
+######################################################
+# Start the job on a pull request to the main branch #
+######################################################
+on: pull_request
+
+###############
+# Set the Job #
+###############
+jobs:
+  validate:
+    # Set the agent to run on
+    runs-on: ubuntu-latest
+
+    ############################################
+    # Grant status permission for MULTI_STATUS #
+    ############################################
+    permissions:
+      contents: read
+      packages: read
+      statuses: write
+
+    ##################
+    # Load all steps #
+    ##################
+    steps:
+      ##########################
+      # Checkout the code base #
+      ##########################
+      - name: Checkout Code
+        uses: actions/checkout@v4
+        with:
+          # Full git history is needed to get a proper list of changed files
+          # within `super-linter`
+          fetch-depth: 0
+      - run: cat ".github/super-linter.env" >> "$GITHUB_ENV"
+
+      ################################
+      # Run Linters against code base #
+      ################################
+      - name: Lint Code Base
+        #
+        # Use full version number to avoid cases when a next
+        # released version is buggy
+        # About slim image: https://github.com/github/super-linter#slim-image
+        uses: super-linter/super-linter/slim@v5.7.2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          DEFAULT_BRANCH: main
+          VALIDATE_ALL_CODEBASE: false
+          VALIDATE_GITHUB_ACTIONS: true
+
+      - name: Setup Node
+        uses: actions/setup-node@v3
+        with:
+          node-version-file: '.nvmrc'
+          cache: 'yarn'
+          cache-dependency-path: 'yarn.lock'
+
+      - name: Enable Corepack for Yarn
+        run: corepack enable
+
+      - name: Install Dependencies
+        run: yarn install
+        env:
+          YARN_ENABLE_IMMUTABLE_INSTALLS: false
+
+      - name: Check links
+        run: yarn test
+
+      - name: Build site
+        if: ${{ success() }}
+        run: yarn build

src/pages/guide/index.md

@@ -193,6 +193,10 @@ Please refer to the article [Writing testable code][] for more information on wh
 The `bin/magento` tool provides a common entry point to execute any of the tests, which can be useful for continuous integration.
 Please see the [System Administrators Guide on Running Tests][] for more information.
 
+<div>
+    <iframe src="https://developer.adobe.com/commerce/php/best-practices/admin/placement-and-design/#feature-extensions" frameborder="0" width="100%" height="100%" align="center" scrolling="no"></iframe>
+</div>
+
 ## Where to find the tests in the file system
 
 Each test type described above corresponds to a subdirectory in `<magento2 root dir>/dev/tests`, as shown here: