Profiles

Bio

Polymath by nature, my approach to design is to bring together a holistic perspective to the products I design. My take on design blends with psychology, technology, and business strategy, to help craft something that truly helps user achieve their goals. I’ve a very transparent and open approach to work, and I enjoy working with people to a common, shared goal.

WordPress Origin Story

Around 2003 I started working on a content management system called phpGolem. I was disappointed by the state of CMS options at the time, and I had an idea of a core extension engine where everything was a module on top: phpGolem. That same year, Matt Mullenweg and Mike Little forked b2 (see: “The Great Renaming”, commit 601) and released WordPress 0.70. Clearly I wasn’t the only person feeling CMS options weren’t good enough.

A friend of mine then suggested to have a look on how WordPress was handling filters, as it was a good model. I did, and stared discovering WordPress. In December 2004 phpGolem released 0.4 beta, while WordPress reached 1.2. I was really proud about phpGolem, it had a lot of good things going on, but one thing that I missed at the time was the community. WordPress already understood how important that was.

Years later, when I co-founded Baker Framework, I didn’t do the same error, and we managed to create a lively open source community around it. But that’s another story.

Over time WordPress became so good that phpGolem with me as single developer couldn’t compete in any way anymore. By then however I had studies ins and outs of WordPress, so I wrote an exporter and switched everything to WordPress. The rest is history.

In 2008 I spoke at the first Italian WordCamp with a presentation about “WordPress as a CMS”, and that’s where I met for the first time Matt.

Later I worked for 8 years in Automattic, before leaving in 2021. It’s been a great journey to see it grow from 200 to 1,500 people, but even more because it allowed me to dedicate more time to the WordPress Community. In particular, I helped work with the Customizer and later I helped lay the foundation of Gutenberg with the “Parrot” concept aggregating the input of the many designers in the community.

Badges

CODE
4 badges
Core Contributor '15 Design Contributor '17 Design Team '19 Meta Contributor '15
COMMUNITY
1 badge
WordCamp Speaker '19
PRACTICE
1 badge
Accessibility Contributor '21
POLYGLOTS
1 badge
Translation Editor '15

Current Job

Sr Director of Product and Design
Present

Recent impact

Score weights high-impact work (commits, releases, approved translations, props) at 3x routine activity.

Last 30 days
0contributions
high0
medium0
score0
Last 90 days
0contributions
high0
medium0
score0
Last 12 months
0contributions
high0
medium0
score0

Team focus

Across 6 teams, with no team-attributable contributions in the last 365 days

WordPress releases

Contributed to 9 releases
  • 5.7
  • 5.6
  • 5.5
  • 5.2
  • 5.0
  • 4.9
  • 4.7
  • 4.5
  • 4.2

Contributions

Type
November 2020
Nov 19 Thu · 12:53
Meta med
Wrote a comment on the post Discussion: align the WordPress release cycle with the industry standard, on the site Make WordPress Core:
Yes. It's clearer, communicates better, and provides more structure while reducing complexity.
July 2020
Jul 10 Fri · 11:18
Meta med
Wrote a comment on the post WP Notify – next steps, on the site Make WordPress Core:
I'm unlikely to have the time to lead the design here, but I'd be more…
Jul 10 Fri · 11:16
Meta med
Wrote a comment on the post WP Notify – next steps, on the site Make WordPress Core:
We should have everything in the open from the start. If we have a GitHub…
Jul 10 Fri · 11:14
Meta med
Wrote a comment on the post WP Notify – next steps, on the site Make WordPress Core:
That's the doc linked at the top of the post, so yes. ;) I'm not…
Jul 07 Tue · 17:47
Core high
Mentioned in [48390] on WordPress SVN:
Upgrade/install: Allow plugin and theme updates from a uploaded .zip file.
March 2020
Mar 25 Wed · 18:43
Meta med
Wrote a comment on the post WP Notify weekly meeting suspended, call for proposals for new meeting times or new meeting hosts., on the site Make WordPress Core:
I think we can async the document work, and then publish the results openly for…
January 2020
Jan 20 Mon · 14:35
Meta med
Wrote a comment on the post WP Notify Meeting Recap – January 13 2020, on the site Make WordPress Core:
We added your list (adapted as above) to the Requirements Documents as the starting point…
Jan 15 Wed · 13:58
Meta med
Wrote a comment on the post WP Notify Meeting Recap – January 13 2020, on the site Make WordPress Core:
Ah yes, I checked now the document and the distinction you make "Results" and "Informative"…
Jan 15 Wed · 13:57
Meta med
Wrote a comment on the post WP Notify Meeting Recap – January 13 2020, on the site Make WordPress Core:
This isn’t really a question – is it? Yet, you gave a good answer, so…
Jan 15 Wed · 13:48
Meta med
Wrote a comment on the post WP Notify Meeting Recap – January 13 2020, on the site Make WordPress Core:
I'd note that there aren't just the two possibilities of "interim solution" and "permanent solution"…

Translations

1 locale
it_IT Italiano (Italian) Plugins Translation Editor