92 lines
No EOL
3.7 KiB
JSON
92 lines
No EOL
3.7 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "01d84025-8b37-4456-b7f0-bf659c3f5a2b"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-05-31T23:12:38+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": "Do you still need that module?"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2025-05-31T23:09:56+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-31T23:12:38+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "",
|
|
"pid": null,
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "<p>If a module or library has been added to an application, it was done to serve a purpose.<\/p><p>It must add some required functionality that was asked for earlier in the application's lifecycle.<\/p><p>It was needed then.<\/p><p>But it is still needed now?<\/p><p>Are the original requirements still valid?<\/p><p>Have they changed or are no longer needed?<\/p><p>If the code is no longer serving a purpose, it should be removed.<\/p><p>Common culprits in Drupal projects are the Feeds and Migrate modules, which are used to import data from external sources, such as legacy applications when migrating to Drupal.<\/p><p>Once the data has been imported and the site is live, the modules are often so longer needed.<\/p><p><a href=\"\/daily\/2025\/05\/30\/do-you-need-module\">As I said yesterday<\/a>, having less code in your application will make it easier to maintain and upgrade in the future, so keep it as lean and minimal as possible - but this is an ongoing process as requirements change over time.<br> <\/p>",
|
|
"format": "basic_html",
|
|
"processed": "<p>If a module or library has been added to an application, it was done to serve a purpose.<\/p><p>It must add some required functionality that was asked for earlier in the application's lifecycle.<\/p><p>It was needed then.<\/p><p>But it is still needed now?<\/p><p>Are the original requirements still valid?<\/p><p>Have they changed or are no longer needed?<\/p><p>If the code is no longer serving a purpose, it should be removed.<\/p><p>Common culprits in Drupal projects are the Feeds and Migrate modules, which are used to import data from external sources, such as legacy applications when migrating to Drupal.<\/p><p>Once the data has been imported and the site is live, the modules are often so longer needed.<\/p><p><a href=\"http:\/\/localhost:8888\/daily\/2025\/05\/30\/do-you-need-module\">As I said yesterday<\/a>, having less code in your application will make it easier to maintain and upgrade in the future, so keep it as lean and minimal as possible - but this is an ongoing process as requirements change over time.<br> <\/p>",
|
|
"summary": ""
|
|
}
|
|
]
|
|
} |