Remove the feeds module

content/node.4b7e6128-69d3-4511-a3ca-cfba25c6e002.json

@@ -87,14 +87,5 @@
             "processed": "\n          <p>Tailwind's configuration file also makes it easy to add it to an existing codebase, whether it uses custom CSS or another CSS framework.<\/p>\n\n<p>You can opt-out of Tailwind's CSS reset and normalisation by adding <code>corePlugins: { preflight: false }<\/code> to tailwind.config.js, and if you have duplicate classes with existing classes and Tailwind-generated ones, you can add <code>prefix: 'tw-'<\/code> to prefix all of Tailwind's class names and avoid the conflicts.<\/p>\n\n<p>If you need to deal with specificity, you can mark Tailwind-generated classes as important by adding <code>important: true<\/code> so that they can override any existing styling. You can do the same in HTML code by prefixing a class name with an exclamation mark - e.g. <code>!flex<\/code>.<\/p>\n\n<p>Or, if you know that your Tailwind styles will only be used within a certain element, like <code>#app<\/code>, instead of making all classes important, by adding <code>important: \"#app\"<\/code> to the configuration, Tailwind classes will be prefixed with that selector - making them more specific.<\/p>\n\n<p>Once these options are set, you can start using Tailwind without affecting the existing styles.<\/p>\n\n<p>Doing this, and starting small by using a small number of utilities can be a good step towards migrating an existing codebase to use Tailwind and removing the existing styles at a later date.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7da91326631cb7cf3b105e8837f5879c",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }