Ratburger.org opened to the public on December 10th, 2017, one year ago today, and the first member (non-administrator) account was registered on that day. A year later, we have 143 members who have made 2,230 posts and 28,048 comments. In the month of November 2017 (I cite the last full month, as partial month statistics can be misleading), the site welcomed a daily average of 1448 visits per day, with visitors viewing 9303 pages involving delivery of 24,745 files.
In the month of November, overall statistics were:
To celebrate, and mark how far we’ve come, I have just posted the never-before-published development logs for the site for December 9th and 10th, 2017 on the Updates Group, with this direct link.
Unrelated to the anniversary (it’s just a coincidence), today Ratburger.org migrated to WordPress version 5.0, the first major update to WordPress released since the site was launched. You may have heard some terrible things about this release, perhaps from me. The WordPress powers that be have decided to introduce a new editor for composition of posts, which was originally called “Gutenberg”, but after user experience with it so poisoned that name, they decided to call it the “Block editor” in the version they finally released. It is fully as bad as everything you’ve heard (shortly before the roll-out it had a user rating of 2.3 out of five stars, with 392 five star reviews and 923 one star reviews). For details of just how awful, see Igor Ljubuncic’s post on why “WordPress Gutenberg will be the end of WordPress”.
The good news is that all of this is entirely hidden from Ratburger users, who may continue to use the “Classic Editor” in either Visual or Text (HTML/Quicktags) mode as they’ve always done. WordPress have promised the user and developer community that the Classic Editor will continue to be available at least “through the end of 2021”, so there’s no immediate cause for concern. If, by then, a viable alternative has not appeared, it is probable it will continue on into the foreseeable future. If they, instead, decide to sink WordPress by forcing an unusable mess of an editor on their users, at least their competitors will have had adequate time to roll out alternatives in their products.
I have tested all of our local modifications against the WordPress 5.0 code base and found no problems. (Other than the inclusion of the new editor, which we don’t use, the differences between 5.0 and the version 4.9.8 which we were running previously are actually not that great.) If you encounter something that looks odd, that’s what the Bug Reports group is for.