WordPress support in Florence for sites that actually publish
Sites with a lot of content, several authors and growing archives: updates that do not interrupt the editorial team, performance that holds, and the people writing put in a position to work on their own. Working office at Impact Hub.
The point
A site that publishes
wears out faster.
A ten-page brochure site can sit still for years without anyone noticing. A site publishing every week cannot: archives grow, editorial plugins pile up, images uploaded in a hurry get heavy, and at some point the admin panel becomes slow for exactly the people using it daily.
There is a timing question too: updates cannot happen whenever. If the team is closing a piece, a plugin breaking is a real problem, not a technical inconvenience.
We have run a WordPress course for the Treccani editorial team for three years, built around their workflow. It is the same point of view we bring to support: the site is somebody's working tool.
What it covers
What we look after,
once we take over.
Plans, hours and response times are on the ongoing support page.
Updates at the right time
Tested on a copy and pushed live in windows agreed with whoever publishes. No surprise work while you are closing something.
Performance with large archives
Slow queries, internal search that stops coping, images served larger than needed. Measured before and after, not judged by feel.
Security and access in order
The right role for each person, access removed for people who have left, known vulnerabilities closed. On sites with many authors it is the first thing to sort out.
Training for the editorial team
Half a day on your actual workflow is worth more than ten support tickets. We teach people to do for themselves the things that today become requests.
Why us
Developers,
not plugin installers.
What changes when the problem cannot be solved from the dashboard.
We read the code
If a function does not exist, we write it: twenty lines built for the job beat a plugin with fifty settings used at ten per cent.
The admin panel can be simplified
Unused fields removed, content types tidied, screens reduced to what the team actually uses. It is the quickest way to give editors their time back.
We tell you the cause
Every job closes with what it was and why it happened. If the structure no longer holds, we write that instead of patching indefinitely.
Nothing held hostage
Access, hosting and domain stay yours, and content can be exported whenever you want. Changing supplier should cost an email.
Where we are
The Florence office.
Via Panciatichi 10/14
50141 Firenze (FI)
We can meet in Via Panciatichi, or on a call: half an hour is enough to see what state the site is in and what it really needs.
FAQ
Before you ask.
Yes, it is the most common situation. We start with a check of versions, plugins, backups and security: it is free and tells us both whether it makes sense to work together.
Yes, and it is usually the fastest return of anything we do. The programme is not off the shelf: it is built around your workflow, from routine publishing to the cases that come up twice a year and that nobody remembers how to handle.
We measure instead of guessing: find what is consuming time — queries, images, plugins, hosting — and work on what weighs most. You get the before and after figures.
We audit against the WCAG guidelines and fix what can be corrected on the existing site, telling you clearly what would instead need deeper work.
That can be done as a single intervention: we look, quote it, and fix it.
Who updates your site today?
If the answer is "whenever we remember", send us the address: we will check what state it is in and tell you what is needed, with no obligation.
ISO 9001:2015 certified
Written requirements, tracked changes, a defined path for every issue.
Benefit Corporation
Goals written into the bylaws, an impact report every year.
Listed on MePA
The Italian public sector e-procurement marketplace.
