Remove the feeds module

content/node.b3a28a86-02c5-45ea-8a51-32508cd34b7d.json

@@ -87,14 +87,5 @@
             "processed": "\n          <p>Today I noticed that Drupal's Experience Builder project <a href=\"https:\/\/www.drupal.org\/project\/experience_builder\/issues\/3454669\">has adopted architectural decision records<\/a>.<\/p>\n\n<p>From the issue:<\/p>\n\n<blockquote>\n  <p>I proposed [...] to start adopting ADRs to document decisions that were made. That\u2019d allow us to stop rehashing past conversations and allow people to onboard with fewer meetings.\n  \u2026 or so I think.\n  Because I think that ADRs could be an excellent way to scale this project up to A) many people, B) many timezones.<\/p>\n<\/blockquote>\n\n<p>I like this decision and have adopted and <a href=\"http:\/\/default\/daily\/2024\/06\/12\/recording-architectural-decisions\">written about ADRs before<\/a>.<\/p>\n\n<p>I also like that the documents <a href=\"https:\/\/git.drupalcode.org\/project\/experience_builder\/-\/tree\/0.x\/docs\/adr?ref_type=heads\">are stored as markdown files in the repository<\/a>, alongside the code, making it easy for everyone to view or change.<\/p>\n\n<p>As the work on Experience Builder continues, new contributors can read these documents and understand why previous decisions were made, which is extremely valuable.<\/p>\n\n<p>I'm interested to see how ADRs work for the Experience Builder project and whether they're adopted more widely in other parts of the Drupal ecosystem.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "9553ccae6f298ace5c5f247750bea8a2",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }