Contribution Records organization listing | Drupal.org

- Drupal Core The open source framework behind millions of websites
- Drupal CMS Drupal CMS puts the power of Drupal into the hands of marketers, designers and content creators
- Drupal AI Open limitless possibilities with Drupal AI
- Case Studies Powerful stories that show Drupal solutions in the real world
- Drupal for Government Drupal is the open-source CMS that enables digital transformation of government and increases citizen engagement
- Drupal for Higher Education See why 70% of the world's leading universities chose Drupal
- Drupal for Nonprofit See why Drupal is the open-source CMS choice for some of the world’s most influential nonprofits
- Drupal for eCommerce Natively integrate content and commerce
- Drupal for FinTech Secure and trustworthy FinTech infrastructure
- Drupal for Healthcare Drupal powers systems that are secure, patient-centric and engaging
- Drupal for Enterprise Why enterprise organizations choose Drupal for multi-brand governance and global scale.
- Drupal for Retail See how Drupal delivers retail experiences across every channel and touchpoint.
- Drupal for Travel & Tourism Discover how Drupal powers travel across websites, mobile, and onboard experiences.
- Download Drupal Download Drupal and the extensions you need
- Documentation Full knowledgebase including Drupal 7 resources
- Getting Started Guide to installing Drupal on a server
- Local Development Guide Guide to installing Drupal locally with Docker and DDEV
- Developer Resources Step-by-step guide for learning Drupal
- Drupal User Guide Learn to build with Drupal
- API Complete documentation of Drupal Core APIs
- Modules Extend your project's functionality
- Themes Change your project's look and feel
- Recipes Automate module installation and configuration
- Site Templates Complete, configured starting points for your Drupal website
- Issue Queues Report issues and contribute improvements
- Security Advisories Stay on top of the latest security alerts and updates
- Find a Drupal Certified Partner Connect with the best Drupal agencies around the world
- Become a Drupal Certified Partner Join an elite network of agencies committed to Drupal excellence and innovation
- Find a Hosting Provider Find a hosting provider for your Drupal project
- Find a Migration Partner Get help with your migration to the latest version of Drupal
- Find Training Upskill your Drupal team
- Drupal Steward Ensure your website is protected with Drupal Steward
- About the Community Come for the code, stay for the community
- How to Contribute Get involved in growing and evolving Drupal
- DrupalCon DrupalCon unites experts from around the globe who create ambitious digital experiences. Network, learn, and be inspired
- Events Discover local events, meet-ups, and training
- Jobs / Careers Find opportunities to work in Drupal
- News & Blogs News and stories about Drupal
- Forum Got a question about Drupal? Find answers on the Drupal forums
- Slack Get support and communicate with the global Drupal community
- Newsletters Sign up for Drupal news and manage your subscriptions
- Drupal Swag Shop Get your Drupal branded merch!
- The Drupal Association Learn how we support Drupal's growth and innovation - and how you can help
- Become a Member Become a Ripplemaker and support the Drupal Association
- Become a Drupal Sustaining Member Supporting the infrastructure the Open Web depends on
- Become a Drupal Certified Partner Join an elite network of agencies committed to Drupal excellence and innovation
- Donate Make a donation to the nonprofit that supports Drupal
- Log in
- Create account
- Try Drupal CMS
- Try hosting

Displaying 351 - 400 of 834

FlowDrop

