µ3: WordPress

My focus this µsprint was WordPress (which I haven’t really looked that much into), with the following results:

  • https://veduz.com now using WordPress again.
  • Added statistics to sites, – setting up a matomo-server, and added the WP-matomo-plugin.
  • Improved my WordPress dev setup (documented below).
  • Survey of themes and plugins.
  • Made tiny wordpress plugin, which lists my web/apps.
  • Started documenting µsprints on veduz.com.
  • Tried to fix WordPress plugin bug for a friend (but blocked, as the issues was non-reproducible in my setup).
  • Helped another friend setup WordPress sites.
  • Some (non-WordPress) consulting.

Takeaways

  • docker + npx browser-sync for wordpress dev environment (see notes below)
  • Neve seems to be one of the best bets for a general theme (very popular and good open source development despite being quite new, and quite customisable)
  • Brush up on how to make simple wordpress plugin
  • µSprint public notes in wordpress, and tasks-progress/private-notes in daylog/notes.

Site builders

  • Elementor Pro has bad license for development (tries to be non-GPL), and thus not interesting.
  • Beaver Builder Lite does not work with multi-site, – thus I cannot just turn it on to experiment with (and do not need it enough to buy it yet).

WordPress development environment

One configuration file, and two commands, – let let docker-compose.yml contain:

version: '2' 
services:
db:
image: mariadb
environment:
MYSQL_ROOT_PASSWORD: XXXXXX
volumes:
- ./mariadb:/var/lib/mysql
adminer:
image: adminer
ports:
- 3003:8080
wordpress:
image: db
ports:
- 3002:80
environment:
WORDPRESS_DB_PASSWORD: XXXXXX
WORDPRESS_DB_USER: root
WORDPRESS_DB_HOST: mariadb
volumes:
- ./www:/var/www/htm

(replacing XXXXXX with proper password)

And then just run docker-compose up.

To have auto-reload run npx browser-sync start --proxy "localhost:3002" --files www/**