Category: WordPress

WordPress is a content management system (CMS) powered by PHP, MySQL and JavaScript. WordPress is the world’s leading system to create websites and blogs. Currently, approximately 38% of all the content on the web was built with WordPress.

Need more? Design Rush has compiled a list of the Top WordPress Developers Of 2020 according to Design Rush.

  • Alt Text: Enhancing SEO and Accessibility in 2025

    Alt Text: Enhancing SEO and Accessibility in 2025

    In today’s digital landscape, where visuals dominate content strategy and user experience, a seemingly minor element continues to play an outsized role in both search engine performance and inclusive web design. Alt text—those concise descriptions attached to images across the web—remains one of the most powerful yet underutilized tools in a digital marketer’s arsenal.

    For website owners, content creators, and SEO professionals looking to maximize their online presence while creating truly inclusive digital experiences, understanding the multifaceted value of alt text has never been more important. Let’s dive into why alt text matters more than ever in 2025, and how you can leverage it for better rankings and broader audience reach.

    What Exactly Is Alt Text?

    Before exploring the benefits, let’s clarify what alt text (alternative text) actually is. Alt text is HTML attribute code that describes the appearance and function of images on a webpage. This descriptive text appears in place of images when they fail to load and is read by screen readers for visually impaired users.

    A simple example of alt text in HTML looks like this:

    html
    <img src="red-running-shoes.jpg" alt="Red Nike running shoes with reflective laces on a wooden surface">

    While the code itself is straightforward, crafting effective alt text requires thoughtfulness, precision, and an understanding of both user needs and search engine priorities.

    The Dual Impact: SEO Benefits of Alt Text

    Improving Image Search Visibility

    Search engines have become increasingly sophisticated in understanding visual content, but they still rely heavily on textual cues to interpret and rank images. Well-crafted alt text serves as a bridge between your visual content and search algorithms, significantly improving your chances of appearing in image search results.

    Recent statistics from SearchEngine Journal reveal that image search accounts for nearly 27% of all search queries across major platforms. This represents a massive opportunity for websites that optimize their visual content properly.

    Contextual Relevance Signals

    Alt text doesn’t just help your images rank—it contributes to how search engines understand your overall content. By providing additional context through image descriptions, you reinforce the topical relevance of your page, potentially boosting its position in organic search results.

    Google’s algorithms are increasingly focused on understanding content in context. When your alt text aligns with your page’s primary keywords and subject matter, it sends a powerful signal that your content comprehensively addresses the topic at hand.

    Core Web Vitals & User Experience Signals

    In 2025, Google’s emphasis on page experience metrics continues to influence rankings. Accessibility features like alt text factor into how search engines evaluate your site’s overall user experience. As search algorithms evolve to prioritize truly user-friendly websites, implementing proper alt text becomes not just good practice but a competitive necessity.

    Recent updates to Google’s ranking systems have placed greater emphasis on sites that follow WCAG (Web Content Accessibility Guidelines) standards, with alt text implementation being a fundamental requirement.

    Beyond SEO: The Human Impact of Alt Text

    Creating Truly Inclusive Web Experiences

    For the estimated 285 million people worldwide with visual impairments, alt text isn’t a technical SEO consideration—it’s the difference between accessing information and being excluded from it entirely.

    Screen reading technology relies on alt text to convey image content to users who cannot see it. When a visually impaired user encounters an image without alt text, their screen reader might simply announce “image” or read out the file name, providing little to no useful information about what the image contains.

    Consider this real-world scenario: An online shopping site displays product photos without alt text. A visually impaired shopper cannot determine what the products look like, severely limiting their ability to make informed purchasing decisions. This represents not just a single missed sale, but potential customer loss and brand damage.

    Legal Compliance and Brand Reputation

    Accessibility isn’t just ethically important—it’s increasingly becoming a legal requirement. Companies across industries have faced litigation for websites that fail to meet accessibility standards, including missing alt text. In the United States, ADA (Americans with Disabilities Act) compliance for websites has become a significant concern for businesses of all sizes.

    Beyond avoiding legal complications, brands that prioritize accessibility demonstrate their commitment to serving all users equally. This inclusive approach can significantly enhance brand perception and loyalty, particularly among the disability community and their allies—a market segment with substantial purchasing power often overlooked by competitors.

    Crafting Effective Alt Text: Best Practices for 2025

    Be Descriptive But Concise

    The ideal alt text provides enough detail to convey the image’s purpose and content without overwhelming the user. While screen readers can handle longer descriptions, most experts recommend keeping alt text under 125 characters to ensure it remains digestible.

    Poor example: “Image1.jpg” Better example: “Woman in business attire smiling while typing on laptop in a bright office setting”

    Include Keywords Strategically

    While incorporating relevant keywords into your alt text can boost SEO value, forcing keywords unnaturally can harm user experience and potentially trigger search engine penalties. The key is natural integration that serves both search algorithms and human users.

    Poor example: “SEO services SEO agency best SEO company marketing SEO” Better example: “Digital marketing professional analyzing SEO performance metrics on computer screen”

    Context Matters

    The most effective alt text considers the image’s role in the surrounding content. Is the image decorative, informative, or functional? Does it contain text that should be conveyed? These contextual factors should guide your approach.

    Poor example: “Chart” Better example: “Bar graph showing monthly website traffic growth of 45% from January to June 2025”

    Avoid Redundancy

    If the information in your alt text is already clearly stated in the surrounding content, consider using a more concise description or, in rare cases where the image is purely decorative, an empty alt attribute (alt=””) to prevent screen readers from providing unnecessary repetition.

    The Technical Side: Implementation Challenges and Solutions

    Content Management System Integration

    Most modern CMS platforms like WordPress, Shopify, and Wix provide built-in fields for adding alt text to images. However, ensuring consistent implementation across large sites remains challenging. Site audits using tools like Screaming Frog SEO Spider can help identify images missing alt text.

    Legacy Content Management

    For established websites with thousands of existing images, retroactively adding alt text can seem daunting. Prioritizing high-traffic pages and gradually working through your image library makes this task more manageable. Additionally, batch updating tools are available for many platforms.

    Automating Alt Text Creation with AI Tools

    As websites scale and content production accelerates, manually writing alt text for every image becomes increasingly challenging. This is where specialized tools like WP Descriptor come into play, offering automated solutions that save time while maintaining quality.

    WP Descriptor uses advanced AI to analyze image content and generate accurate, contextually appropriate alt text automatically. For busy content teams and large-scale websites, this automation ensures no image goes without proper description, maintaining both accessibility standards and SEO advantages without creating workflow bottlenecks.

    Future-Proofing: Alt Text in an Evolving Digital Landscape

    Voice Search Optimization

    As voice search continues to grow in popularity, the descriptive nature of good alt text becomes even more valuable. Voice search queries tend to be more conversational and question-based than typed searches, and comprehensive image descriptions can help your content appear in these results.

    AI and Machine Learning Developments

    While Google and other search engines are improving their ability to understand images without explicit text descriptions, alt text remains crucial for providing context and nuance that even advanced AI might miss. Your human-crafted descriptions often capture subtleties and brand-specific details that automated systems might overlook.

    Multimodal Search Evolution

    As search engines move toward multimodal experiences that combine text, images, voice, and other inputs, properly labeled visual content will be positioned to perform well in these new search environments. Today’s alt text best practices lay the groundwork for success in tomorrow’s search paradigms.

    Measuring the Impact: Tracking Alt Text Performance

    Analytics Integration

    To truly understand how alt text affects your site performance, consider setting up tracking for image search traffic in Google Analytics or similar platforms. This data can help quantify the SEO benefits of your alt text implementation.

    Accessibility Testing

    Regular accessibility audits using tools like WAVE (Web Accessibility Evaluation Tool) or axe can help identify areas where your alt text could be improved. These tools provide actionable insights about compliance with WCAG standards.

    User Feedback

    Don’t underestimate the value of direct feedback from users with disabilities. Consider adding accessibility feedback options to your site or conducting user testing with individuals who use assistive technologies.

    The Strategic Advantage of Alt Text Excellence

    In 2025’s competitive digital landscape, every ranking factor and user experience element matters. Alt text represents a unique opportunity to simultaneously improve search visibility, demonstrate social responsibility, and create more inclusive digital spaces.

    By investing in quality alt text—whether through meticulous manual creation or strategic automation with tools like WP Descriptor—you position your website for both immediate performance gains and long-term success as search algorithms and user expectations continue to evolve.

    The most successful digital strategies recognize that technical SEO and human-centered design aren’t separate considerations but complementary approaches that, when combined effectively, create truly exceptional online experiences. Alt text sits precisely at this intersection, offering a perfect example of how doing what’s right for users ultimately benefits your business goals as well.

    Don’t miss this opportunity to enhance your digital presence while making the web more accessible for everyone. Whether you manage a small blog or oversee enterprise-level content operations, making alt text a priority today will yield returns well into the future.

  • WordPress Drama – The Latest Update

    If you don’t know what WordPress is or the recent discussions about it, let’s talk. WordPress is a widely used platform that allows people to easily create and manage websites, and lately, there have been some important debates about its future direction that are worth understanding. Let’s break it down step by step so you have a good idea of what’s happening and why people care so much about it.

    The Main Player(s)

    Let’s talk about the important people and groups:

    • WordPress is one of the most popular tools for building websites. It is very flexible and easy to use, which makes it popular with marketing companies that want to create websites without needing special technical skills. WordPress has helped many of these companies offer more services and call themselves web development agencies. This means that businesses that may not have had the technical ability to create websites in the past can now use WordPress to do so, which has made website building much more accessible. However, this has also led to different opinions about the value of these services and whether such agencies can truly be called web development providers.
    • Automattic is the company started by Matt Mullenweg, who also co-founded WordPress. Automattic runs many products related to WordPress, including WordPress.com, which is a commercial service that provides hosting and other features for users who want a more streamlined experience. Automattic has a big influence on the WordPress world, and its decisions are often talked about in the community. Because Automattic plays such a major role in the development and direction of WordPress, the choices it makes are sometimes met with mixed reactions, with some supporting the changes and others feeling concerned about how these decisions affect the larger WordPress ecosystem.
    • The WordPress Community includes developers, designers, content creators, and users who help with the open-source project. This group helps improve WordPress by giving feedback, making plugins and themes, and joining community events. The community has different views about the direction of WordPress, with some wanting to keep things stable and others wanting more changes. This diversity of opinion is both a strength and a challenge for WordPress. It means that there is always a lot of input, but it also means that reaching agreements can be tough. The community is made up of many different types of people, from beginners to experts, and from hobbyists to professional developers, which adds to the variety of perspectives.

    The Events*

    • Matt gets a bug up his ass one day about WPEngine and decides to accuse them of freeloading and messing up his software and doing other things he doesn’t like. Initially, people were sympathetic to this, because this is absolutely a thing that companies do with free software and it sucks. However, reactions were muted and WPEngine especially didn’t immediately just roll over and give him what he wanted, so Matt went on to turn up the heat in a follow-up blog post, calling them a “cancer” and telling their customers they should leave.
    • WPEngine sends a cease-and-desist in which they also accuse Mullenweg of trying to shake them down for millions of dollars and threatening them if they did not pay up, and oh my goodness they included receipts.
    • Mullenweg does not, in fact, cease or desist. Automattic — controlled by Matt — fires back with its own cease and desist, and Matt goes on to comment on X (“formerly Twitter”), and a particular orange site where many other commenters plead with him to shut up for his own good, and on his personal blog.
    • When all that only manages to get a quiet murmur in tech news circles, Matt decides to ban WPEngine’s hosted sites from accessing WordPress software updates from WordPress.org, which he controls.
    • WPEngine responds with a lawsuit in 11 complaints, using delightfully tasty legal terms like “extortion”, and, oh, also now telling the world that Matt had tried to poach their CEO and then threatened her when she didn’t cooperate, and oh my goodness again there are receipts in the lawsuit! The current executive director of WordPress apparently finds out, from this lawsuit, that Matt was attempting to replace her, and bounces.
    • Matt goes on to run his mouth everywhere until he lands a lawyer with a high enough hourly rate to convince him to touch grass for a minute.
    • Now the tech news is starting to pick all this up (and this is when traffic starts to spike at r/Wordpress), but still not quite at the volume Matt’s looking for.
    • Matt offers employees of Automattic a pretty sweet severance deal if they don’t like the emperor’s new clothes, and over 8% of his staff say “thank you, bye”.
    • Matt gets a petty little checkbox added to the wordpress.org login that makes you promise, cross-your-heart, you’re not “affiliated with” WPEngine. What does that mean? Nobody knows and Matt banhammers people for asking.
    • Next, Matt directs WordPress.org to steal a popular plugin, managed by WPEngine, used by millions of sites, and rename it, and force-install that onto every site that was previously using WPEngine’s plugin. Matt calls this a “fork”, and says it’s “for security reasons”. This has a direct impact on millions of customers, ties up agencies with inquiries, and absolutely blows up tech news. Matt starts injecting this directly into his veins and slumps back on the floor of his “post-economic” bathroom (this last part might not have actually happened, I’m not sure).
    • …and he bans another popular plugin (archive)
    • …so some plugin developers begin to move their plugins off of wordpress.org: exhibit a (archive), exhibit b (archive).

    Other recaps for those that try to maintain a balanced drama diet:


    Lifted almost verbatim from: https://www.reddit.com/r/SubredditDrama/comments/1g4pr8f/wordpress_the_software_is_currently_embroiled_in…

    You can read more about this discussion on Reddit. Automattic supports changes like the Gutenberg project that, in theory, was intended to make editing easier, but the community grew worried about compatibility, learning new features, and how these changes might affect their current way of working. The Gutenberg editor aimed to bring a modern editing experience similar to other popular platforms, but these changes mean that users have to adapt, and not everyone found the transition easy. The UI, to this day, fails to be clear and useable. A few users appreciate the new features and felt that Gutenberg makes content creation simpler, but others find it disruptive to their current setup.

    For more on community reactions, check out this Reddit thread. On the other hand, some people think that using new technologies is important for WordPress to stay competitive as website tools change. The world of website building is constantly evolving, and many feel that WordPress needs to keep up by offering more advanced tools and features that users expect. Without these updates, WordPress might fall behind newer competitors that offer a more modern user experience.

    Business Considerations

    From a business point of view, these changes are part of a larger trend in the industry to make editing tools more dynamic and user-friendly. Businesses today want platforms that are easy to use, even for people who are not very technical. This topic has also been discussed extensively on Reddit. As with any changing platform, it can be hard to balance new features with what the community wants, but it is often needed to keep growing in the long run. If WordPress does not innovate, it risks losing users to other platforms that offer a simpler or more modern experience. However, too much change can also create frustration for long-time users who prefer the old way of doing things.

    For agencies and businesses that use WordPress, these changes bring both good opportunities and some challenges. Businesses that have used the classic editor for years may find it difficult to switch, and there could be additional costs involved in making sure everyone knows how to use the new tools effectively. Businesses need to consider how these changes affect their overall strategy. While Gutenberg could have improved the way content was created, it requires updates to plugins and themes to ensure compatibility. This can be both time-consuming and costly, especially for businesses with complex setups.

    The discussions about WordPress’ future show how hard it can be to manage an open-source platform with many users and different opinions. Automattic’s role in leading the project is important, but they must always balance new ideas with what the community needs and expects. It is not easy to keep everyone happy when there are so many different types of users with different needs. Some people want stability, while others want new features, and Automattic has to try to find the best path forward for everyone.

    For businesses, staying informed about these changes and adapting to new features will be important to get the most out of WordPress while avoiding any major issues. Keeping up with changes can be challenging, but it is also an opportunity to improve and grow. By understanding the new tools and taking the time to learn how to use them, businesses can make sure they are making the most of what WordPress has to offer. This will help them stay competitive and ensure that their websites are modern, engaging, and effective. Being proactive about adapting to change is key, and businesses that do so will likely find themselves in a better position to succeed in the long term.

  • What Comes After WordPress?

    What Comes After WordPress?

    This week WordPress and its founder, Matt Mullenweg, got into a conflict with the Managed WordPress hosting company, WP Engine. WP Engine started in 2010 under the helm of Jason Cohen. It currently hosts 200,000 WordPress websites. At the WordPress WCUS 2024 event, Mullenweg called out WP Engine for its ‘lack of contribution’ to the community. WP Engine sent a cease and desist letter over the statements. WordPress sent a cease and desist letter of its own. In their letter on the 23rd, they called for action and a response by October 3rd. On September 25th, Mullenweg blocked access to code updates by all of the WP Engine sites hosted there. In short, WordPress wants 8% of WP Engine’s estimated $400-million/year income for “licensing.” They want $32-million. The WordPress community is in disarray. Some are siding with Mullenweg. Many are questioning if this is the point where WordPress dies. It’s a good question. One person has hobbled 200,000 websites leaving them vulnerable to bugs and exploits. WordPress runs approximately 30 – 40% of the websites on the Internet. If there is a massive shift in how it functions, how one can gain access to updates or how much it costs, they could change. Developers adopt content management systems. Salespeople sell what the developers produce. If WordPress becomes toxic, that adoption trend could reverse. People could start to replace their WordPress websites with alternatives like Squarespace, Laravel, etc..

    What if, as some have said, this is The Death of WordPress? Well, first: it won’t be the actual death of the project. People out there are still using janky applications concocted in 1995 and they won’t surrender them. There’s always going to be a million websites using WordPress. Second, people are going to adopt new tools. The trend of simplicity is going to snag many WordPress site owners who have been shaken out of their complacency. They will go to Squarespace, Wix, Weebly, Card and a host of other simple solutions. For many, this will be fine. Honestly, there’s a tier of WordPress sites that were never well served by the excess horsepower of WordPress.

    Maybe this is an opportunity.

    Where am I coming from? My personal history with content management goes back to the 1990s. I’ve been coding since the Apple ][ days. I was tapped ca. 1996 to build functionality into my websites. I built ecommerce systems from scratch. I built Perl based content management systems. In the 2000s, I built “Daccor” an ASP driven content management company that ran sites like the BC Conservatives website and the CARP BC website. Why didn’t I keep going? Money. I was too poor to do the slog of evangelizing an unknown CMS while building out functionality, roll out new designs, and being a breadwinner. Since 2005 or thereabouts, I have been building custom code for Drupal, WordPress and other projects.

    WordPress started as blogging software. It was a fork of the b2/cafelog project by François Planque. Mullenweg and Mike Little forked the code and began building towards what we know as WordPress today. If you look at the b2 code, you can see evolutionary clues of what grew from there. A lot has happened in 21 years.

    The Content Management System

    Here are my thoughts for what a content management system needs. It’s coloured by my affinities, so what I propose will echo what I like. For the longest time, WordPress’ stack looked like my goto stack, so some of these choices will be familiar.

    PHP Based. Love it. Hate it. PHP is very popular and runs almost all of the web servers. PHP8 is economical in its processing. It’s well adopted. The one trend I see that I don’t like: Composer. There are so many applications that ship with the need to go through Composer to get the supporting libraries. That’s great for nerds, but for every nerd rolling out a WordPress website, there are 1000 non-nerds who want to hit [DOWNLOAD] and call it done. Using Composer knee-caps adoption. If a product is going to be popular, it needs to be easy.

    When it comes to coding conventions: I spent my first 20 years (1983 – 2003) writing procedural code. Object oriented (OO) code is bolted on as a skill set for me. I found that how WordPress combined OO and procedural code was really attractive. Some developers are so in love with OO code that they miss the heart attack it delivers to the hardware it runs. The code needs to be as lean as possible. Period.

    When the considerations are stacked: security, performance, utility: in that order. There are so many bad actors, security has to be the first and foremost considerations. Second, but a close second: the CMS needs to deliver its output quickly. It’s not uncommon to see WordPress sites dawdle for two to three seconds before it gets around to serving its content. What a failure. Third, utility. The user experience has to be good. There needs to be easy templating available to control the look and feel of the admin screens, the front end displays and data directly sent to users.

    The code conventions need to be straightforward and orderly. There needs to be a way to filter all of the content and templating easily. I used to write code to track the behaviour of Drupal code to build its output. It would go round and round and round, refactoring and messing with the presentation of the data. That all cooks into server load, performance lags and unpredictable code.

    JQuery Based. This is a personal bias. I like JQuery and I dislike React. As WordPress has adopted JQuery, it’s a move I like that I would keep with a new CMS. I would move towards headless, but not full on headless. I have seen web servers have partial failures and their output is immediately lobotomized. I maintain that while search engines can index dynamically built pages that pull in data via Ajax, search engines better index pages where the content is on the page. I like the idea that a page can be saved offline and look intelligible. I don’t like the idea that a web page has to only be viewed on the connected Internet. It flies in the face of using the Internet to publish data in a way that delivers portable content. I like the idea of using Ajax to bring in content for progressive disclosure– to enhance the experience. Maybe having the JavaScript library as a swappable element would be a winning feature. It would let some developers work with React, JQuery or whatever library they choose.

    MySQL Based, but flexible. MySQL and MariaDB are workhorses. Going to one server for the true source of data creates a chokepoint. WordPress’ architecture has been good when it comes to its data schema. I used to wince seeing all of the tables that Drupal would spin up; with their complicated and resource intensive db joins; the 500+ tables that would give the MySQL paging system a stroke. WordPress avoided that for the most part. I think they went a little too far and some of the tables are cumbersome and problematic in their own way. Lessons learned from other CMSes:

    • Fewer tables is better, to a point.
    • Simple queries win– it’s best to pull a lot of records.
    • Remember revisions. Every piece of content should have a way to see its history.
    • Find a way to warehouse old data to remove it from the active data.
    • Build in a way to use DB replication (master-slave relationships) from the outset. Write to main DB, read from the best available child DBs.
    • Build in a way to pull in other data sources easily to synthesize a complete picture: remote data, S3 storage, text file content, etc.
    • Cache data as much as possible without being its own performance hit.
    • Pre-package data as much as data when the data will be commonly called in its packaged form.

    HTML5. Embrace it. Use the HTML5 potential and all that it brings. There are powerful shorthand ways to accomplish things nowadays. Make sure all of the HTML conventions work with lean code.

    Build with SEO and Performance In Mind. We’re talking about web publishing. It’s not an afterthought to have the page load fast, work well and be discoverable on the web. WordPress will plunk all manner of render blocking Javascript in the header. Don’t do that. Put as much code in the footer and defer as much as possible. Work with what web clients need to create the best output delivered in the best fashion. Build the output to make the time-to-first-byte (TTFB) as short as possible.

    Fetch some content routinely at the client. Some of the aspects of a page don’t need to appear immediately. If they’re not indexed by Google it may not be that important. Build in a capacity to easily fetch some content from the CMS or even remote sources of data.

    Portable. Portable Portable. Make everything on the site portable. Make it show that content and configs can be backed up, downloaded, moved, frozen or otherwise worked with. With the prospect of use generated content, but the need to promote websites through the development lifecycle there needs to be easy ways to move setting without slamming content.

    Reconcile CSS before it gets served out. In my coding, I will see three and four layers or countermanding CSS instructions: WP core, Woo, Divi, some other plugin, then eventually what I introduce to style the output. That’s sloppy. There needs to be a compilation step that sorts out these conflicting and countermanding rules before the styling comes out. If it’s not reconciled, it creates processing load for the web client, and inconsistent user experiences. It needs to be cleaned up before it’s delivered.

    Inherit Good Code. In mulling this over, I’ve thought: keep all of the WordPress hooks, lose some of the code. WordPress plugins go beyond hooks. I’ve written many plugins that drill right into the core of WordPress to get the functionality and data I need. This proposed plugin should be poised to make the use of the huge number of WordPress plugins that exist. Because of the deep ties to the WordPress core, I propose this instead: map the hooks (actions and filters) to how the arguments are made with WordPress. Build a conversion system to adapt incoming WordPress plugins to operate in the new CMS. It gives those products additional longevity and it gives the new CMS a library of tools to start with.

    The Open Source Project

    WordPress’ row with WP Engine has shown off that the organizational shortcomings can jeopardize a project more than bad coding or poor adoption. There needs to be several things in place to proceed successfully.

    Make it Open Source. Make it under the GPL2 license to ensure that there won’t be a rug pull later by a petulant player.

    Put shared assets under the control of the non-profit. It should be easy to add assets and value. It should be hard to vandalize it; or repeal it. That’s in the core of the Open Source movement, but it’s obvious that people can decide to ignore that. The key holders of these critical elements need to be vetted by the non-profit oversight and then there needs to be a means to hold them accountable to uphold a charter of conduct.

    Set up a non-profit. Set up a non-profit that oversees the roadmap. Make it democratic. Given how many anecdotes there are of women and other voices being squelched by less than diplomatic developers and gatekeepers, put governance, safeguards and oversight into the core of the organization, along with a way to deal with people who make the contribution environment toxic. When my staffer and I were listening to a talk by Angela Byron about how they were blockaded by bad actors in the Drupal community, she described their tactics, their language and how they put a chill on participation. Everything she said was valid and I believed all of it, but also: my staffer and I experienced the same thing despite being men. The gatekeeping and anti-social conduct can kill a community. The oversight of the community needs to keep people on good behaviour and it has to watch the watchers with cycles of accountability and democratic interaction.

    Set up a means of commercialization. Often founders struggle to get a glimmer of adoption. Then something kicks and the process takes off. Open source is a different beast from commercial software. Software accomplishes work and carries value. When open source does that, often consultants and producers of add-on products reap the rewards. With software, the money comes to those who exploit the technology more so that the person who pioneers the technology. There needs to be an understood means of commercialization that all parties understand. If one company reaps billions while another gets millions, that’s how it goes.  Rasmus Lerdorf, the inventor of PHP, is not as wealthy as Mark Zuckerberg the user of PHP who used the technology to build Facebook. It’s impossible to police parties that profit from a successful venture.

  • ECommerce Transaction Alternatives For WordPress.

    There are several alternative ecommerce plugins for WordPress that you can consider:

    Easy Digital Downloads (EDD)

    Easy Digital Downloads is an excellent choice if you’re primarily selling digital products like ebooks, software, or downloadable content. Key features include:

    • Built-in support for popular payment gateways like PayPal and Stripe
    • Customer account management
    • Order tracking
    • Ability to sell subscriptions and accept recurring payments

    EDD offers a free version with robust features, making it a cost-effective option for many online stores.

    WP Simple Pay

    If you don’t need a full shopping cart system and primarily sell services or single products, WP Simple Pay is a decent alternative. It offers:

    • Pre-built templates and a drag-and-drop form builder
    • Support for multiple payment gateways
    • Easy setup for buy now buttons and donations
    • Ideal for one-time payments and simple transactions

    Ecwid Ecommerce Shopping Cart

    Ecwid is a versatile option that can be integrated with WordPress and other platforms. It offers:

    • Focus on physical product sales
    • Shipping and tax management
    • Integration with various payment providers
    • Customizable design blocks for store layout

    GetPaid

    For freelancers and service providers, GetPaid offers a simpler solution focused on invoicing and payments:

    • Buy Now buttons for standalone products
    • Invoice creation and sending
    • Customizable checkout pages
    • Recurring payment options

    MemberPress

    If your business model involves selling online courses, memberships, or exclusive content, there is MemberPress:

    • Tools for creating and managing online courses
    • Membership site functionality
    • Content dripping and paywalls
    • Subscription payment handling

    When choosing an alternative to WooCommerce, consider your specific needs, such as the type of products you’re selling, payment requirements, and desired features. Each of these plugins offers unique strengths that may better suit your ecommerce goals.

  • Setting Up A Custom Color Scheme For Divi

    Setting Up A Custom Color Scheme For Divi

    I have attached the file that I used my case.blankOne Divi feature is”Color Scheme.” It presets for green, orange, pink, red and its default blue color schemes that influence the colors of borders, buttons and other accents on a baseline Divi theme. What happens if none of those colors jibe with your design? In our case, there were layers of styling rules: baseline WordPress, Divi, Woocommerce, and our styling. It’s great that Divi has Woo specific styling available, but it wasn’t helping what we were trying to accomplish.  That’s a lot to wade through and all of those style rendering decisions turn into processor use on your client machines. A site that is intensive to render may perform worse or appear to render in some unpredictable way on some browser. Rather than add to that, setting the color scheme in Divi is one way to output as little styling as possible. The following is my approach for overriding the Divi color schemes and adding a reference for your project.

    The Divi color schemes can be appended by adding some filters and actions to your custom theme’s functions.php

    In my case, I was working on a custom theme, named “hira,” so the prefixes in my example echo that.

    The color scheme choices need to be appended.


    // Add Hira color scheme to Divi color scheme choices
    function hira_color_scheme_choices($color_choices = []) {
    $color_choices['hira'] = esc_html__( 'Hira', 'Divi' );
    return $color_choices;
    }
    add_filter('et_divi_color_scheme_choices', 'hira_color_scheme_choices');

    The color schemes need to be appended with an entry for the new key (example here: ‘hira.’)


    // Define the Hira custom color scheme
    function hira_custom_color_scheme($color_schemes) {
    $color_schemes['hira'] = array(
    'Accent Color'         => '#FF5733',
    'Secondary Color'      => '#33FF57',
    'Footer Background Color'  => '#3357FF',
    'Menu Background Color' => '#FF33F1',
    'Menu Text Color'      => '#33FFF1',
    );
    return $color_schemes;
    }
    add_filter('et_builder_color_schemes', 'hira_custom_color_scheme');

    After the color scheme is set, it can be referenced. In my case, I added a css sub-directory to my child theme, “css.” I made a stylesheet for this scheme. I called it “hira_scheme.css” and put it in that css file.


    // Load the CSS only if Hira color scheme is selected
    function load_hira_scheme_css() {
    // Get current theme options
    $settings = get_option('et_divi');

    /* Check if 'hira' is selected as the color scheme */
    
    if ( isset( $settings['color_schemes'] ) && $settings['color_schemes'] === 'hira' ) {
    // Enqueue the Hira color scheme CSS file
    wp_enqueue_style( 'hira-scheme', get_stylesheet_directory_uri() . '/css/hira_scheme.css', array(), null );
    }
    }
    add_action( 'wp_enqueue_scripts', 'load_hira_scheme_css', 15 );

    To build out the scheme elements, I cribbed from the main divi file,
    /wp-content/themes/Divi/style-static.min.css
    I looked for all of the color scheme relevant stylings with the “_scheme_red” phrase in the selectors and copy them into my [keyword]_scheme.css file. I then do a find-replace to swap
    “_red” to match your phrase from your color scheme settings (in my example, I would be swapping _red or _hira

    I have attached the file that I used my project.

     

  • If I Have Divi For My Theme, Why Would I Need A Child Theme for Divi?

    If I Have Divi For My Theme, Why Would I Need A Child Theme for Divi?

    If you’re using the Divi theme, there are several reasons why you might want to consider using a child theme:

    Preserving Customizations

    The main benefit of using a Divi child theme is to preserve your customizations when Divi updates. If you make direct changes to Divi’s core files, those changes will be overwritten when you update the theme. A child theme allows you to make customizations that won’t be affected by updates.

    Advanced Customization

    If you want to make more advanced customizations beyond what’s possible through Divi’s built-in options, a child theme is necessary. This includes:

    • Editing PHP files like header.php or footer.php
    • Adding new PHP or JavaScript files
    • Making extensive CSS changes

    Professional Development

    For agencies or freelancers, using child themes allows for easier customization and integration for client websites. It provides more flexibility and control over the site’s functionality and appearance.

    When You May Not Need a Child Theme

    It’s important to note that you don’t always need a child theme for Divi. If you’re only:

    • Using Divi’s built-in customization options
    • Adding custom CSS through Divi Theme Options
    • Using the Divi Builder for layouts
    • Not editing core theme files

    In these cases, a child theme isn’t strictly necessary.

    Deciding to Use a Child Theme

    Consider using a Divi child theme if:

    • You’re serious about your website and want maximum flexibility
    • You plan to make extensive customizations
    • You want to ensure your changes are preserved during updates
    • You’re a developer working on client sites

    If you’re creating a website for your business or blog, Divi’s built-in design tools might be all you need, especially if you want to keep things simple. Think of it like decorating a room – sometimes you just want to arrange the furniture and hang some art, rather than knocking down walls or doing major renovations. While there are ways to make more advanced changes to your site’s design, you don’t have to worry about those unless you want to do some serious customization down the road.

  • The Juggling Act of Priorities for a WordPress Developer

    The Juggling Act of Priorities for a WordPress Developer

    Being a WordPress developer is akin to performing a delicate juggling act. With numerous tasks requiring attention, from translating visual designs into functional websites to ensuring optimal performance and security, managing priorities becomes crucial. We put a lot of effort putting together an in-depth look at how a WordPress developer can effectively balance these responsibilities.

    1. WordPress Development

    Collaboration with Design Teams, Digital Marketers and Subject Matter Experts. A WordPress developer’s journey often begins with collaboration. Working closely with design teams to translate visual designs and wireframes into fully functional and interactive websites is foundational. This requires understanding the design vision and translating it into code, ensuring the website is both visually appealing and functionally robust.

    2. Theme Customization

    Customizing existing WordPress themes or developing new ones from scratch is a critical task. This involves ensuring that the website maintains a consistent and branded look. Whether tweaking a pre-made theme or building a custom one, the goal is to align with the brand’s identity while providing a unique user experience.

    3. Responsive Design

    With the increasing variety of devices, ensuring responsive design is non-negotiable. A WordPress developer must ensure that websites are optimized for various screen sizes, providing a seamless experience on desktops, tablets, and mobile devices. This involves thorough testing and adjustments to maintain functionality and aesthetics across platforms.

    4. Plugin Integration

    Extending Functionality Plugins are the lifeblood of WordPress, extending its capabilities beyond the core features. Integrating and configuring plugins to add functionalities like contact forms, social media feeds, SEO optimization, and caching is a regular task. Each plugin must be evaluated for compatibility, performance impact, and security before implementation.

    5. Performance Optimization

    Speed Matters Fast page load times are crucial for user experience and SEO. Implementing best practices for front-end performance optimization, such as image compression, code minification, and effective caching techniques, is essential. Regular performance audits and adjustments ensure the website runs smoothly and efficiently.

    6. Cross-Browser Compatibility

    Ensuring cross-browser compatibility is another important aspect. A website must look and function consistently across different browsers. This requires thorough testing on multiple browsers and devices, identifying and fixing inconsistencies to provide a uniform experience for all users.

    7. Code Quality

    Maintaining Standards Writing clean, well-organized, and maintainable code is fundamental. Adhering to industry standards and best practices not only improves code quality but also facilitates easier maintenance and updates. Regular code reviews and refactoring are part of this ongoing effort.

    8. Troubleshooting and Bug Fixing

    Despite best efforts, issues and bugs can arise. Promptly identifying and resolving front-end issues, bugs, and inconsistencies is crucial to maintain a flawless user experience. A systematic approach to troubleshooting and debugging helps in quickly addressing these problems.

    9. Collaboration

    Seamless collaboration with UX/UI designers and content creators is essential for integrating design, functionality, and content. Regular communication and coordination ensure that everyone is aligned and working towards the same goals, resulting in a cohesive final product.

    10. Staying Updated

    The web development landscape is constantly evolving. Staying updated with the latest trends, technologies, and best practices in WordPress and web design is vital. Continuous learning and adaptation enable a developer to enhance the quality of websites and stay competitive.

    11. Security

    Security is a paramount concern. Implementing security measures and best practices to safeguard websites against threats and vulnerabilities is an ongoing responsibility. Regular security audits, updates, and monitoring help in maintaining a secure environment.

    Juggling these diverse priorities requires a structured approach, effective time management, and continuous collaboration. By balancing these responsibilities, a WordPress developer can create high-quality, secure, and performant websites that provide an exceptional user experience. The key is to stay organized, proactive, and adaptable, ensuring each aspect is given the attention it deserves while keeping the bigger picture in mind.

  • Understanding CSS Media Queries

    Understanding CSS Media Queries

    CSS media queries are a powerful tool that allow you to apply different styles based on the characteristics of the device or viewport. They enable you to create responsive designs that adapt to different screen sizes, resolutions, and device types (desktop, tablet, mobile, etc.).

    Syntax

    The basic syntax for a media query is as follows:

    css

    @media [media-type] ([media-feature-rule]) {
    /* CSS rules go here */
    }
    • @media is the at-rule that starts a media query.
    • media-type (optional) specifies the type of media the styles should apply to, such as screen, print, or all (default).
    • media-feature-rule defines the conditions or rules that must be met for the styles to apply. Common rules include min-width, max-width, orientation, and others.

    Common Use Cases

    1. Responsive Web Design

    Media queries are essential for creating responsive websites that adapt to different screen sizes. Here’s an example of how to apply different styles based on the viewport width (see more on breakpoints below):

    css

    /* Styles for screens smaller than 600px (mobile devices) */
    @media screen and (max-width: 599px) {
    body {
    font-size: 14px;
    }
    .container {
    width: 100%;
    }
    }
    /* Styles for screens between 600px and 900px (tablets) */
    @media screen and (min-width: 600px) and (max-width: 899px) {
    body {
    font-size: 16px;
    }
    .container {
    width: 80%;
    }
    }/* Styles for screens 900px and wider (desktops) */
    @media screen and (min-width: 900px) {
    body {
    font-size: 18px;
    }
    .container {
    width: 60%;
    }
    }

    1. Printing Styles

    Media queries can be used to apply specific styles when a page is printed to paper:

    css

    /* Styles for printing */
    @media print {
    body {
    font-size: 12pt;
    color: black;
    background-color: white;
    }
    .no-print {
    display: none;
    }
    }
    1. Orientation-specific Styles

    You can target styles based on the device’s orientation (portrait or landscape) using the orientation media feature:

    css

    /* Styles for portrait orientation */
    @media (orientation: portrait) {
    .container {
    flex-direction: column;
    }
    }
    /* Styles for landscape orientation */
    @media (orientation: landscape) {
    .container {
    flex-direction: row;
    }
    }

    Common CSS Breakpoints

    When creating responsive designs with media queries, it’s essential to consider the screen sizes of popular devices and web browsers. By targeting specific breakpoints, you can ensure that your website or application displays correctly across a wide range of devices.

    Desktop Browsers

    For desktop browsers, the most common breakpoints are:

    • 1920px: This breakpoint targets large desktop screens and high-resolution displays. It’s a good practice to start with a wide layout and scale down for smaller screens.
    • 1366px: This breakpoint covers most modern desktop and laptop displays with a resolution of 1366×768 pixels or higher.
    • 1024px: This breakpoint is suitable for older desktops and laptops with smaller screen resolutions.

    css

    /* Styles for large desktop screens */
    @media screen and (min-width: 1920px) {
    /* CSS rules */
    }
    /* Styles for modern desktops and laptops */
    @media screen and (max-width: 1919px) and (min-width: 1367px) {
    /* CSS rules */
    }/* Styles for older desktops and laptops */
    @media screen and (max-width: 1366px) and (min-width: 1025px) {
    /* CSS rules */
    }

    Tablets and Mobile Devices

    For tablets and mobile devices, the most common breakpoints are:

    • 768px: This breakpoint targets most tablets in landscape orientation and some smaller desktop screens.
    • 600px: This breakpoint is a common choice for targeting smaller tablets and larger mobile devices in landscape orientation.
    • 480px: This breakpoint is suitable for most smartphones in landscape orientation.
    • 320px: This breakpoint covers most smartphones in portrait orientation, including older and lower-resolution devices.

    css

    /* Styles for tablets in landscape orientation */
    @media screen and (max-width: 1024px) and (min-width: 769px) {
    /* CSS rules */
    }
    /* Styles for smaller tablets and larger mobile devices in landscape */
    @media screen and (max-width: 768px) and (min-width: 601px) {
    /* CSS rules */
    }/* Styles for smartphones in landscape orientation */
    @media screen and (max-width: 600px) and (min-width: 481px) {
    /* CSS rules */
    }

    /* Styles for smartphones in portrait orientation */
    @media screen and (max-width: 480px) {
    /* CSS rules */
    }

    It’s important to note that these breakpoints are general guidelines and may vary depending on your specific project requirements, target audience, and device usage patterns. It’s always a good practice to test your website or application on actual devices and make adjustments as needed.

    Additionally, consider using responsive design techniques like fluid grids, flexible images, and media queries to create a seamless experience across different devices and screen sizes.

    Best Practices

    • Use relative units like em, rem, or vw/vh for better responsiveness.
    • Start with mobile-first or desktop-first approach based on your target audience.
    • Combine media queries with CSS techniques like flexbox and grid for efficient layouts.
    • Prefer min-width over max-width for better future-proofing.
    • Test your media queries on various devices and screen sizes.

    CSS media queries are a powerful tool that enable you to create responsive and adaptive designs. By understanding their syntax and use cases, you can create websites and applications that provide an optimal user experience across a wide range of devices and screen sizes.

    blank

  • Turning Off The AI Bar on Divi

    Divi (the theme system from Elegant Themes) has added an AI tool. Some people don’t like it. With the most recent copy of Divi, the element can be switched off.

  • Performance Improvements That Can Speed Up Your Website

    Performance Improvements That Can Speed Up Your Website

    Picture this: You’ve crafted an incredible WordPress website complete with engaging content and a design that could win awards. But there’s a catch – your site takes ages to load, and your audience’s enthusiasm wanes with each passing second. The load speed of a website is not just a number; it’s the gateway to transforming visitors into loyal customers and brand ambassadors. When your site is a speedster, it lays out a red carpet for everyone to dive into what you offer. Even Google rewards such sprightly sites with higher rankings, thanks to its consideration of page loading speed and server response time in its algorithm.

    However, sluggish server response times could spell doom. Don’t test the patience of your website visitors: they’ll just leave the site. Websites need to load fast to keep the audience riveted.

    Let’s explore how to achieve some WordPress performance improvements to ensure your website is as swift while keeping any of the pizazz delivered by Javascript and CSS, keeping your audience captivated and Google happy. Let’s supercharge your WordPress website!

    KASD (Keep A Simple Dom)

    Similar to the KISS rule, the complexity of your HTML can make or break your performance. While HTML is usually the smallest part of your page payload, it’s the conductor: it’s orchestrates what happens on the page. All of those instructions have to be weighed in and reconciled. If they are too complicated, that distills into a performance loss. This is especially important for designers who chase the mobile experience. It’s easy for designers to repeat an element for the sake of the mobile experience. That adds more complexity and leans of the web browser to show and hide elements based on the screen size or device. Instead, try to have one element that is always present with its look affected by CSS. Also, don’t be afraid to second guess the HTML output by WordPress page builders. They sometimes build cumbersome HTML that gives web browsers a heart attack.

    Image Optimization

    Images can sometimes be unnecessarily large. For instance, an icon measuring 72×72 pixels might actually be utilizing a 1400×800 pixel image. There could be a possibility of a plugin malfunction which requests an image that is too large for optimal performance. A GTMetrix report is handy in such situations as it not only identifies the images in need of optimization but also generates the optimized versions for you. Replacing the problem images with these optimized ones can improve performance.

    Understanding Image Formats. It’s crucial to discern between the different image formats like GIFs (pronounced with a hard or soft ‘G’– let’s not fight over this), JPEGs, PNGs, SVGs, and bitmaps. Each format has its own set of attributes, so choose the one that best suits the intended purpose within your presentation.

    JavaScript Placement

    Header Placement – Use With Caution. Placing JavaScript code in the header makes it execute before the rest of the content. However, this could also mean that the content display is paused until the JavaScript is fully executed, which is known as “render blocking.” For the end user, this is not desirable as they might end up staring at a blank screen for an extended period.

    Consider Footer Placement. Certain codes can be placed in the footer without any issues, such as analytics code, auxiliary code, or code pertaining to the lower sections of the web page (like a dynamic footer).

    Client-Side Caching

    Enable Content Caching. WordPress often appends query strings to URLs and modifies these strings with each load to ensure that images, scripts, or styles are loaded afresh. While this guarantees that the content is up-to-date, it can be time-consuming from an end user’s perspective.

    Modify Expiry Dates. By altering the expiry date, which is a metadata setting in the served assets, you can extend it to days or even months into the future. This allows the web browser to save some of the content on the user’s computer, which means it won’t have to re-download these elements each time the page is loaded. This takes advantage of browser caching, thus improving the loading speed for returning visitors.

    Handling Third-Party Assets in WordPress

    Third-party assets, though convenient, can adversely affect performance. It’s tempting to effortlessly integrate snippets from Instagram, Facebook, Google, Click-to-chat, or CRM tools into your WordPress site, but these can significantly slow it down.

    Gain Control Over External Assets. Whenever possible, try to host assets on your own site or CDN. For instance, download Google fonts and serve them from your WordPress site or your CDN.

    Serve Content via Server-Side Generated HTML. Instead of relying on Javascript to deliver or construct content, use server-side generated HTML, which is generally faster.

    Choose Wisely. Carefully decide on the third-party assets you want to include on specific pages. If performance is paramount, be discerning when it comes to incorporating third-party applications.

    GZIP Compression

    Minimizing file downloads is essential for speed. If a file is smaller, it takes less time to move it. Optimizing the number of files requested and reducing their size is key. In WordPress, each plugin and theme you use is likely to add multiple CSS and JS files, which can quickly accumulate to over 20 CSS and 20 JavaScript file requests.

    Use Plugins for consolidation. GZip Compression. Most web servers can serve files compressed with GZip, and almost all web browsers can decode them. Make sure this is enabled for your WordPress site for faster loading. WordPress plugins like WP Fastest Cache can combine CSS into fewer files and perform the same task for JavaScript.

    Server Caching in WordPress

    Cache Static Content. Store static versions of complex outputs, such as leaderboards, lists of recent posts, or stats, so that they don’t have to be regenerated every time.

    Optimize Before Shipping. Ensure that code is optimized on the server-side before it is sent to the client.

    Use Caching Plugins. Employ plugins like W3 Total Cache or WP Super Cache to enhance the caching capabilities of your WordPress site.

    Tune Keep-Alive Settings. Some browsers may repeatedly establish a connection to your server for each file request. By adjusting the server’s Keep-Alive settings, this connection can be maintained, saving time.

    Use Content Delivery Networks (CDNs) with WordPress. Integrating a CDN can alleviate the load on your server and provide faster content delivery by serving data from a location closer to the end user. In WordPress, this can be easily achieved by using plugins that facilitate CDN integration, such as WP Rocket.

    Flush Your Content

    Hang time is a killer when you’re waiting for a web page. This can be a side effect of the foundations of a website– PHP: the driver for WordPress and so many other website applications. By default, PHP can wait a long time before delivery of content back to the end user. It is possible to push it to begin earlier than otherwise. That sends content back to your audience faster. I do this by putting the flush() call at the top of the page.tpl.php file. If you’re about to output the themed data, you’re ready to deliver content, so I say push it out as soon as you can, even starting the process before the page.tpl.php is populated and served. One thing to note: flushing content may not be a tactic that plays well with GZip, so experiment.

    Consolidate CSS and JavaScript Files

    It’s highly beneficial to merge all your JavaScript files into a single file and do the same for CSS. Although content management systems like Drupal may inherently involve numerous supporting files, they often have the feature to aggregate JavaScript and CSS files. This consolidation can dramatically reduce the number of files from over 30 to just two or four. When using Wordress, add in a plugin like WP Fastest Cache to aggregate supporting files. While CSS can be aggregated with little jeopardy, aggregating JavaScript can lead to problems, so experiment before your deploy a change like that.

    Build and Use CSS Sprites

    CSS sprites allow you to use sections of a larger image to fulfill various graphical requirements on your web page. The concept of sprites is not new and has been used in video games for decades. However, its application in web design is relatively recent.

    By combining multiple elements into one image and utilizing CSS to extract the necessary sections, you can decrease the number of file downloads, which is crucial for performance. To effectively use CSS sprites, it’s essential to understand the intended use of the image and be adept in handling CSS backgrounds. This involves mastering techniques such as cropping and controlling image repetition.

    In WordPress, CSS sprites can be integrated into themes and plugins to enhance the loading speed and optimize graphical elements on your website.

    Need help?

    Part of what we do at Web321 is a set of performance improvements (aka a WordPress speed service). Do you want to talk about what we can do to improve your site speed?

We’ll take good care of your website.

Copyright © 2025 – Web321 | All Right Reserved