WordPress history, from 4.9 to the Gutenberg era
WordPress 4.9 was "the calm before the storm." We analyze this pivotal moment in WP history that prepared the ground for the block editor. What changed since? How did the ecosystem evolve?
I am Mariusz Szatkowski, a WordPress developer working from Gdynia, Poland. I have no office in Edinburgh. I build WordPress and WooCommerce sites for Edinburgh businesses remotely, by email and shared documents, and I reply within 48 hours.
Poland is one hour ahead of the UK, so your 9:00 is my 10:00. Scope, quotes and handover are written down and sent as documents, which is why the time difference rarely matters.
I have had a wordpress.org account since 2006, contributed to WordPress core for versions 7.0 and 7.1, maintain 30 plugins on wordpress.org, organise and speak at WordCamps, and have been at every WordCamp Europe from 2017 to 2026.
Most briefs fall into three kinds: a company site that has to take enquiries, an ecommerce store, and an older site that has outgrown its theme. For the first kind I use a block theme with theme.json, so the editor shows what the page will look like and the layout rules live in one file. A classic PHP theme stays when it carries template logic that costs more to port than to keep. I write that trade-off down before the first commit.
Logic that has to survive a redesign, such as custom post types, roles, forms and integrations, goes into a plugin. Presentation stays in the theme. If the service list vanishes when you change theme, the boundary was drawn wrong.
For ecommerce I use WooCommerce, covered on the WooCommerce developer in Edinburgh page. The full development scope is on the WordPress developer page.
I do not do graphic design, UX, mockups or wireframes. If you search for a WordPress designer in Edinburgh, you need a designer first, and then a developer for the second step. You or your designer provide the design as a Figma file or a wireframe. I turn it into a working, fast, accessible WordPress site: templates, editable blocks, responsive behaviour, forms and performance.
A design handed over with real content, states for hover and error, and mobile layouts saves the most time. If something in the design cannot be built accessibly, for example text over an image with low contrast, I tell you before I build it, with the specific screen.
The Edinburgh Festival Fringe Society reports an estimated 2,604,404 tickets issued for 3,893 shows across 301 venues in 2025, with the festival closing on 25 August (Edinburgh Festival Fringe). If you run a venue, a hotel, a restaurant or a shop in the city, your site meets that demand in August whether you planned for it or not.
Before August I freeze plugin updates and deployments, put full-page caching on public pages with exceptions for cart, checkout and booking forms, and test the booking path on a throttled mobile connection on staging. The result is a written release calendar: what is frozen, from which date, and who can deploy.
Cookie rules in the UK come from the Privacy and Electronic Communications Regulations (PECR). Section 112 of the Data (Use and Access) Act 2025 replaced regulation 6 and added Schedule A1 with exceptions to the consent rule (section 112). Legislation.gov.uk records section 112 as in force on 5 February 2026 under S.I. 2026/82.
For analytics, Schedule A1 paragraph 5 sets conditions all of which must be met: the sole purpose is statistics on how the service is used, with a view to making improvements; the data is shared only to help make those improvements; users get clear information; and users have a simple, free way to object (Schedule 12). Whether your analytics tool meets that depends on its data flows. I list what each script sends and where, so you or your data protection adviser can decide. Anything outside the exceptions, such as advertising pixels, loads only after consent.
For forms that collect personal data I keep the fields to what the purpose needs, write the data flow into the handover notes, and keep an admin change log. UK GDPR Article 33 gives a controller 72 hours from becoming aware of a breach to notify the regulator where notification is required (Article 33), so the log has to show who changed what and when. Legal bases and processor agreements are your decisions. I configure WordPress so those decisions can be carried out.
For a private firm, the UK frame is the Equality Act 2010. Section 29 bars a service provider from discriminating in how it provides a service and applies the reasonable adjustments duty to service providers (section 29).
Public sector bodies, and some charities that are mostly publicly funded or provide essential services, must meet WCAG 2.2 AA and publish an accessibility statement. Charities and other non-government organisations outside those criteria are exempt but keep the Equality Act duty (GOV.UK guidance). If you work for a university, a health body or a council in Scotland, I build to WCAG 2.2 AA and prepare the statement as a template your team completes.
In code that means semantic markup, labelled form fields, visible focus, keyboard-operable menus and contrast checks on the finished templates. I do not promise a certificate. An audit by an accessibility specialist is a separate service.
I invoice from Poland. HMRC’s manual says that when a UK business customer receives certain services from a non-UK supplier, the customer does not pay VAT to the supplier. It adds the VAT to its own VAT account as output tax and generally reclaims it as input tax, so no net tax is payable for a fully taxable business (HMRC, VATPOSS14100). Whether development work falls into the covered services is a question for your accountant.
A GOV.UK policy paper proposes that from 1 April 2027 the reverse charge applies only when the buying business is registered for VAT in the UK, and that suppliers charge UK VAT to unregistered business customers (GOV.UK policy paper). It describes a proposal, and I have not seen it enacted. Tell me at the start whether your business is VAT-registered, so the quote states the VAT treatment.
After launch, updates, backups and monitoring can move to WordPress maintenance in Edinburgh or the WordPress website maintenance page.
Are you a freelance WordPress developer or an agency? I am one person, a sole proprietorship in Gdynia, Poland. There is no account manager between you and the code. If a project needs several people working in parallel, I say so in the written scope instead of stretching one person across it.
Can you design the website as well as build it? No. I do not do graphic design, UX or mockups. You or your designer provide the design as a Figma file or a wireframe, and I build it as a working, fast, accessible WordPress site.
Do you build WooCommerce stores for Edinburgh businesses? Yes. Store builds sit on a separate page, WooCommerce developer in Edinburgh. Payment gateway, shipping and VAT rules are agreed in writing before the build, and your accountant confirms the tax settings.
How do we work across the time difference? Poland is one hour ahead of the UK. Everything runs by email and shared documents, so the difference rarely matters. I reply within 48 hours.
Send the current state of the site, the goal, any deadline such as the August festival season, and the design file if you have one through the contact form. I quote per scope after reading it.
Examples of my work.
Vectorsmartdata.net is a website created for VECTOR Group, a provider of advanced telemetry solutions enabling real-time data monitoring and management. As ...
The website wyposazenie-szkol.com was designed to comprehensively present the offer of educational facility supplies. The main goal of the site is to showcas...
Zafriko.pl is an advanced project in my WordPress developer portfolio that I had the opportunity to develop as part of creating a modern social and entertain...
Describe your project by e-mail. I reply within 48 hours.
Describe your projectWordPress 4.9 was "the calm before the storm." We analyze this pivotal moment in WP history that prepared the ground for the block editor. What changed since? How did the ecosystem evolve?
Compare the best WordPress plugins in 2026 for security, SEO, cache, backups, and image optimisation, with practical advice on what to install and what to avoid.
Gutenberg blocks, synced patterns, full site editing, custom templates, and block plugins for teams that want a cleaner WordPress editing system.
CrUX field-data audit with per-template LCP, INP, CLS attribution.
Core Web Vitals, caching, and faster delivery.
A free check of your site's public version, results on screen.
Stability, updates, and post-launch support.
Updates checked before release, with a report.
Migration to Astro, Next.js, and headless WordPress.
Audit, hardening, and incident risk reduction.

How to optimize Interaction to Next Paint (INP) on WordPress sites. Practical fixes for the newest Core Web Vital metric that directly impacts Google rankings.

Field versus lab, LCP, INP and CLS for WordPress in 2026. Google's green LCP is still 2.5 s in CrUX. 100/100 in Lighthouse is a lab target. Edge HTML, consent banners, checkout widgets.

How we took a slow WooCommerce site from score 45 to 100. A technical deep dive into Speculation Rules, AVIF, and Critical CSS in 2026.