Release

.ci/github/create_release_pull_request

@@ -0,0 +1,107 @@
+#!/bin/bash
+
+set -eo pipefail
+
+# If we aren't updating an existing pull request, create one to merge develop into master.
+if [[ -z "$PR_NUMBER" ]]; then
+  pull_request_response=$(curl -s -H "Accept: application/vnd.github+json" \
+    -H "Authorization: token $ACCESS_TOKEN" \
+    -X POST -d '{"title": "Release", "head": "develop", "base": "master"}' \
+    "https://api.github.com/repos/$REPO/pulls")
+
+  message=$(echo "$pull_request_response" | jq -r 'if has("errors") then .errors[].message else null end')
+
+  # Check if the pull request creation was successful.
+  if [[ -n "$message" ]]; then
+    echo "Failed to create pull request."
+    echo "Error: $message"
+    exit 1
+  else
+    pr_url=$(echo "$pull_request_response" | jq -r '.html_url')
+  fi
+
+  # Extract the pull request number from the response.
+  PR_NUMBER=$(echo "$pull_request_response" | jq -r '.number')
+
+# If there is an existing PR number, get the PR.
+else
+  pull_request_response=$(curl --silent -H "Authorization: token $ACCESS_TOKEN" \
+    "https://api.github.com/repos/$REPO/pulls/$PR_NUMBER")
+
+  pr_url=$(echo "$pull_request_response" | jq -r '.html_url')
+fi
+
+# Page through the /pulls/#/commits endpoint.
+page=1
+per_page=100
+
+while true; do
+  # Get the list of commits from the pull request and extract commit SHAs.
+  commits_response=$(curl --silent -H "Authorization: token $ACCESS_TOKEN" \
+    "https://api.github.com/repos/$REPO/pulls/$PR_NUMBER/commits?per_page=$per_page&page=$page")
+
+  current_commit_shas=$(echo "$commits_response" | jq -r '.[].sha')
+
+  # Append current commit SHAs to the overall list.
+  commit_shas+="$current_commit_shas"
+
+  # Check if there are more pages, otherwise finish.
+  if [[ $(echo "$commits_response" | jq -r '. | length') -lt "$per_page" ]]; then
+    break
+  fi
+
+  # Increment page number for the next API call.
+  ((page++))
+done
+
+# Create list of unique pull requests based on commit SHAs, and another for changes without PRs.
+pull_requests=()
+changes_without_pr=()
+
+for sha in $commit_shas; do
+  single_pr_url=$(curl -s -H "Authorization: token $ACCESS_TOKEN" \
+    "https://api.github.com/repos/$REPO/commits/$sha/pulls" \
+    | jq -r 'if type == "object" and has("message") and length > 0 then null else .[].html_url // empty end')
+
+  if [[ -n "$single_pr_url" && "$single_pr_url" != "null" ]]; then
+    pull_requests+=("$single_pr_url")
+  elif [[ "$single_pr_url" == "null" ]]; then
+    :
+  else
+    changes_without_pr+=("$sha")
+  fi
+done
+
+# Dedupe pull request URLs.
+pull_requests=($(printf '%s\n' "${pull_requests[@]}" | sort -u))
+
+# Begin outputting description if there are PRs.
+if [[ -n "${pull_requests[*]}" ]]; then
+  description+="## Pull requests\n"
+
+  # Create pull request description with list of pull requests as a markdown list.
+  for pr in "${pull_requests[@]}"; do
+      description+="- $pr\n"
+  done
+
+fi
+
+# Output changes that are not in a pull request.
+if [[ -n "${changes_without_pr[*]}" ]]; then
+  description+="\n## Changes without a pull request:\n"
+
+  for sha in "${changes_without_pr[@]}"; do
+      description+="- $sha\n"
+  done
+fi
+
+# Update pull request with new description.
+update_pull_request=$(curl -s -L \
+  -H "Accept: application/vnd.github+json" \
+  -H "Authorization: token $ACCESS_TOKEN" \
+  -X PATCH -d "{\"body\": \"$description\"}" \
+  "https://api.github.com/repos/$REPO/pulls/$PR_NUMBER")
+
+if [[ -n "$pull_request_response" || -n "$update_pull_request" ]]; then
+  echo "Pull request created or updated: $pr_url"
+fi

