wp2static VS WordPress-Coding-Standards

Download and Install WP2Static Plugin

> It is not actually that hard to run Wordpress securely. Stick to supported plugins and themes, and install security patches quickly when they are released.

Depending on your site's functionality, it may also be possible to run a static WP site:

* https://wordpress.org/plugins/simply-static/

* https://wp2static.com

You do all your regular updates via the CMS, but, instead of putting the dynamic site on the public Internet, you generate static files and point your public web server's HTML rootdir at those.

Also, for a bit more complex although richer in features workflow, you might try Wordpress with the Block Editor (or any page builder like Elementor) and the [WP2Static](https://github.com/WP2Static/wp2static) plugin, which allows you to turn a Wordpress site into a static one!

The closest "free" option I can think of is Oracle Cloud, but /r/oraclecloud shows plenty of horror stories in registration and maintaining an instance. If you don't actually need interactive features, WP2Static on your local instance to be deployed to Cloudflare Pages might work.

> Most WP sites should be static sites.

https://wordpress.org/plugins/simply-static/

https://wp2static.com

Depending on the site, ask yourself "How dynamic does it actually have to be?". Perhaps using the GUI to update the content, and then creating static files and serving those may be an option:

* https://wp2static.com

You could also use WordPress as a SSG with the WP2Static plugin — https://github.com/WP2Static/wp2static/

What is wrong with using Wordpress? I believe now one can get Wordpress to have 'static site' capabilities these days [0]

[0] https://wp2static.com/

Is a Docker WordPress Environment focused on the development of WordPress plugins and themes, supports WP-CLI, phpMyAdmin, Xdebug and WordPress Coding Standards - WPCS.

PHP Code Sniffer helps us to achieve uniformity of code styles, we also can add other standards, like WordPress Coding Standars, some companies define their own standards etc. There are several ways to config that, but in this article, I will manage WordPress Coding Standards through Composer so we can manage these standards per project, using VS Code IDE.

WPCS's static code checks don't seem to recognize the vulnerability either, so I opened an issue: https://github.com/WordPress/WordPress-Coding-Standards/issues/2217.

Are you a new developer in general or is WordPress new for you as a developer? In my experience it's best to practise and start with little plugins. Be sure to use a code-sniffer which enforces the WordPress coding standards.

The standard here is probably wpcs (https://github.com/WordPress/WordPress-Coding-Standards) which is a set of rules for the tool phpcs (https://github.com/squizlabs/PHP_CodeSniffer)

We use WordPress Coding Standards for PHP_CodeSniffer (WPCS) which uses Squizlabs' PHP codesniffer (phpcs) and beautifier & fixer (phpcbf) under the hood to scan and format the code.

You can also save yourself some time too by making use of the WordPress ruleset for PHPCS. I've integrated this into my code editor so it evaluates my code on-the-fly.