Refactor code to abstract various technologies

Looks good @the_g_bomb I was thinking of refactoring against something like the Web Sustainability Guidelines

• User Experience Design
• Web Development
• Hosting, Infrastructure, Systems
• Business Strategy & Product Management

As I suggested here https://www.drupal.org/project/pasc/issues/3512043 📌 Move to Performance and Sustainability Checklist Active

But that's just a framework to think about the bigger problem.

We'd also talked about spinning out Apache/Nginx, MySQL/SQLite/Postgresql and PHP out into a sub-module, as if you're hosting on Acquia or Panteon, you're not going to be fiddling with their configs.

But with this approach here, I'm wondering about starting with Apache, as that's not the lowest common denominator. Probably most folks installing this will be Drupal admins. They might be able to use this to bring in front-end design folks into the equation.

I took a look at YSlow and just realized how old that library was. Is it still a best practice? I think sitespeed.io or Unlighthouse.dev would be better.

Take any of the auto-detect code for the module considerations.

I really don't think that those should be checklists, since we know what modules are installed (and shouldn't be).

I do like reminding folks to disable the PASC module, as having this enabled in production isn't going to help anyone.

Several of the links to best practices are only available on Archive.org. I think we can find new references that would be better than archived pages from over a decade ago. I hope so. Maybe not.

Gander is something I wanted to mention but haven't yet https://www.tag1consulting.com/blog/gander-future-drupal-performance-and...

Worth including, I think.