Remove the feeds module

content/node.92b0bd2f-d0fe-4d21-b208-961525c053ea.json

@@ -87,14 +87,5 @@
             "processed": "\n          <p>Almost all Drupal projects have multiple environments - production and one or more pre-production environments.<\/p>\n\n<p>A lot have development and staging, some have QA or UAT, or an environment per feature or sprint.<\/p>\n\n<p>Each Developer has their own local environment to work on.<\/p>\n\n<p>As new things are added, such as content types, fields and views, they need to be present on all environments.<\/p>\n\n<p>When I started using Drupal, I needed to perform the same steps to manually recreate the changes on each environment.<\/p>\n\n<p>Later, people started to use the Features module to export configuration into modules that could be committed and deployed as code.<\/p>\n\n<p>This was accompanied by \"deploy\" modules that included update hooks to revert features or perform other tasks.<\/p>\n\n<p>Since version 8, Drupal has had the Configuration Synchronization module.<\/p>\n\n<p>Developers make changes once and export them to files using a simple command like <code>drush config:export<\/code>.<\/p>\n\n<p>Once the code has been deployed to each environment, run <code>drush config:import<\/code> to import the changes.<\/p>\n\n<p>This will synchronise the configuration on the environment, making it the same as the exported configuration in an automated way - the same way every time.<\/p>\n\n<p>Much quicker and more robust than doing it manually.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a689477a80adb90fdbe7160be7d2450e",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }