Naming WooCommerce Extensions: Addon, Add-On, or AddOn?

Flat lay of scattered Scrabble tiles spelling 'NAMING' on a white background.

A common question for WordPress plugin developers creating extensions for their own WooCommerce plugins revolves around the proper naming convention.

Specifically, how should the “addon” part of the plugin name be formatted? This seemingly minor detail can impact clarity, consistency, and even potential trademark considerations.

A recent online discussion explored the different approaches and offered some valuable insights for plugin developers in the WooCommerce ecosystem.

Let’s examine the various styles and recommendations for naming your WooCommerce extensions.

The Quest for Consistent Naming

The initial question highlighted the uncertainty surrounding the capitalization and hyphenation of “addon” when naming plugins that extend a main plugin, using “WooCommerce Do Whatever” as an example.

The three variations presented – “Addon,” “Add-On,” and “AddOn” – represent the common approaches developers might consider. The goal is to choose a style that is both clear to users and consistent across all extensions for the main plugin:

  1. WooCommerce Do Whatever – Yet Another Addon
  2. WooCommerce Do Whatever – Yet Another Add-On
  3. WooCommerce Do Whatever – Yet Another AddOn

The “Extension” Alternative

One participant humorously suggested using the term “Extension” instead of “Addon” altogether. While this doesn’t directly answer the formatting question, it points to a valid alternative that might be preferred by some developers for its clarity and common usage in the software world.

For example, “WooCommerce Do Whatever – Yet Another Extension“.

The “X for Y” Pattern

Another concise suggestion was to follow a pattern like “[Addon Name] for WooCommerce Do Whatever“. This approach clearly indicates the main plugin being extended and keeps the addon name separate and easily identifiable.

For instance, “Yet Another Feature for WooCommerce Do Whatever“. This pattern prioritizes clarity and avoids the formatting ambiguity of “addon“.

Trademark Considerations

A crucial point raised in the discussion concerned trademark infringement. It was advised that to minimize the risk of legal issues, the trademarked name (“WooCommerce”) should ideally come last in the plugin name.

Following this advice, the suggested format becomes “Add-On for Do Whatever For WooCommerce“. This prioritizes legal safety by clearly positioning the plugin as an add-on for the established WooCommerce extension.

The “AddOn” Preference

One developer simply stated a preference for the “AddOn” format (e.g., “Do Whatever Yet Another AddOn for WooCommerce“).

This style favors a single capitalized word, which can look clean and consistent in plugin lists. However, it might be less visually distinct than the hyphenated version for some readers.

Conclusion: Clarity, Consistency, and Trademark Awareness

While there isn’t a single universally mandated standard for naming WooCommerce extensions, the discussion highlights several important considerations. Prioritizing clarity for users, maintaining consistency across all extensions of a main plugin, and being mindful of trademark implications are key.

The suggestion to use the “[Your Plugin Name] Add-On for WooCommerce” format appears to strike a good balance by clearly indicating the plugin’s purpose, using a visually distinct and common “Add-On” style, and placing the “WooCommerce” trademark at the end to mitigate potential legal concerns.

Ultimately, developers should choose a naming convention that is clear, consistent within their own plugin ecosystem, and legally sound.

Related content

Rodolfo Melogli

Business Bloomer Founder

Author, WooCommerce expert and WordCamp speaker, Rodolfo has worked as an independent WooCommerce freelancer since 2011. His goal is to help entrepreneurs and developers overcome their WooCommerce nightmares. Rodolfo loves travelling, chasing tennis & soccer balls and, of course, wood fired oven pizza. Follow @rmelogli

Reply

Your email address will not be published. Required fields are marked *