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, one developer working as a sole trader (JDG) from Gdynia in Poland. I build WordPress sites and WooCommerce shops for businesses in Glasgow and across the UK, remotely and in writing. There is no UK office and no agency behind the page. You write to me, and I write back.
Two kinds of project make up most of the work:
I also take over an existing install that has stalled: a theme nobody can update, a plugin pile that breaks on every release, a shop that needs a payment provider added. For recurring updates after launch see WordPress website maintenance. For the shop side in more depth see WooCommerce developer.
No. Some people search for “WordPress web design Glasgow” and expect layouts, logos and mockups. I do not provide graphic design, wireframes or UX design. The design comes from you or your designer, as Figma files, PDFs or a marked-up wireframe. I build from the client’s design: I turn it into a responsive WordPress theme, check it on real devices and tell you in writing where a design cannot work in a browser as drawn.
If you have no design yet, the sensible order is to get one first, then send me the files with the brief. A build estimated from finished designs is more accurate than one guessed from a description.
A Glasgow business that gets a site built by a supplier abroad still carries the legal duties as the site owner. These are the items I put on the acceptance list. I am a developer, not a solicitor, so they are checks on the build, not legal advice. Each one is read from the legislation text.
If I handle personal data for you, for example customer records in a shop or form submissions on a staging copy, UK GDPR article 28 applies. It says processing by a processor is governed by a contract that sets out the subject matter and duration, the nature and purpose, the types of personal data and data subjects, and the controller’s obligations and rights. The contract must also bind the processor to act only on your written instructions, keep staff under confidentiality, apply the article 32 security measures, follow the rules on sub-processors, delete or return the data when the service ends, and allow audits.
I give you that terms list in writing before I touch real customer data.
Article 33 gives the controller, which is you, 72 hours after becoming aware of a breach to notify the regulator, unless the breach is unlikely to risk people’s rights and freedoms. Since 30 September 2026 that regulator is the Information Commission, which took over from the Information Commissioner under the Data (Use and Access) Act 2025. The processor must tell the controller without undue delay. For a site this means two practical things: access logs and backups exist before anything goes wrong, and you know who tells whom the same day I find a problem.
Regulation 6 of the Privacy and Electronic Communications Regulations 2003 forbids storing information on a visitor’s device, or gaining access to it, except as Schedule A1 allows. Schedule A1 sets two conditions: the visitor receives clear and comprehensive information about the purpose, and gives consent. It exempts storage that is strictly necessary for a service the visitor requested. On a build this decides what loads before consent: analytics and marketing scripts wait for the choice, a basket cookie does not.
Regulation 6 of the Electronic Commerce (EC Directive) Regulations 2002 lists what a service provider must make easily, directly and permanently accessible: name, geographic address, contact details including an email address, trade register details where applicable, a VAT number where VAT is charged, and prices stated clearly, including whether they include tax and delivery costs. The footer and the legal pages of a Glasgow site carry these.
For a WooCommerce shop selling to consumers at a distance, the 2013 Regulations drive several pieces of the build. Regulation 13 requires a cancellation form to be given or made available where a right to cancel exists. Regulation 29 gives the consumer the right to cancel a distance contract during the cancellation period. Under regulation 30(3), for a sales contract of goods the period ends 14 days after the day the goods come into the consumer’s physical possession. The order emails, the account area and the returns page have to show those terms, so I build them in rather than add them the week before launch.
GOV.UK states that the Equality Act 2010 makes it unlawful to discriminate because of a protected characteristic, that disability is one of them, and that the protection applies to people “as a consumer”. The page I read does not set a technical standard for websites, so I do not claim one. I build with semantic markup, keyboard operation, visible focus states and text alternatives, and I test the checkout by keyboard, because a form that cannot be completed is the commonest way a shop shuts people out.
WordPress.org lists 7.1.4 of 28 October 2026 as the latest release and states that only the most recent release in the 7.1 series is safe to use. A site that stays on an older point release is running software the project itself does not call safe, which is why updates are part of any engagement that continues past launch.
For shops, WooCommerce documents High-Performance Order Storage as a solution that keeps order data in dedicated custom tables instead of the posts and postmeta tables, enabled by default for new installations since WooCommerce 8.2. On a new Glasgow shop I start with it on, and I check each order-related plugin for compatibility before it goes into the build.
Pricing is individual and follows the agreed scope. I do not hold calls or meetings; the brief, the questions and the decisions all live in writing, so nothing depends on anyone’s memory of a conversation. Working hours differ from a Glasgow office, which is why the 48 hour written reply is the commitment, not a same-day answer.
Yes. Design, mockups and wireframes come from you or your designer. I build them into a responsive WordPress theme or WooCommerce shop and do not provide graphic design.
Yes. A shop selling to UK consumers has to follow the Consumer Contracts Regulations 2013, so the cancellation information and the 14 day period for goods are part of the scope.
If I handle personal data on your behalf, UK GDPR article 28 requires a written contract that sets out the terms of the processing. I provide the terms list before I work with real customer data.
No to both. I am one developer, a sole trader based in Gdynia, Poland. I work remotely and in writing.
Send a written brief through the contact form. I reply in writing within 48 hours.
Examples of my work.
Ilovehair.pl is an e-commerce store based on the WordPress platform, dedicated to the sale of professional hairdressing products by Hair Saloon Products. As ...
jpg.pl is an advanced hosting platform designed for secure storage, management, and distribution of images. The service is aimed at both individual users and...
kochamruch.pl is a website for a community focused on movement and physical activity, with content publishing and stable technical foundations.
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.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Stores, checkout flow, and sales logic.
Stability, updates, and post-launch support.
What the monthly care fee covers and what changes it.
Business process automation around WordPress and company systems.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.

How to start as a WordPress developer in 2026. Local environment, theme and plugin development, REST API and headless paths, security and Core Web Vitals. A practitioner playbook that does not waste your first month.

WordPress 7.0 with AI Client vs Astro 6 after Cloudflare acquisition. Speed, cost, SEO and security comparison. My take after 20 years as a WP developer - when to migrate and when to stay.

WordPress 7.0 with AI Client against Astro 7 with the Rust compiler and Vite 8. Speed, cost, SEO and security compared, plus the real bill for my own Astro 6 to 7 migration.