Raise an issue first, gauge the reaction, and then create a PR if you think they would welcome it. Whether it's a website or some other open source project, ma

Raise an issue first, gauge the reaction, and then create a PR if you think they would welcome it. Whether it's a website or some other open source project, maintainers usually don't like it when you create a massive refactoring PR without talking with them first. If, luckily, the maintainers are on HN, I guess talking about the "problem" here could very well substitute for raising an issue on whatever platform they use.