Improvements to HubSpot Asset Marketplace Theme requirements

[DHrynevych]

We kindly request the review or removal of the undocumented HubSpot Asset Marketplace Theme requirement that prohibits custom modules from having the same label as default modules.

1.

As theme creators, we strive to have greater control over our custom theme modules, and we believe that the labeling of these modules should not be restricted. The idea of using "Some prefix Button" or "Theme name Button" instead of simply "Button" module label appears illogical and unfriendly to end users, undermining the cohesiveness of the theme. Unfortunately, we find ourselves facing limited options:

• Prefixing all our custom modules with "Theme name...module" would result in peculiar and illogical module names. Since editors are already aware they are using our theme, there is no need to constantly remind them of it through module labels.
• Naming only the default-like modules with the prefix "Theme name..." would create an awkward disparity in module naming. For instance:
  • Theme name Link
  • Card
  • Theme name Button
  • Hero Image
• Finding an alternative naming approach could either compromise semantic accuracy or introduce redundancy:
  • Using "Links" instead of "Link" or "Buttons" instead of "Button" raises semantic concerns.
  • Employing names like "Link-bla" or "Button-bla" would appear redundant.

Considering these limitations, we kindly urge you to reconsider this aspect and provide us with more flexibility in labeling our custom modules.

2.

Since theme modules and default modules are already segregated into distinct tabs, namely "Theme modules" and "Common modules", it seems reasonable to conclude that having identically labeled modules in different tabs should pose no issue.

3.

As an alternative solution, maybe this rule can be skipped when we hide official modules in our theme. So end user will not see two modules with the same label while using our Theme.

our theme.json:

...

"hidden_modules": [
  "@hubspot/rich_text",
  "@hubspot/button",
  "@hubspot/form", 
  "@hubspot/linked_image",
  "@hubspot/icon",
  "@hubspot/divider",
  "@hubspot/horizontal_spacer",
  "@hubspot/text",
  "@hubspot/page_footer",
  "@hubspot/section_header",
  "@hubspot/header"
],
...

***

We kindly request a thorough review of this specific rule.

Thanks

[DHrynevych]

Thanks ANisar for your feedback on the overall theme guidelines. We will discuss this with the internal team and our team will get back to you.

[DHrynevych]

Thank you for your feedback! Your feedback is important to us and helps us improve our services/products.   

The intent of this check is to avoid naming confusion between default and custom modules to content creators/marketers and to provide clear differentiation for our default modules. While I agree with #3 in the community post that after developers hide the theme modules, they should be able to name the custom modules as per their choice, there would still be confusion when the modules are being referred. After discussing with our internal team,  we think it would be best to keep the naming distinct for custom and default modules.

I would also take this opportunity to let you know that the theme modules categorization has been added back to the menu. Pls check it out!

[HariniSam]

Thank you for your feedback! Your feedback is important to us and helps us improve our services/products.   

The intent of this check is to avoid naming confusion between default and custom modules to content creators/marketers and to provide clear differentiation for our default modules. While I agree with #3 in the community post that after developers hide the theme modules, they should be able to name the custom modules as per their choice, there would still be confusion when the modules are being referred. After discussing with our internal team,  we think it would be best to keep the naming distinct for custom and default modules.

I would also take this opportunity to let you know that the theme modules categorization has been added back to the menu. Pls check it out!

[HariniSam]

Thanks ANisar for your feedback on the overall theme guidelines. We will discuss this with the internal team and our team will get back to you.

[mii]

theme.json: hidden_modules
I agree with point 3. Support for custom module paths, for example to deactivate Parant-Theme modules in Child-Themes.