Add coder-ddev project entry and remove Vortex recommended flag

[theodorosploumis]

Motivation

• Introduce a new coder-ddev project entry for DDEV-based Coder workspace templates and update the Vortex metadata to no longer be marked as recommended.

Description

• Add _data/projects/coder-ddev.yml containing metadata (name, year_created, source, homepage, docs, description, requirements, drupal_versions, operation_system, category, and similar).
• Remove the recommended: true flag from _data/projects/vortex.yml to change its recommendation status.

Testing

• No automated tests were run for these data-only YAML changes.

---

Codex Task

[qodo-code-review]

Review Summary by Qodo

Add coder-ddev project and update Vortex recommendation status

✨ Enhancement

Walkthroughs

Description

• Add new coder-ddev project entry with DDEV workspace templates
• Remove recommended flag from Vortex project metadata
• Update project recommendations in data files

Diagram

flowchart LR
  A["Projects Data"] --> B["Add coder-ddev.yml"]
  A --> C["Update vortex.yml"]
  B --> D["New DDEV Project Entry"]
  C --> E["Remove Recommended Flag"]

Loading

File Changes

1. _data/projects/coder-ddev.yml ✨ Enhancement +22/-0

Add new coder-ddev project metadata file

• New project file for Coder DDEV workspace templates
• Includes metadata: name, year_created, source, homepage, docs
• Specifies requirements (docker, ddev) and Drupal 11 support
• Categorized under cloud, development, docker, and workflow
• Marked as recommended with Linux OS support

_data/projects/coder-ddev.yml

---

2. _data/projects/vortex.yml ✨ Enhancement +0/-1

Remove recommended flag from Vortex project

• Remove recommended: true flag from Vortex project
• Maintains all other project metadata unchanged
• Changes recommendation status for Vortex template

_data/projects/vortex.yml

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 📐 Spec deviations (0)

1. Empty logo renders broken img 🐞 Bug ✓ Correctness

Description

_data/projects/coder-ddev.yml sets logo: with no value, which won’t satisfy the templates’ `logo
== null check and will render <img src=""/>` instead of the placeholder image.

Code

_data/projects/coder-ddev.yml[6]

+logo:

Evidence

The new project defines an empty logo value. The homepage tiles and project layout only use the
placeholder when logo == null; an empty value will go to the else branch and emit an <img> tag
with an empty src attribute, producing a broken image for this entry.

_data/projects/coder-ddev.yml[1-22]
index.html[15-35]
_layouts/project.html[6-20]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`_data/projects/coder-ddev.yml` defines `logo:` with no value. In Liquid templates, the placeholder image is only used when `logo == null`, so an empty value causes `<img src=""/>` to render (broken image).

### Issue Context
This affects both the homepage tile view and the project detail page.

### Fix Focus Areas
- Set `logo: null` or remove the `logo` key entirely, or provide a valid logo URL.
- (Optional hardening) Update the Liquid checks to treat empty strings as missing, e.g. `if project.logo == null or project.logo == ''`.

- _data/projects/coder-ddev.yml[6-6]
- index.html[22-24]
- _layouts/project.html[10-12]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[qodo-code-review]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: update-package

Failed stage: Commit and push changes [❌]

Failed test name: ""

Failure summary: The action failed due to a Bash syntax error while running the git commit -m command. - The commit message passed to -m spans multiple lines and includes unescaped characters/command substitution like $(cd mcp-package && node -e "console.log(Object.keys(JSON.parse(... with parentheses (. - This broke the generated shell script, leading to /home/runner/work/_temp/246cbee4-5d2f-469d-84a7-4b3be0e12270.sh: line 9: syntax error near unexpected token </code>(' and the step exiting with code 2. - Because the script failed at the commit step, git push never successfully ran.

Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 190: ##[group]Run git config --local user.email "action@github.com" 191: �[36;1mgit config --local user.email "action@github.com"�[0m 192: �[36;1mgit config --local user.name "GitHub Action"�[0m 193: �[36;1mgit add mcp-package/�[0m 194: �[36;1mgit commit -m "chore: Update MCP package with latest Drupal tools data�[0m 195: �[36;1m�[0m 196: �[36;1m- Rebuilt projects.json with $(cd mcp-package && node -e "console.log(Object.keys(JSON.parse(require('fs').readFileSync('dist/projects.json', 'utf8'))).length)" tools�[0m 197: �[36;1m- Updated package when _data/projects changed�[0m 198: �[36;1m�[0m 199: �[36;1m🤖 Generated with [Claude Code](https://claude.com/claude-code)�[0m 200: �[36;1m�[0m 201: �[36;1mCo-Authored-By: Claude <noreply@anthropic.com>"�[0m 202: �[36;1mgit push�[0m 203: shell: /usr/bin/bash -e {0} 204: ##[endgroup] 205: /home/runner/work/_temp/246cbee4-5d2f-469d-84a7-4b3be0e12270.sh: line 9: syntax error near unexpected token `(' 206: ##[error]Process completed with exit code 2. 207: Post job cleanup.