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?
My name is Mariusz Szatkowski. I build and extend WordPress sites from Gdynia, on the Polish coast, and have worked with WordPress since 2006. If you searched for an Italian freelance WordPress developer, you should know up front that I am not Italian. I am a Polish freelancer, I work remotely, and with companies in Turin I write in English. This page explains what that arrangement covers, which Italian rules a WordPress site in Turin has to follow, and what you send me to get a written estimate.
The work divides cleanly. I handle the WordPress side: theme or block implementation from your layout, custom post types and fields, forms, integrations, the consent setup, multilingual structure, speed and the move to your hosting. You or the people you already trust handle the words: Italian page copy, the privacy policy, the cookie policy, terms of sale and any English or French versions. I do not write legal texts and I do not translate into Italian. I put the approved texts in the right place and make the site behave the way they describe.
Graphic design is not part of what I deliver either. The layout comes from you, from your designer or as a filled-in spreadsheet where you mark which elements go on which view. I turn that into a working, responsive WordPress site.
All communication is written: the brief, my questions, the scope, the staging review, the acceptance list. That suits a remote arrangement across two languages, because every decision has a record that a translator or a colleague in your office can read later.
Italy implemented the EU e-commerce directive with Decreto Legislativo 9 aprile 2003, n. 70. Its article 7 obliges the provider of an online service to make certain information easy, direct and permanent to reach. On a WordPress site that turns into a short list I check before launch:
“Permanent” is the word that matters for a build. A company number tucked into one About page does not meet it. I place these details in the site footer, which WordPress renders on every template, and repeat them on a legal notice page. In a block theme the footer is a template part, so one edit updates every view and a later redesign cannot quietly drop it.
The Italian data protection authority, the Garante per la protezione dei dati personali, adopted its cookie and tracking guidelines on 10 June 2021. Several points translate directly into how the consent banner on a WordPress site has to work:
In practice I set up a consent plugin so that marketing tags, embedded videos and third-party fonts stay blocked until the visitor agrees, and I test that on staging with the browser’s network panel open. Which tools you use and how you word the banner is your decision, ideally with your privacy consultant. My part is a site that keeps its promise.
Italy transposed the European Accessibility Act, Directive (EU) 2019/882, with Decreto Legislativo 27 maggio 2022, n. 82. Article 1 makes it apply to products and services placed on the market from 28 June 2025, and the list of services in article 1, paragraph 3 includes e-commerce services (letter f). Paragraph 5 leaves out some older content: pre-recorded audio and video and office files published before 28 June 2025, and archived content not updated after that date.
The AgID FAQ adds the practical points:
For a Turin company that sells online and is above the microenterprise size, accessibility belongs in the build from the first template. When I implement a layout I keep the parts that decide whether a visitor can use the shop without a mouse: real headings, labelled form fields, visible keyboard focus, menus that open with the keyboard, images with text alternatives, and a checkout that reports errors in words. If the layout itself causes a problem, such as light grey text on white, I point it out in writing before I build it, because the visual design stays yours.
The Agenzia delle Entrate states in its electronic invoicing FAQ that invoices issued to VAT-registered businesses (B2B) must be electronic via the Sistema di Interscambio, and that the SdI delivers each invoice to the address it carries: a PEC address or a recipient code (codice destinatario).
WordPress is not an invoicing system, and I do not try to make it one. What a WooCommerce shop for Italian business buyers needs is the right data at checkout: company name, partita IVA, codice fiscale where relevant, and the PEC or codice destinatario. I add those fields, validate their format, and pass the order to the invoicing software or accountant you already use. The details of shop builds are on the WooCommerce developer page for Turin.
Two payment plugins come up often for Italian shops, both on wordpress.org: Satispay for WooCommerce, published by Satispay, and Nexi XPay, published by Nexi Payments, which needs the bcmath PHP extension on the server. Whether either fits depends on your contract with the provider, so I ask before I install anything.

Photo: Gabridelca, CC BY-SA 3.0, Wikimedia Commons.
Four local institutions are worth knowing if your website is part of a wider digital plan. None of them is a reason to hire me; they are places where a Turin company can get support that a WordPress developer does not give.
For speed I work to Google’s published thresholds: LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1, as described on web.dev. I measure the live site against them after launch rather than promising a score in advance.
Use this with any developer, including me.
| Check | Where to look |
|---|---|
| Company name, sede legale, email, REA and partita IVA visible on every page | Site footer, then a legal notice page |
| Prices say whether VAT and delivery are included | Product and cart pages |
| Cookie banner has an X that closes it without accepting | Front page in a private window |
| No marketing tags load before consent | Browser network panel, before clicking anything |
| Refusal is remembered and not asked again at once | Reload after refusing |
| Analytics either consented or configured with masked IP and aggregate use | Analytics settings |
| Shop pages and checkout usable with keyboard only | Tab through a full order |
| B2B checkout collects PEC or codice destinatario | Checkout form with a company buyer |
| Italian copy and legal texts approved by you, not by the developer | Your own sign-off |
No. I am Polish, based in Gdynia, and I work remotely for clients abroad. With Turin companies I write in English. Italian page copy, privacy texts and translations come from you, your translator or your consultant, and I put them into WordPress.
Article 7 of D.Lgs. 70/2003 lists them: name or company name, registered office, contact details including email, the REA or company register number, the VAT number, and prices that state whether tax and delivery are included. I place them in the footer and on a legal page so they appear on every view.
No. Under the Garante guidelines of 10 June 2021 the banner needs an X that closes it and keeps only technical cookies, scrolling never counts as consent, and a cookie wall is unlawful unless the visitor gets an equivalent alternative without consenting.
D.Lgs. 82/2022 covers e-commerce services placed on the market from 28 June 2025. According to AgID, which supervises services, it does not apply to microenterprises that provide services: fewer than ten employees and annual turnover or balance sheet total of no more than two million euros. A brochure site that sells nothing online is outside the e-commerce category.
Not by itself. Invoices between VAT-registered businesses in Italy are electronic and travel through the Sistema di Interscambio to the PEC address or recipient code on the invoice. A shop usually passes order data to the invoicing software you already use, and that software talks to the SdI.
The address of the current site if there is one, the goal, the deadline, the layout for each view, the Italian content, and access to hosting and the domain. With that I can write a scope.
If an English-speaking developer in Poland works for you, write to me through the contact page. Tell me the site address or that there is none yet, what the site should achieve, your deadline, and what it runs on today. I read every message myself, reply in writing with my questions, and then send a written estimate with scope and assumptions. That first estimate costs you nothing. More about how I approach WordPress builds in general is on the WordPress developer page.
Examples of my work.
The pepegotti.com website is a modern platform dedicated to furniture distribution, combining clear design with advanced functionalities tailored for both in...
pluginfinance.com is a modern, highly scalable WordPress-based service dedicated to showcasing and distributing financial plugins. The project was designed w...
Radio.friko.pl is an internet radio station that operated between 2005 and 2010 as part of the Friko.pl platform, offering users access to music streaming, l...
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.