WordPress has supported a Themes System since 2005.
The first default theme was called Kubrick.
Since then thousands of themes have been developed. Over 8,500 are available from wordpress.org/themes
There are many more. Some of them you can buy fairly cheaply. But there are also countless custom themes, developed by individuals and agencies, that provide the look and feel of millions of WordPress sites.
So which is my favourite?
Last updated:July 13, 2021
At the WordPress Cambridge meetup on 10th May 2021 I gave a slightly longer version of the Show & Tell talk I’d prepared for WPChelt in April. “Does my site run slow with this?” reports on attempts to measure WordPress server response, and the plugins used to visualise the results.
These are the slides for the talk.
Last updated:May 11, 2021
Yesterday, the Cheltenham WordPress Meetup was a series of Show and Tell talks. Along the lines of Lightning talks, these are talks of approximately 10 minutes, where individuals share something they’ve been working on. There were 7 talks planned:
This post is the annotated version of the slides.
Last updated:April 20, 2021
An update on my long running endeavour to visualise the effect on server performance of changes to my WordPress websites.
Since 2015 I’ve been developing a routine to compare the effect on server response times of the top 12 WordPress plugins. I’m just about ready to publish some results.
Last updated:February 14, 2021
OK. so I’ve demonstrated that my iPad can’t display WebP format images, so I’ll have to try the picture tag method as a polyfill.
This is the sample HTML copied from CSS Tricks: Using WebP Images.
So let’s try displaying
oik-types-banner-772x250.webp to browsers that support it and the JPEG version for those that don’t.
Last updated:February 6, 2021
The WordPress Gutenberg project’s plan for internationalization (i18n) and localization (l10n) of Full Site Editing themes (FSE) has not yet been formulated. I’ve written a proposal, entitled Internationalization and localization: translating templates and template parts, raised as Feature request #27402.
I believe that very little needs to be done to Internationalize a file containing Gutenberg blocks and HTML, and that it can be translated and localized into a statically delivered file in the user’s required locale ( language and country ) using the process described in the feature request.
This post briefly discusses some of the challenges of translating rich text content.
Last updated:December 6, 2020
I’ve been using GitHub since October 2012 but until recently I’ve had very little understanding of any working process that enables me to contribute to other projects using Pull Requests ( PRs ).
But now I’ve started to try to work with branches. Two reasons:
In this post I’ll document the process I’m using for developing PRs against Gutenberg issues.
I read the instructions on WordPress.org. They all made sense, but I couldn’t work out how to create a PR that only contained the changes I’d intended to make. While the overall effect of my PRs were the change I intended, every Pull Request consisted of multiple commits, not just the one I wanted to apply. Obviously I was doing it wrong.
I read some Stack Overflow items ( thanks Angel for directing me to them ) and discovered the git commands that appear to do the job.
I’ve now created 4 or 5 PRs using this method. And so far I’ve not had any problems. This is a good thing. I’ve just re-read the Git Workflow process and realised it’s almost exactly the same.
cd \apache\htdocs\wordpress\wp-content\plugins git clone https://github.com/bobbingwide/gutenberg.git gutenberg-source cd gutenberg-source git remote add upstream https://github.com/WordPress/gutenberg.git git fetch --all
Work in a new branch (
git checkout -b fix/%1 upstream/trunk
Now make and test changes in the new branch. Add files and commit as often as necessary, with a nice commit message, referencing the issue number each time?
git commit -m "good commit message 50-70 characters
When ready push the changes to your fork of the repository (
git push -u origin fix/%1
Theoretically this should work for any repository.
Then change back to the main branch
git checkout trunk
To keep the local repository up to date use
fetch --all. I believe this has to be done in
C:\apache\htdocs\wordpress\wp-content\plugins\gutenberg-source> git checkout trunk git fetch --all Fetching origin Fetching upstream remote: Enumerating objects: 3248, done. remote: Counting objects: 100% (3248/3248), done. remote: Compressing objects: 100% (273/273), done. Receiving objects: 100% ( Receiving objects: 100% (4749/4749), 51.99 MiB | 3.85 MiB/s, done. Resolving deltas: 100% (3648/3648), completed with 996 local objects. From https://github.com/WordPress/gutenberg ...
For the 150 or so GitHub repositories under
bobbingwide I developed all my changes in the
main branch. It’s still called
master for many of them. Then I pulled the changes to a local version in
C:\github\bobbingwide\repository-name and pushed them from there.
I had two copies of each repository. One reason for this was protection against having the repository destroyed accidentally by WordPress updates or unpacking
.zip files into other development enviroments.
Last updated:May 28, 2021