The executor plugin id comes from the node type, never from the payload (SCH-28)
Thu, 07/30/2026 - 18:53
The wire shape is lean: emit a key only when it diverges from the default (SCH-27)
Thu, 07/30/2026 - 18:53
The editor catalog serves enabled node types, sorted (SCH-26)
Thu, 07/30/2026 - 18:53
Enrichment anchors on the node-type id alone (SCH-25)
Thu, 07/30/2026 - 18:53
Building node data logs and degrades instead of failing the editor (SCH-24)
Thu, 07/30/2026 - 18:53
The UI schema is generated from the final config schema (SCH-23)
Thu, 07/30/2026 - 18:53
Only a config-edit provider gets a configEdit block (SCH-22)
Thu, 07/30/2026 - 18:53
Every node gets a reserved instance title and description (SCH-21)
Thu, 07/30/2026 - 18:53
A node's visual type comes from the config entity only (SCH-20)
Thu, 07/30/2026 - 18:53
Both key enumerations skip trigger and hidden parameters (SCH-19)
Thu, 07/30/2026 - 18:53
Prepend the unified output port when the node exposes one (SCH-18)
Thu, 07/30/2026 - 18:53
Prepend the unified input port when the node exposes one (SCH-17)
Thu, 07/30/2026 - 18:53
The exposure defaults of the reserved ports (SCH-16)
Thu, 07/30/2026 - 18:53
An injected port declares its exposure default only when it diverges (SCH-15)
Thu, 07/30/2026 - 18:53
Inject the reserved error output on every executable node (SCH-14)
Thu, 07/30/2026 - 18:53
Inject the reserved tool output only on a tool-exposed node (SCH-13)
Thu, 07/30/2026 - 18:53
Inject the reserved trigger output on every node but a terminal node (SCH-12)
Thu, 07/30/2026 - 18:53
Inject the reserved trigger input on every node but a start node (SCH-11)
Thu, 07/30/2026 - 18:53
The schema-to-dataType map is closed (SCH-10)
Thu, 07/30/2026 - 18:52
A union type normalizes to its first non-null member (SCH-9)
Thu, 07/30/2026 - 18:52
One mapping turns a schema into ports (SCH-8)
Thu, 07/30/2026 - 18:52
An output reaches the editor only when the node type exposes it (SCH-7)
Thu, 07/30/2026 - 18:52
A parameter is required on the input side only when it is not configurable (SCH-6)
Thu, 07/30/2026 - 18:52
Reserved config-only parameters never become ports (SCH-5)
Thu, 07/30/2026 - 18:52
Hidden parameters are dropped from both derived schemas (SCH-4)
Thu, 07/30/2026 - 18:52
Deriving splits one parameter schema into an input schema and a config schema (SCH-3)
Thu, 07/30/2026 - 18:52
Schema derivation reads its gate flags from the plugin schema (SCH-2)
Thu, 07/30/2026 - 18:52
A node's input and output surface comes only from its two schema methods (SCH-1)
Thu, 07/30/2026 - 18:52
Transport edges and job-metadata edges each own their own key names (EDGE-9)
Thu, 07/30/2026 - 18:52
Edge conditions are a removed feature that is tolerated but never read (EDGE-8)
Thu, 07/30/2026 - 18:52
What makes a node tool-only (EDGE-7)
Thu, 07/30/2026 - 18:52
An edge is an error edge by its source handle (EDGE-6)
Thu, 07/30/2026 - 18:52
An edge is a tool edge by declared type, else by its target handle (EDGE-5)
Thu, 07/30/2026 - 18:52
An edge is a loopback edge when its target handle says so (EDGE-4)
Thu, 07/30/2026 - 18:52
An edge is a trigger edge when its target handle says so (EDGE-3)
Thu, 07/30/2026 - 18:52
No wire key is structurally required; an absent one becomes a missing endpoint (EDGE-2)
Thu, 07/30/2026 - 18:52
How a port handle encodes its node, direction and port name (EDGE-1)
Thu, 07/30/2026 - 18:52
Refuse a duplicate edge between the same two ports (R13)
Thu, 07/30/2026 - 18:52
Refuse an edge from a node to itself (R12)
Thu, 07/30/2026 - 18:52
Every configured expression must pass its engine's check at save (R11)
Thu, 07/30/2026 - 18:52
A workflow exposure must target a port exposed on the node instance (R10)
Thu, 07/30/2026 - 18:52
A node's node-type anchor must resolve to a node type that exists (R9)
Thu, 07/30/2026 - 18:52
Edge ids must be present and unique at save (DECIDED) (R3)
Thu, 07/30/2026 - 18:52
Node ids must be unique (DECIDED) (R2)
Thu, 07/30/2026 - 18:52
The whole validator runs again at launch (VAL-LAUNCH)
Thu, 07/30/2026 - 18:52
The validator instantiates plugins only for the exposure checks (VAL-PERF)
Thu, 07/30/2026 - 18:52
Warn about an edge leaving a terminal node (W-T)
Thu, 07/30/2026 - 18:51
An exposure must name a port the plugin declares (R4.d)
Thu, 07/30/2026 - 18:51
An exposure must name a node that exists (R4.c)
Thu, 07/30/2026 - 18:51
Exposure names must be unique per side (R4.b)
Thu, 07/30/2026 - 18:51