lokl VS WordPress-Coding-Standards

I've used GeneratePress and their blocks. I might give SimplyStatic another shot this weekend, this time with full site editing and a fse theme I'm making. I also want to try another alternative. SimplyStatic was forked from an earlier version of wp2static included in the bundle.

Timely plug for Lokl, which I just put out a new release for over weekend :) Allows creating/managing a bunch of WP sites locally, optimized for deploying statically.

I've switched from the Jamstack/static site generators to nocode WordPress for content sites, to focus my coding more on app UIs in the long term.

Jamstack is nice, but it's either for personal developer blogs or larger teams. Outsourcing is too expensive with coders being in high demand.

Everything WP can be easily outsourced when needed, and there really isn't much of a speed benefit with Jamstack sites if you cache your WP site on the edge (e.g. with Cloudflare APO). Security of the origin server isn't a problem with a good host or going static.

You can generate static sites from a local WP install if you find secure hosting too expensive, here's a nice docker based tool for this: https://lokl.dev/

WP is really as hard, ugly fast or slow as you make it, you have to find the right theme and plugin ecosystem within WP.

I don't have to and don't need touch the code building sites with it, so all those weird WP code conventions don't really bother me.

There’s also lokl.dev from the wp2static dev

It might be worth mentioning that Lokl [0] seems to be from the same author [1] as the "wp2static" plugin [2], my and many others go to for static site generation of WordPress.

I find Lokl and interesting take, although the usual self-serve script is kind of annoying for power users (what I mean is that this bash scripts tried to do everything for you and it's less transparent), I recommend the repo [4] as the source of the actual Dockerfiles, that you could just reference in something like a docker-compose setup.

The Dockerfiles are kind of surprising since they read more like a an ansible-playbook than like a Dockerfile. This one image has it all - php, nginx, mariadb, phpmyadmin and who knows what else [4]. It's an interesting approach to Docker images, certainly against the recommendation but might have some good reasoning for something as special as WordPress.

[0]: https://github.com/leonstafford/lokl-cli

[1]: https://github.com/leonstafford

[2]: https://github.com/leonstafford/wp2static

[3]: https://github.com/leonstafford/lokl

[4]: https://github.com/leonstafford/lokl/blob/master/php8/Docker...

For Automation, I've got full end to end tests using it in the main https://github.com/leonstafford/lokl repo. Just 1 E2E test in there so far, but that's what I'm planning to use to generate living documentation for the project itself and my SSGs included with it (I suck at maintaining docs otherwise!).

I thought the reddit discussion did a better job explaining it, but here are the direct links:

https://lokl.dev/

https://github.com/leonstafford/lokl

The developer, Leon Stafford, is also working hard on WP plugins that convert to static sites and even upload directly to popular services such as Cloudflare, Netlify, Amazon, etc.

(I am not associated with this project.)

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.