lokl-cli VS gutenberg

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...

But, in the last builds, I added support to run Lokl noninteractively, by setting environment variables. Ugh, Readme on Lokl main GitHub repo now stale, but lokl-cli's source shows how to run it as such: https://github.com/leonstafford/lokl-cli/blob/master/cli.sh

For anyone wondering, this is not gutenberg.org, Gutenberg is the name of the Block Editor from WordPress

> The Block Editor project for WordPress and beyond. Plugin is available from the official repository.

https://github.com/WordPress/gutenberg

In this last and specific case I was working with a Laravel application that needs to interact with a WordPress site, and as both works from different Compose projects, I need to add a custom configuration to allow internal requests between them, what get easy to do with Laravel Sail, simply adding a extra_hosts configuration to the docker-compose.yml file but was impossible to do with wp-env and probably will not be implemented as we can see from this Github issue.

The meteoric rise of plugins like Advanced Custom Fields (which is still an excellent plugin and serves it’s purpose very well), and page builder Themes like Divi, was a result of a gap in WordPress’s page editing abilities. And while these things may have been absolutely necessary in the past, with the introduction and integration of Gutenberg into WordPress core, that is no longer the case.

If you are using Gutenberg editor on your WordPress website, simply select the block you would like to create a pattern for, then click the three dots at the top-right corner of the block editor and click "Create reusable block".

Gutenberg is attempting to be a Frontend / UI style site editor (example here: https://wordpress.org/gutenberg ). An amazing example of this type of editor is Webflow. Lesser examples include Square Space and Wix which is what these other plugins, Divi/Elem/Avada/Salient do is provide professional templates that allow users to build from. These push WP from simple blog to an actual website experience. You can think of them, and Webflow imo, kinda like photoshop for websites, or maybe Figma for web development. They allow designers to learn a tool instead of CSS / JS. What I think the WP theme builders really excel at is getting something that looks modern and fast really really quickly. I'm happy to talk about the market and who builds licenses for the WP theme builders but this post would be a book! haha.

Vanilla WP is excellent for beginners who aren't trying to do anything fancy, in fact I think its one of the best things to ever happen to the web. Yes there are exploits etc but that comes with all software. But most other software doesn't run something like 30-40% of the web though so their bugs are really magnified. Same goes for the WP plugin theme builders I mentioned above.

You can also add your support and follow of the status of this ticket on Github.

WordPress 6.2 “Dolphy”, the first major release in 2023, includes more than 900 enhancements and bug fixes. But WordPress/gutenberg still had 4842 open and 18128 closed issues at the time of writing, including 1051 open issues labeled as bugs.

WordPress bundles Gutenberg - https://wordpress.org/gutenberg/ and it comes fully featured with full site editing - https://fullsiteediting.com/.