Erdfisch Expands nerdfisch DevBits into Public Drupal Code Archive

Small fixes, written in the middle of a project and reused weeks later, often carry more value than a polished tutorial. erdfisch has expanded its internal DevBits system into a publicly accessible archive of reusable code snippets, documenting working solutions drawn directly from real Drupal project work. The collection allows developers to retrieve working implementations directly from a growing archive of real project decisions.

The initiative addresses a recurring inefficiency in development work: solutions are often rediscovered rather than reused. DevBits attempts to reduce that repetition by preserving working implementations in their original form, without expanding them into tutorials or long-form documentation. The result is a reference layer focused on execution rather than explanation.

The Drop Times received responses from Frank Holldorff, co-founder and CEO of erdfisch, outlining how DevBits prioritises practical implementation over documentation-style explanation.

According to Frank, the project emerged in 2024 from an internal need to document recurring technical solutions, small code snippets, and best practices in a structured way, reducing the need to repeatedly solve the same problems across projects.

This internal system later transitioned into a public-facing resource, with regular publication beginning in late 2025 as a compact and accessible knowledge format.

Unlike conventional documentation or blog-driven tutorials, DevBits are structured for immediate use.

The approach deliberately avoids extended explanation and focuses on minimal, functional clarity. Frank noted that DevBits prioritise clearly understandable, immediately usable solutions rather than contextual or narrative detail.

This design positions DevBits differently within the Drupal knowledge landscape. DevBits isolate implementation by removing explanatory context, positioning them alongside documentation and tutorials rather than replacing them.

The initiative is also framed as part of erdfisch’s ongoing engagement with the open-source ecosystem. The organisation reports more than 1,000 hours of Drupal development each month, forming the experience base from which DevBits draws. Frank added that the effort was conceived as an open-source initiative intended to share knowledge beyond the internal team.

You May Like

Blog

Documenting DrupalCamp England: A Behind-the-Scenes Story

Blog

Documenting DrupalCamp England: A Behind-the-Scenes Story

The workflow reflects a fully remote organisation. Each DevBit is typically authored by the developer who identified and solved the problem, with submissions made directly from the developer’s IDE to a central GitLab repository. This allows solutions to move from implementation to documentation without an additional publishing layer.

A CustomGPT model analyses submitted snippets, generates structured explanations, and assigns tags. These outputs are reviewed and validated internally by developers before publication, ensuring that human expertise remains central to the final published entries.

Each entry passes through a defined release workflow, including internal review cycles such as Friday TeamTime sessions, where developers share and validate work outside client schedules. Contributions are currently maintained internally to ensure consistency, with the team indicating that curated external contributions may be considered in the future while maintaining quality control.

DevBits are not restricted to specific Drupal versions or modules, and in some cases extend beyond Drupal itself. A tagging system enables contextual filtering across use cases, including adjacent tools such as Jira.

nerdfisch DevBits operates as a working archive rather than a learning platform. It documents solutions as they emerge, preserving them close to their original context rather than reshaping them into formal guidance. The collection is publicly accessible at https://erdfisch.de/devbits.