Why Designers Should Embrace WordPress ![rw-book-cover](https://i0.wp.com/ivanovicmarko.com/wp-content/uploads/2025/10/wordpress-design.png?fit=1200%2C675&ssl=1) ## Metadata - Author: [[it's Marko.]] - Full Title: Why Designers Should Embrace WordPress - Category: #articles - Document Note: ```markdown --- tags: [WordPress, Design, OpenSource] author: it's Marko. source: ivanovicmarko.com reference: [https://ivanovicmarko.com/2025/10/01/wordpress-and-design/] date created: 2025-10-03 00:00 --- # 🏷️ Title: Why Designers Should Embrace WordPress ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - The author recounts shifting to WordPress after skepticism. - It matters because designers may hold dated perceptions. - Stakeholders include designers, agencies, Automattic, and WordPress.org. - Risks include oversimplifying complexity and ignoring developer needs. - Bottom line: WordPress now offers modern, flexible design workflows. ## 📖 Main Content - The author tried WordPress in 2012 and left unimpressed. - In 2022, joining Automattic changed their view. - They observed major UX and editor improvements with blocks. - They highlight cultural touches like WordPress and jazz releases. - They call designers to re-evaluate current capabilities. - Uncertainties: scope of improvements across complex builds; plugin quality variance. - Context: Gutenberg shifted editing to block-based design. See the WordPress project pages for background: Gutenberg and block editor (note: official docs may vary by release). ### 🗒️ Notes ### [H1] Designer perception changes after hands-on exposure > [!quote] [Why Designers Should Embrace WordPress](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) by [[it's Marko.]] via [[ivanovicmarko.com]]. Published 2025-10-01. Accessed 2025-10-03. > “WordPress was no longer the clunky tool I remembered from 2012.” Perception lag persists. Direct use updates beliefs. [view highlight](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) #xref #articleseed ID:rw_[MISSING] ### [H2] Block editor improves designer building experience > [!quote] [Why Designers Should Embrace WordPress](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) > “a system that let anyone create a website by simply adding blocks or editing themes with ease.” Blocks reduce dependency on rigid themes. Lowers designer friction. [view highlight](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) #xref ID:rw_[MISSING] ### [H3] Ongoing investment enhances editing experience > [!quote] [Why Designers Should Embrace WordPress](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) > “Behind the scenes, I also saw the amount of work going into improving the editing experience” Signals roadmap maturity and sustained UX focus. [view highlight](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) #xref #articleseed ID:rw_[MISSING] ### [H4] Cultural connection: WordPress names and jazz > [!quote] [Why Designers Should Embrace WordPress](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) > “the connection between WordPress and jazz.” Cultural elements can engage design audiences. [view highlight](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) #share ID:rw_[MISSING] ### [H5] Call for designer feedback on blockers > [!quote] [Why Designers Should Embrace WordPress](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) > “I’d like to invite you designers who believe WordPress isn’t for you to share the biggest reasons with me.” Feedback can refine onboarding and content. [view highlight](https://ivanovicmarko.com/2025/10/01/wordpress-and-design/) #articleseed #share ID:rw_[MISSING] ## 📚 References - [WordPress block editor overview](https://wordpress.org/documentation/article/wordpress-block-editor/) - [WordPress releases named after jazz musicians](https://wordpress.org/about/history/) - [Automattic company page](https://automattic.com/) - If any link above is inaccessible, use WordPress.org documentation search. ## 🗣️ Paraphrase - The author used WordPress again and found it transformed. - They urge designers to reassess WordPress with current tools. ## 📰 Newsletter - Designers, WordPress today feels modern and flexible. - Blocks, theme editing, and UX investments changed the game. - Share your blockers; we will route them to teams. - Resources: WordPress block editor, theme.json, Patterns Directory. ## ✅ Action Items #### DevRel - Publish a “Designer-first WordPress guide” — context/article #articleseed - Run office hours for design workflows — context/article #share - Build block-based starter templates — context/article #articleseed - Collect designer blockers via form — context/article #share #### OSPO - Document upstream contribution paths for designers — context/article #xref - Create licensing guide for design assets — context/article - Define review cadence for design contributions — context/article #### Community - Host “Design in WordPress” clinics — context/article - Publish mentorship pathways for designers — context/article - Report impact metrics quarterly — context/article #### WordPress - Design: expand design token guidance and examples. - Documentation: add designer personas and flows. - Training: produce FSE tutorials for designers. - Marketing: feature modern designer case studies. - Accessibility: include design-focused checklists. - Playground: add designer sandboxes with patterns. #### The WPCC - Programs: microgrants for designer tooling. - Projects: documentation sprints for design flows. - Funding experiments: matched grants for design education. ### FAIR - Policies: transparent funding for design contributions. - Artifacts: maintain scorecards for onboarding quality. ## 🧪 Hypotheses - Designers update opinions after trying the block editor. - Designer-focused onboarding increases adoption intent. - Cultural storytelling improves designer engagement rates. - Public feedback channels reduce perceived friction. ### 📊 Methodology - A/B test designer onboarding guides with surveys. - Run usability tests on theme editing tasks. - Track engagement before/after cultural storytelling posts. - Analyze feedback themes from intake forms. ### ❓ Questions - Which designer tasks still feel hard? - Where does theme.json confuse newcomers? - Which plugins block smooth design workflows? ### 🔮 Future Research - Map designer personas to WordPress tasks. - Benchmark WordPress vs. Webflow for designer flows. - Evaluate pattern libraries’ impact on build speed. ### 💡 Implications - Better designer onboarding can grow the ecosystem. - Funding design contributions improves UX quality. - Clear documentation reduces support load. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ~8–9 (approximate). #### 👀 Visual learners - Present: screenshots would help; add diagrams. - Improve: flowcharts for block layouts and patterns. #### 🔊 Aural learners - Present: none noted. - Improve: short audio walkthroughs and TTS. #### 🗣️ Verbal learners - Present: clear narrative and definitions implied. - Improve: glossary for blocks, patterns, templates. #### 🧩 Kinesthetic learners - Present: encourage trying WordPress directly. - Improve: guided labs in Playground. #### 🧠 Logical learners - Present: stepwise argument from experience. - Improve: decision trees for theme choices. #### 🧑‍🤝‍🧑 Social learners - Present: invitation to DM feedback. - Improve: moderated forums and cohorts. #### 🧘‍♀️ Solitary learners - Present: reflective narrative. - Improve: self-checklists for first builds. #### 🌿 Naturalistic learners - Present: none explicit. - Improve: lifecycle of site design assets. ### 📊 Accessibility Assessment #### Screen reader semantics - Pres - Summary: Discover how my journey with WordPress transformed from skepticism to appreciation, urging designers to explore its true potential. - URL: https://ivanovicmarko.com/2025/10/01/wordpress-and-design/ #### WordPress and design I first tried to build a portfolio with WordPress back in 2012. It didn’t really work for me at the time, so I moved on with my life. In the following years, I focused mainly on branding projects, with occasional website work for clients. For development, I always hired others to handle it. In design circles, WordPress was rarely a favorite tool. My own websites were usually custom-coded by friends, and later some of them helped with Webflow site building. Then, in 2022, while I was busy growing my design studio, something unexpected happened: I joined Automattic. A colleague, who had seen my work on Dribbble—approached me, introduced me to the company, and encouraged me to apply. At first, I was hesitant. My focus was still on building what I hoped would become the best branding studio in the world. But business had slowed down. After an incredible run in 2020 and 2021, the year 2022 brought almost 0 profit. So I gave it some thought. Eventually, I decided to give Automattic a chance, which meant giving WordPress another chance too. The transformation was immediate. WordPress was no longer the clunky tool I remembered from 2012. The conversations we designers had about it for years, simply didn’t match the reality. What I found was an improved interface, a much better building experience, and a system that let anyone create a website by simply adding blocks or editing themes with ease. Behind were the days of struggling with fixed themes that left designers stuck. Behind the scenes, I also saw the amount of work going into improving the editing experience—far beyond what I ever expected. The whole thing was, a shock. And then there were the small details that resonated with me, like the connection between WordPress and jazz. Something I’d never known, even though I love jazz. Slowly, I started to like WordPress. If I went back to 2016 and told my past self this, I wouldn’t believe it. I know many designers still feel the same today. ![A collage featuring album covers inspired by jazz musicians, showcasing various WordPress versions, with titles and artists like Rollins, Dorsey, Shirley, and Lionel. The design emphasizes the connection between jazz and WordPress, with a central black vinyl record.](https://i0.wp.com/ivanovicmarko.com/wp-content/uploads/2025/10/jazz.png?w=4560&ssl=1)A collage featuring album covers inspired by jazz musicians, showcasing various WordPress versions, with titles and artists like Rollins, Dorsey, Shirley, and Lionel. The design emphasizes the connection between jazz and WordPress, with a central black vinyl record. This should change. At the very least, designers should know what WordPress can actually do before dismissing it. That’s now part of my mission as someone working on the WordPress brand: to present WordPress in its true light, especially to designers. Beyond what Automattic already does, I will announce a personal side project dedicated to this goal. More about it soon! I won’t even talk about the open source aspect, community or global importance of WordPress. Those are things designers are aware of. Let’s see what we can do for you, a designer. Above all, I’d like to invite you designers who believe WordPress isn’t for you to share the biggest reasons with me. Feel free to send me a DM on [X](https://x.com/ivanovic_marco) or [LinkedIn](https://www.linkedin.com/in/ivanovic-marko/)., Why Designers Should Embrace WordPress, it's Marko., 01k6js9r9c0mfxh0vq18vcg5pv.