WordPress.org Putting the Boot to Premium Theme Developers  Full Document Contents/Articles/WordPress.org Putting the Boot to Premium Theme Developers.md, WordPress.org Putting the Boot to Premium Theme Developers, justintadlock.com. > [!note]+ Document Notes > tags: > - #WordPress > - #PremiumThemes > - #AutomatticGovernance > Author: Justin Tadlock > Source: Justin Tadlock's Blog > Reference: [https://justintadlock.com/archives/2008/12/11/automattic-putting-the-boot-to-premium-theme-developers](https://justintadlock.com/archives/2008/12/11/automattic-putting-the-boot-to-premium-theme-developers) > date created: 2024-10-23 12:45 > > # Title: "Automattic's Shift: Impact on Premium Theme Developers" > <!-- deep-read:sections start --> ## 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) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ## 📝 Summary: This article discusses Automattic's stance on premium themes, raising concerns about the future of independent premium theme developers in the WordPress ecosystem. Justin Tadlock shares his perspective on how Automattic's decisions may lead to a less open, more restricted market for developers, potentially putting independent theme creators at a disadvantage compared to larger, Automattic-backed services. ## 📖 Main Content: The article focuses on Automattic’s move to limit or restrict the sale of premium themes through certain channels, raising concerns that this decision could harm independent developers who rely on these sales. Tadlock questions whether this move aligns with WordPress’s open-source ethos, suggesting that it could create an uneven playing field where Automattic-backed products receive preferential treatment over those created by smaller developers. The potential implications of this change could affect theme developers’ ability to compete fairly in the marketplace. ### 🗒️ Notes - **Automattic's Control Over Theme Market**: - Automattic’s stance on premium themes may restrict developers from selling themes on WordPress.org, pushing them to other platforms. - This raises concerns about Automattic’s growing control over the WordPress ecosystem. - **Impact on Independent Developers**: - Small theme developers, who depend on premium theme sales, may struggle to compete if Automattic-backed themes are prioritized or given better visibility. - The policy could lead to a more closed, restrictive ecosystem, making it harder for independent developers to thrive. - **Ethical and Governance Implications**: - Tadlock raises the question of whether Automattic’s actions align with the principles of open-source collaboration that WordPress was built on. - Concerns are expressed about the direction WordPress.org is taking and its long-term effects on developer autonomy. ## 📖 References: - [Automattic's Premium Theme Policy](https://justintadlock.com/archives/2008/12/11/automattic-putting-the-boot-to-premium-theme-developers) ## 🗣️ Paraphrase: 1. Tadlock argues that Automattic's decision to restrict premium theme sales on certain platforms may disproportionately impact independent theme developers. He believes this move will limit competition, making it difficult for smaller developers to sell their products within the WordPress ecosystem. 2. The article critiques Automattic for potentially shifting away from the open-source principles that WordPress was built on. By exerting more control over the premium theme market, Automattic risks alienating smaller developers who rely on equal access to the marketplace. ## 📰 Newsletter: **Automattic's Control Over Premium Themes Sparks Concerns** Justin Tadlock has raised important questions about Automattic's recent policy changes regarding premium themes. Independent theme developers are concerned that the new restrictions will limit their ability to sell themes on WordPress.org, giving Automattic-backed products an unfair advantage. As WordPress grows, how will this shift affect the open-source ethos it was built on? Find out more about the future of premium themes and what it means for developers. [Read more here](https://justintadlock.com/archives/2008/12/11/automattic-putting-the-boot-to-premium-theme-developers). ## ✅ Action Items: 1. Review Automattic's policies on premium themes and assess how these changes may affect your theme sales or development strategy. 2. Explore alternative platforms to market premium themes if WordPress.org becomes less accessible for independent developers. 3. Engage with the WordPress community to discuss potential solutions or adjustments to ensure fairness in the marketplace. ## 🧪 Hypotheses: - If Automattic continues to limit premium theme sales, independent developers may see a significant reduction in visibility, leading to fewer sales and reduced participation in the WordPress ecosystem. - The broader developer community may shift to alternative marketplaces or platforms if restrictions become more stringent, leading to a fragmented theme market. ### 📊 Methodology: To investigate the impact of these policy changes, conduct a survey among premium theme developers to gauge how these restrictions have affected their sales. Track market trends over time to assess whether independent developers are migrating to other platforms or markets. ### ❓ Questions: - How will Automattic’s control over premium themes affect the long-term sustainability of independent developers in the WordPress ecosystem? - Could these changes lead to a more closed and commercialized WordPress environment, moving away from its open-source roots? ### 🔮 Future Research: - Study how policy changes in open-source platforms, like WordPress, impact developer participation and innovation. - Investigate the long-term consequences of centralizing control within a single organization, particularly in open-source communities. ### 💡 Implications: If Automattic’s policies restrict competition in the theme market, we may see a consolidation of power within the WordPress ecosystem. This could discourage independent developers from contributing, leading to a loss of diversity in the types of themes and products available to users. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: No visual aids are provided in the article. - **Improve**: Add diagrams or charts showing market trends and the effects of policy changes on developers. 2. **Aural Learners (Auditory-Musical)**: - **Present**: None. - **Improve**: Include an audio summary or podcast discussing the topic for auditory learners. 3. **Verbal Learners (Linguistic)**: - **Present**: The article uses clear and precise language to explain complex topics. - **Improve**: Incorporate more real-life examples or analogies to enhance understanding. 4. **Physical Learners (Kinesthetic)**: - **Present**: None. - **Improve**: Suggest interactive activities, such as community forums or discussions, where readers can actively participate. 5. **Logical Learners (Mathematical)**: - **Present**: The article follows a logical progression of arguments. - **Improve**: Add data points or statistics to further appeal to logical learners. 6. **Social Learners (Interpersonal)**: - **Present**: None. - **Improve**: Encourage group discussions or peer collaboration on how to adapt to the changes in premium theme policies. 7. **Solitary Learners (Intrapersonal)**: - **Present**: The article is suitable for reflection. - **Improve**: Include personal reflection prompts to help readers think critically about how the changes affect their work. 8. **Naturalistic Learners**: - **Present**: No references to nature or environmental concepts. - **Improve**: Use analogies comparing open-source ecosystems to natural ecosystems to engage naturalistic learners. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure that all links and images include descriptive alt-text for screen reader accessibility. - **Keyboard Navigation**: Verify that the website supports full keyboard navigation for all users. - **Contrast and Readability**: Use high-contrast colors and ensure the text is easy to read for individuals with visual impairments. ### 🌍 DEIB Assessment: - **Cultural Relevance**: The article does not address diverse cultural perspectives. - **Inclusive Language**: The language is neutral but could benefit from more inclusive terms to ensure broader accessibility. - **Representation**: No mention of underrepresented groups in the WordPress community. - **Psychological Safety**: Ensure that content is presented in a way that welcomes diverse opinions and fosters an inclusive environment. ### ✅ Logical Validity: - **Sound Deductive Reasoning**: The article logically follows from its premises, providing well-supported arguments about the potential risks for independent developers. - **Consistent Analogies**: The article draws appropriate comparisons between open-source governance and marketplace fairness. - **Suggestions**: Include more empirical evidence, such as developer testimonials or sales data, to strengthen the argument. ### 🔍 SEO Evaluation: 1. **Keywords**: "Automattic premium themes," "WordPress theme market," and "independent developers" are effectively used. 2. **Meta Description**: Add a concise meta description to improve search engine visibility. 3. **Title Tag**: The title is optimized but could be more concise for better readability. 4. **Internal Links**: Include internal links to related discussions about premium theme sales. 5. **External Links**: The article references external sources, but more authoritative links could be added. ## 🎯 Conclusion: Automattic's policy changes surrounding premium themes may have a profound impact on independent developers, potentially limiting their ability to compete in the WordPress ecosystem. The article raises important ethical and market-related questions about how these changes align with WordPress's open-source values and what the future holds for smaller developers. <!-- deep-read:sections end --> ## Highlights - The [about page](http://wordpress.org/extend/themes/about) of the theme directory has been updated with some new information: > All themes are subject to review. Themes for sites that support “premium” (non-GPL or compatible) themes will not be approved. ([View Highlight](https://read.readwise.io/read/01jax6agknmqpge34dspbwze0y)) - these 200 themes were pulled overnight with no warning at all. It just happened. Theme authors received a one-line email with nearly no explanation. I’m guessing that means a loss of all the statistics that were recorded as well. ([View Highlight](https://read.readwise.io/read/01jax6b2rj3rdatwg0vtdj5pzt)) - The other day I noticed a ton of bad stuff had snuck in like lots of spammy SEO links, themes whose sites said you couldn’t modify them (which is a violation of the GPL), etc. Exactly the sort of stuff the theme directory was meant to avoid. ([View Highlight](https://read.readwise.io/read/01jax6bpcq7yt9d87d1vqq19t9)) - Revolution ad now on theme directory I have no ill will toward Brian Gardner and his business, but apparently RevolutionTwo has an ad on the [theme directory](http://wordpress.org/extend/themes) now. This was pointed out in the comments below. Here’s a [screenshot of the ad](https://justintadlock.com/user/media/2008/12/revolution-ad-wordpress.png). I’m not sure how all this plays into the grander scheme of things, but it is an interesting thing to note. It has been labeled under “Paid Themes”, yet RevolutionTwo is an open-source project (with paid support services) ([View Highlight](https://read.readwise.io/read/01jax6cahxwrp61xqkdtpgmes6))