"value":"\n <p>Open-source software, such as Drupal modules and themes, PHP libraries and Tailwind CSS plugins, is great.<\/p>\n\n<p>Instead of writing everything from scratch, if someone else has written what you need, you can use it.<\/p>\n\n<p>In the Drupal ecosystem, there's a saying - \"There's a module for that!\".<\/p>\n\n<p>But, assuming you find a project that adds the functionality you need, you should review and vet it before adding it to your application.<\/p>\n\n<p>Adding too many modules and libraries can cause performance issues, add a maintenance overhead, introduce upstream bugs and add potential security vulnerabilities.<\/p>\n\n<p>As well as reading the code, here are some questions I ask and things I look for when deciding to add a project or not:<\/p>\n\n<ul>\n<li>Does it do what I need?<\/li>\n<li>Does it add too much functionality? Is there a more minimal version that does what I need without the extra overhead?<\/li>\n<li>Does it have a stable release? If there's only a development or alpha release (which are unstable and can break at any time), I wouldn't add it.<\/li>\n<li>Is it extendable? Can I configure or extend it if I need to add more or alter it's default functionality?<\/li>\n<li>How many other websites are using it? Websites like Drupal.org and Packagist will show usage statistics.<\/li>\n<li>How many open issues are there?<\/li>\n<li>When was the most recent commit and release?<\/li>\n<li>Does it have automated tests? If so, are they passing?<\/li>\n<li>Does it have a README.md file or other documentation?<\/li>\n<li>Who are the maintainers?<\/li>\n<li>Are they responsive to issues and accepting of outside contributions? If I find a bug, can I fix and contribute it?<\/li>\n<li>Does the project have a published roadmap?<\/li>\n<\/ul>\n\n<p>Finally:<\/p>\n\n<p>Do I really need it?<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>Open-source software, such as Drupal modules and themes, PHP libraries and Tailwind CSS plugins, is great.<\/p>\n\n<p>Instead of writing everything from scratch, if someone else has written what you need, you can use it.<\/p>\n\n<p>In the Drupal ecosystem, there's a saying - \"There's a module for that!\".<\/p>\n\n<p>But, assuming you find a project that adds the functionality you need, you should review and vet it before adding it to your application.<\/p>\n\n<p>Adding too many modules and libraries can cause performance issues, add a maintenance overhead, introduce upstream bugs and add potential security vulnerabilities.<\/p>\n\n<p>As well as reading the code, here are some questions I ask and things I look for when deciding to add a project or not:<\/p>\n\n<ul>\n<li>Does it do what I need?<\/li>\n<li>Does it add too much functionality? Is there a more minimal version that does what I need without the extra overhead?<\/li>\n<li>Does it have a stable release? If there's only a development or alpha release (which are unstable and can break at any time), I wouldn't add it.<\/li>\n<li>Is it extendable? Can I configure or extend it if I need to add more or alter it's default functionality?<\/li>\n<li>How many other websites are using it? Websites like Drupal.org and Packagist will show usage statistics.<\/li>\n<li>How many open issues are there?<\/li>\n<li>When was the most recent commit and release?<\/li>\n<li>Does it have automated tests? If so, are they passing?<\/li>\n<li>Does it have a README.md file or other documentation?<\/li>\n<li>Who are the maintainers?<\/li>\n<li>Are they responsive to issues and accepting of outside contributions? If I find a bug, can I fix and contribute it?<\/li>\n<li>Does the project have a published roadmap?<\/li>\n<\/ul>\n\n<p>Finally:<\/p>\n\n<p>Do I really need it?<\/p>\n\n ",