Allow empty Alt text, config management init, & automated config imports#187
Allow empty Alt text, config management init, & automated config imports#187Infi-Knight wants to merge 10 commits intomainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR establishes the infrastructure for Configuration Management and improves accessibility by allowing empty alt text for decorative images. It creates a synchronized configuration baseline from Production and automates the deployment workflow to eliminate manual intervention.
Changes:
- Automated deployment workflow now includes
drush config:importand cache rebuild - Accessibility improvement: decorative images can have empty alt text (alt="")
- Configuration Management baseline established with ~1000 auto-exported config files
- Added team documentation for safe config management workflows
Reviewed changes
Copilot reviewed 300 out of 1104 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| config/*.yml | Auto-exported baseline configuration from Production (can be ignored per PR description) |
| ci/deploy/staging/cleanup.sh | Added automated config import and cache rebuild |
| ci/deploy/production/cleanup.sh | Added automated config import and cache rebuild |
| ci/CONFIG_MANAGEMENT.md | New documentation for config management workflows |
|
moving back to draft, some content types seem to be missing from staging but are in prod. need to verify where the drift is coming from |
| 3. Commit the changed YAML files to git. | ||
| 4. Deploy to Staging/Production. | ||
| 5. **Deployment:** The deployment process (via GitHub Actions or `make deploy`) now **automatically** runs: | ||
| - `drush config:import -y` (Configuration import) |
There was a problem hiding this comment.
Is it possible that this process is configured to import configuration changes only into the staging/production databases, and not into the local database?
If that is true, we need a way to import `/config' pulled from the PR into the local Db
There was a problem hiding this comment.
most likely this was the reason, I have updated the local config path so it should not pick up the tracked config
PR Checklist
Fixes #123)Summary
This PR achieves three key infrastructure and accessibility goals:
Changes
sequenceDiagram participant GH as GitHub Actions participant Staging as Staging Server participant DB as Drupal DB Note over GH, DB: OLD WORKFLOW GH->>Staging: rsync code Note right of GH: 🛑 Deployment "Complete" Note right of Staging: Config NOT applied User->>Staging: SSH & run manual import Staging->>DB: Update Config & Schema Note over GH, DB: NEW WORKFLOW GH->>Staging: rsync code GH->>Staging: execute cleanup.sh rect rgb(200, 255, 200) Note right of Staging: ✅ Automatic Steps Staging->>DB: drush config:import -y Staging->>DB: drush cr endAccessibility Updates
field.field.media.image.field_media_imagefield.field.media.svg.field_media_svgChange: alt_field_required` set to false.
Documentation
Added
ci/CONFIG_MANAGEMENT.md: Guide for the team on how to make config changes using the UI/Drush and safe export/import procedures.4. Reviewer Guide
Files to Ignore: You can safely IGNORE the ~1000 files in config/. These are auto-generated exports representing the current state of Production. We are committing them to establish a "Clean Baseline" so future PRs only show specific diffs.
Please focus your review on:
ci/deploy/staging/cleanup.sh: Automation logic added.ci/deploy/production/cleanup.sh: Automation logic added.config/field.field.media.image.field_media_image.yml: Verified change to alt_field_required: false.ci/CONFIG_MANAGEMENT.md: New team documentation.Verification
This has been verified on Staging using the "Break-Fix" method:
Baseline: Manually reverted Staging to require alt text.
Test: Deployed this branch via make deploy.
Result: The deployment script automatically ran config:import, and the site updated to allow empty alt text without any manual SSH intervention.