.github/dependabot.yml

@@ -0,0 +1,35 @@
+version: 2
+updates:
+  # Update root composer.json and drupal/core only.
+  - package-ecosystem: "composer"
+    open-pull-requests-limit: 5
+    target-branch: "develop"
+    schedule:
+      interval: "monthly"
+    directory: "/"
+    versioning-strategy: increase
+    commit-message:
+      prefix: "chore"
+      include: "scope"
+    allow:
+      - dependency-name: "drupal/core-*"
+    groups:
+      drupal-core:
+        patterns:
+          - "drupal/core-*"
+
+  # Update yalesites_profile composer.json.
+  - package-ecosystem: "composer"
+    open-pull-requests-limit: 5
+    target-branch: "develop"
+    schedule:
+      interval: "monthly"
+    directory: "/web/profiles/custom/yalesites_profile"
+    versioning-strategy: increase
+    commit-message:
+      prefix: "chore"
+      include: "scope"
+    groups:
+      yalesites-profile:
+        patterns:
+          - "*"

.github/workflows/build_deploy_and_test.yml

@@ -115,6 +115,12 @@ jobs:
           if [ -n "$contrib_check" ]; then
             echo "::error::$contrib_check found in /composer.json and should be moved to /web/profiles/custom/yalesites_profile/composer.json" && exit 1
           fi
+      - name: Check for unpinned dependencies
+        run: |
+          unpinned_dependencies=$(jq -r '.require | to_entries | map(select(.value | test("\\^|\\~|\\>|\\<")) | "\(.key): \(.value)") | join(", ")' ./web/profiles/custom/yalesites_profile/composer.json)
+          if [ -n "$unpinned_dependencies" ]; then
+            echo "::error::$unpinned_dependencies found in /web/profiles/custom/yalesites_profile/composer.json. Please switch to pinned versions." && exit 1
+          fi
 
       - name: run static tests
         run: |

.github/workflows/release.yml

@@ -4,6 +4,7 @@ on:
     branches: master
 env:
   GH_TOKEN: ${{ secrets.YALESITES_BUILD_TOKEN }}
+  YALESITES_BUILD_TOKEN: ${{ secrets.YALESITES_BUILD_TOKEN }}
 jobs:
   build:
     runs-on: ubuntu-latest
@@ -15,8 +16,6 @@ jobs:
         uses: actions/setup-node@v3
 
       - name: Install
-        env:
-          GH_TOKEN: ${{ secrets.GH_TOKEN }}
         run: npm install
 
       - name: Release

.github/workflows/release_pr.yml

@@ -0,0 +1,19 @@
+name: Create release pull request
+on:
+  pull_request:
+    branches:
+      - master
+  workflow_dispatch:
+jobs:
+  create_pull_request:
+    runs-on: ubuntu-latest
+    env:
+      ACCESS_TOKEN: ${{ secrets.YALESITES_BUILD_TOKEN }}
+      REPO: ${{ github.repository }}
+      PR_NUMBER: ${{ github.event.number }}
+    steps:
+    - name: Checkout
+      uses: actions/checkout@v4
+
+    - name: Create pull request
+      run: ./.ci/github/create_release_pull_request

.gitignore

@@ -22,7 +22,6 @@
 # Ignore SimpleTest multi-site environment.
 /web/sites/simpletest
 
-
 # Ignore custom modules managed by Composer.
 #
 # When a development team creates one or more custom modules that
@@ -113,6 +112,7 @@ package-lock.json
 
 # Local files
 .DS_Store
+.zip
 
 # Database references
 reference
@@ -130,3 +130,6 @@ web/profiles/custom/yalesites_profile/vendor/
 /atomic
 /component-library-twig
 /tokens
