Ari Stathopoulos

The plugin-territory functions currently includes 4 functions: https://github.com/WordPress/theme-check/blob/17dd4eb9393a6e6eca45401f01f629fe752e81e5/checks/class-plugin-territory-check.php#L33-L38 * `register_post_type`: This should definitely be kept because if we remove it then users will lose content when switching themes. * `register_taxonomy`:...

I think we can also remove the appearance-menu rule...

> I suggest to change the text here, Place WordPress _**core**_ features behind a paywall. Why change this? They can place their own features behind a paywall if they want,...

This was done using the `WP_Filesystem` because at the time file operations were not (and still are not) allowed directly in themes. If I remember correctly they were even throwing...

Just my 2c: For simple projects like this one with minimal JS & CSS, a build process is more annoying than useful. I agree that we should use something consistent...

When you put it like that it makes perfect sense :laughing:

This PR can improve soooo many things! I love it ❤️

I believe this is also part of the refactor in https://github.com/WordPress/gutenberg/pull/25892

I still don't understand why we **need** this block. Is it something that users want to import in multiple pages? Then why can't they create a reusable block with a...

I agree that we need some strings that are dynamic... But I'd prefer to have a mechanism to inject dynamic strings in content - in lieu of custom blocks. I...