Randy Fay Outlines How to Contribute to ddev.com in Latest Training

Staff Reporter

Randy Fay has published a contributor training session for the DDEV community, demonstrating the process for editing and adding content to the DDEV website.

The session explains how contributors can quickly fix content errors by clicking the pencil icon on blog posts, which opens GitHub in edit mode and allows pull requests without a local checkout. Community blog submissions are encouraged, beginning with an issue to propose the topic and followed by adapting an existing post in src/content/blog.

To be listed as an author, contributors must create a file in src/content/authors/ with name details and an optional avatar. Local previews are made possible through ddev start, and every pull request triggers automated checks using Prettier and Textlint to ensure consistency and formatting. A Cloudflare Pages preview is also generated for each submission.

The training draws from both video and presentation slides and was largely compiled by Claude Code. The full video is available on YouTube, and contributors are encouraged to refer to the DDEV Website For Contributors post for detailed guidance.

Reference: Contributor Training: Contributing to ddev.com by Randy Fay (rfay), DDEV (10 October 2025)

DDEV

Training

GitHub

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.