{ "uuid": [ { "value": "0318e249-a9a8-476f-9bd4-432544369917" } ], "langcode": [ { "value": "en" } ], "type": [ { "target_id": "daily_email", "target_type": "node_type", "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7" } ], "revision_timestamp": [ { "value": "2025-05-11T09:00:01+00:00" } ], "revision_uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "revision_log": [], "status": [ { "value": true } ], "uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "title": [ { "value": "To patch or not to patch" } ], "created": [ { "value": "2025-02-24T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T09:00:01+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2025\/02\/24\/patch", "langcode": "en" } ], "body": [ { "value": "\n
Applying patch files<\/a> is a common way to customise and extend open source software, and how we used to submit changes to Drupal before issue forks and merge requests were added to Drupal.org.<\/p>\n\n Some software, such as dwm and st from suckless.org are released as minimal versions that you patch to add features to.<\/p>\n\n If you find a line of code that you want to add, edit or delete, a patch file describes the changes so you can re-apply them whenever the source file changes.<\/p>\n\n Patching offers unlimited customisation and flexibility.<\/p>\n\n Whatever changes you want to make, you can.<\/p>\n\n The downside is you need to maintain any patches you've written.<\/p>\n\n If a change is made that causes your patch to no longer apply, you'll need to update the patch.<\/p>\n\n There are some patches I commonly apply to Drupal projects, but I'll try to either contribute the changes back to the Drupal so I no longer need the patch or make the change in a custom module.<\/p>\n\n Sometimes, though, patching is the only option<\/a>.<\/p>\n\n ",
"format": "full_html",
"processed": "\n Applying patch files<\/a> is a common way to customise and extend open source software, and how we used to submit changes to Drupal before issue forks and merge requests were added to Drupal.org.<\/p>\n\n Some software, such as dwm and st from suckless.org are released as minimal versions that you patch to add features to.<\/p>\n\n If you find a line of code that you want to add, edit or delete, a patch file describes the changes so you can re-apply them whenever the source file changes.<\/p>\n\n Patching offers unlimited customisation and flexibility.<\/p>\n\n Whatever changes you want to make, you can.<\/p>\n\n The downside is you need to maintain any patches you've written.<\/p>\n\n If a change is made that causes your patch to no longer apply, you'll need to update the patch.<\/p>\n\n There are some patches I commonly apply to Drupal projects, but I'll try to either contribute the changes back to the Drupal so I no longer need the patch or make the change in a custom module.<\/p>\n\n Sometimes, though, patching is the only option<\/a>.<\/p>\n\n ",
"summary": null
}
]
}