Remove the feeds module

content/node.af570204-edaa-41d8-af54-5136ec8f0954.json

@@ -87,14 +87,5 @@
             "processed": "\n          <p>You're or a new&nbsp;team member are&nbsp;onboarded to a project to make some CSS changes.<\/p>\n\n<p>The project uses Sass, Less or another preprocessor.<\/p>\n\n<p>Not knowing this, the generated CSS files are changed instead of the Sass files.<\/p>\n\n<p>The changes are committed and pushed, but because they weren't added to the Sass files, they will be lost when the&nbsp;CSS files are re-generated in the future.<\/p>\n\n<p>Or, if the Sass and CSS files become too out of sync, everyone will be too worried about losing changes to use the Sass files, so they will be abandoned&nbsp;and not used.<\/p>\n\n<p>What if you change the&nbsp;correct files but don't know the magic command to generate the assets for that project?<\/p>\n\n<p>I've seen things like this happen on numerous projects and is an example of why the \"no build\" approach is appealing.<\/p>\n\n<p>Especially with enhancements to CSS, such as custom properties (variables) and nesting, a lot of the functionality from preprocessors can now be done with normal CSS.<\/p>\n\n<p>This means the front-end build steps can be simplified&nbsp;or removed entirely, reducing the technical overhead and dependency cost, and it's easier for new Developers to get started.<\/p>\n\n<p>Win, win!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "247a1b12455fa21f13c5bcd13b69f5c7",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }