What a year! At the end of 2017, I remember thinking that the previous year had been one of the biggest when it came to change in WordPress. But I didn’t know what was in store for 2018!2018 has seen some of the most fundamental and farthest-reaching changes in WordPress since its inception, embodied by the Gutenberg plugin (and the row over it).But in my view, it’s not Gutenberg that will dominate 2019—it’s the changes it heralds.So let’s take a look at what 2019 might have in store for WordPress and its community of users and developers.The WordPress CodebaseGutenberg represents the beginning of a fundamental shift in the WordPress codebase.Remember Matt Mullenweg’s State of the Word 2015 (yes, it was that long ago), when he told everyone to “learn JavaScript, deeply”?Well, now is the time when those people who listened to him will…
From “Ready for Beta” I went back to “Pre-Alpha, format everything and start over”, by experience / luck / care I have maintained a versioning of the site in my local developer environment,
Two days ago I posted a grumble about how WordPress was incredibly slow and cumbersome, it really is slow and cumbersome but even after removing…
To solve the problem, I edited the WP_ADMIN / POST.PHP and POST_NEW.PHP files including this style sheet code (CSS) at the end of the files.
Now is time to make a good full backup of the current state, from tomorrow 10 / January / 2019 begins the beta phase.
Sometimes it seems like a lot of developer time is lost correcting flaws in other people’s programs …
At first, it seemed to be an easy ride, get the Amazon AWS Free Tier to connect with my domain, setup the DNS server to the Web Server, install any freeware CMS or perhaps build/compile some open source basic website management, publish whatever I want to my domain, profit!