Home

Awesome

WordPress website lifecycle

Tweet

How to work with WordPress. :bulb: #active-development #self-hosted #long-term #monitoring

We run WordPress on Debian GNU/Linux operating system which runs on an UpCloud cloud instance.

Division of labour

Who does what.

  1. Editor manages the content and related settings.
  2. Developer commits plugin and theme source code to GitHub and initiates deployment (CI/CD).
  3. Viktor manages the operating system, webserver software, WordPress core, plugins, the theme, privileged users, system settings, security, backup and migrations.

There is no web-based administration. WordPress installation is managed with git, Composer and WP-CLI on the command-line.

More than the famous 5-minute installation

Our WordPress installation includes preparations for the next few error-free years.

These preparations are implemented in MU plugins.

Support my work

Please consider sponsoring me monthly if you use my packages in an agency.

Sponsor

They are already sponsoring me.

<!-- markdownlint-disable MD033 -->

<img src="https://github.com/johnbillion.png" width="50px" alt="johnbillion">   <img src="https://github.com/JJJ.png" width="50px" alt="JJJ">   <img src="https://github.com/montchr.png" width="50px" alt="montchr">   <img src="https://github.com/blockifywp.png" width="50px" alt="blockifywp">  

<!-- markdownlint-enable MD033 -->

Working in a git repository

Our WordPress installation is stored in a git repository and managed with Composer.

This is the starter template. szepeviktor/composer-managed-wordpress

Custom plugins and themes live in separate git repositories.

Purchased themes should have an active child theme.

wp plugin install child-theme-configurator --activate

Keep the child theme in a git repository also.

Onboarding for developers

Let's prevent working against each other!

High level overview

:bulb:

Installation materials

Theme review

Development stuff

Testing