+
+# Secrets for local use
+secrets.json

.lando.local.example.yml

@@ -42,5 +42,6 @@ services:
     overrides:
       environment:
         COMPOSER_PROCESS_TIMEOUT: 1800
+        CUSTOMER_SECRETS_FAKE_FILE: /app/secrets.json
     # This is needed to expose the reverse proxy to the xdebug port (9003)
     xdebug: true

README.md

@@ -1,4 +1,4 @@
-# YaleSites Project
+# YaleSites Project.
 
 The YaleSites platform empowers the Yale community to create digital experiences for the web in applications that are secure, cost-effective, accessible, and sustainable. This project repository contains the tooling, configuration, and scaffolding required to create sites on the platform. This project includes:
 

composer.json

@@ -10,6 +10,18 @@
     "drupal": {
       "type": "composer",
       "url": "https://packages.drupal.org/8"
+    },
+    "ckeditor5-anchor-drupal": {
+      "type": "package",
+      "package": {
+        "name": "northernco/ckeditor5-anchor-drupal",
+        "version": "0.4.0",
+        "type": "drupal-library",
+        "dist": {
+          "url": "https://registry.npmjs.org/@northernco/ckeditor5-anchor-drupal/-/ckeditor5-anchor-drupal-0.4.0.tgz",
+          "type": "tar"
+        }
+      }
     }
   },
   "require": {

docs/development.md

@@ -91,3 +91,25 @@ lando drush migrate-rollback --group ys_starterkit
 # Update partial configuration if altering the migration configuration.
 lando drush cim --partial --source=/app/web/profiles/custom/yalesites_profile/modules/custom/ys_starterkit/config/install -y
 ```
+
+## Data model best practices
+
+A well-structured data model ensures efficiency, maintainability, and scalability within the YaleSites platform. Below are some guiding principles adopted by the platform maintainers:
+
+- **Documentation Maintenance**: Keep the data model documentation up to date. This Teams document includes entity definitions, text formats, display mode definitions, and other content settings. Whenever there's a change to a content type, block, paragraph, taxonomy, or any other entity, make it a priority to update this central documentation source. Maintaining accurate documentation is crucial for team collaboration and project continuity.
+- **Normalize Data**: Follow established principles of database normalization to minimize data redundancy and enhance data integrity. Leverage reference fields and relationships to establish connections between related content instead of duplicating data. This approach ensures that the data remains consistent and predictable.
+- **Reuse Fields**: Reduce the proliferation of field definitions by reusing fields across multiple content bundles, as long as they serve a similar business purpose. For instance, if several content types (e.g., pull quote, video description, banner intro) require a 'field_text' storage, consider reusing this field definition to maintain consistency and simplify content management.
+- **Avoid Single-Purpose Fields or Entities**: When adding fields or entities, strive to make them versatile enough to fulfill multiple purposes across YaleSites. For example, while a dedicated 'Speaker' field might seem useful for an event content type, evaluate whether this feature could be addressed using a content-spotlight block. Add new fields only when they contribute to sorting, filtering, or theming content in specific ways.
+- **Build with Blocks**: Embrace the power of the layout builder by utilizing blocks to define new components. YaleSites relies on blocks for editorial controls and mapping content to the component library. This includes both custom blocks (content entities) and programmatically defined blocks (plugins).
+- **Use Paragraphs for Nested Content**: Paragraphs remain a valuable tool, particularly when dealing with components that contain an indeterminate number of children, such as accordion items, tab items, or gallery items. The Paragraphs module provides intuitive widgets that offer an effective editorial interface for managing reference content within these complex components.
+
+## Adding a 'dial' for theming a component
+
+This project features custom fields for block theming. For example, the divider block includes settings for position, width, and animation style. In contrast to traditional Drupal projects using predefined list-field options in the configuration file, we've chosen a distinct approach. Our approach prioritizes the ability to add, remove, and dynamically adjust these options in future YaleSites themes and platform iterations, ensuring enduring flexibility. This system accommodates unique values for each field instance and supports changes over time, avoiding database integrity concerns. To add a dial:
+
+1. Begin by adding the desired style field to the custom block using the standard field UI. Whenever feasible, utilize an existing field like field_style_position, field_style_width, or field_style_variation.
+2. Configure the display of this field using the Field UI. Ensure that the style field is presented without a label and employs the 'key' formatter.
+3. Export the site configuration to generate all the associated field YAML files.
+4. In the event that this is a newly created field, update the field storage configuration file. Specify the callback function for values using `allowed_values_function: ys_themes_allowed_values_function`.
+5. Proceed to update the key-value pairs within `ys_themes.component_overrides.yml`. Remember to make these updates in two locations: the config/sync directory and the module/install directory.
+6. With these adjustments in place, you can now connect these values to components within the theme templates, achieving the desired styling and functionality.

docs/export-starterkit-content.md

@@ -0,0 +1,47 @@
+# Exporting starterkit content
+
+## Purpose
+
+There are certain YaleSite sites whose purpose is to provide a starting set of
+pages for new YaleSites to use. This is a way to export the content of those
+sites for import into a new site.  This document will focus on the yalesites
+starterkit site. (ys-starterkit)
+
+## What does it do?
+
+This will attempt to execute an export of the pantheon site using the terminus
+command, then SFTP to it to retrieve the zip file, and attempt to unzip it into
+a git repository to make a new commit.
+
+New commits will look like the following:
+
+`Content update: <date>`
+
+## Prerequisites
+
+1. The following installed:
+    1. Terminus
+    2. Sftp
+    3. Git
+    4. tr (most linux/bsd/unix based systems have this)
+1. [Terminus with auth tokens already provided](https://github.com/yalesites-org/yalesites-project/blob/develop/docs/setup.md#terminus)
+
+## Usage
+
+1. Clone this repository.
+1. Clone the [yalesites-starterkit](https://github.com/yalesites-org/yalesites-starterkit) repository at a separate location.
+1. In this local repository, you'll run the following:
+
+  ```sh
+  SITE_MACHINE_NAME=<pantheon site name> \
+  ./scripts/local/starterkit/create-export \
+  <location of yalesites-starterkit>/starterkit
+  ```
+
+4. SITE_MACHINE_NAME is the name of the Pantheon site you want to export from.
+   (i.e. ys-starterkit.dev)
+
+## Where can I get this information?
+
+* PANTHEON_NAME: This is the name of the site as it appears in the Pantheon
+  dashboard.

package.json

@@ -6,6 +6,7 @@
     "build-with-install": "./scripts/local/build-with-install.sh",
     "build-with-assets": "./scripts/local/build-with-assets.sh",
     "confex": "./scripts/local/confex.sh",
+    "content-import": "./scripts/shared/content-import.sh",
     "confim": "./scripts/local/confim.sh",
     "db:get": "./scripts/local/db-get.sh",
     "files:get": "./scripts/local/files-get.sh",
@@ -61,7 +62,7 @@
               "files": [
                 "web/profiles/custom/yalesites_profile/yalesites_profile.info.yml"
               ],
-              "from": "version: .*",
+              "from": "#version:",
               "to": "version: ${nextRelease.version}",
               "results": [
                 {
@@ -76,14 +77,6 @@
           ]
         }
       ],
-      [
-        "@semantic-release/git",
-        {
-          "assets": [
-            "web/profiles/custom/yalesites_profile/yalesites_profile.info.yml"
-          ]
-        }
-      ],
       "@semantic-release/release-notes-generator",
       "@semantic-release/github"
     ]

scripts/local/build-with-install.sh

@@ -1,6 +1,7 @@
 #!/bin/bash
 
+export YALESITES_IS_LOCAL=1
 lando drush si yalesites_profile -y
 lando drush cr
-lando drush migrate:import --group=ys_starterkit
+npm run content-import
 npm run build