Before you start, ensure you've done the following:
Create a free test account to build without impacting a production environment. You can use either of the following types of accounts:
Create a developer account, then create a test account within it. Because you can also build private apps in developer test accounts, along with building public apps in developer accounts, you'll have one home for both CMS and app development.
Developer accounts and their associated test accounts aren’t connected to a standard HubSpot account, and they can’t sync data or assets with another HubSpot account.
So anything I make in the developer account is stuck in this portal, and can never be used in my real account?
HubSpot's language in the documentation says this needs to be done before I begin, yet everything I'm reading says this will lock me out of using what I make.
Do I need a developer account to build custom modules, themes, and templates for my HubSpot account or not?
Yes, I can see that the way it is laid out is a little confusing.
In short, it is not a requirement to create a test account. The main purpose of this test account is to have a space where you can experiment without impacting your live website. As the article states: "Create a free test account to build without impacting a production environment."
Additional benefit is that you have access to play around with some tools that are available at Pro/Enterprise tiers - if you want to see whether that would be useful in your own portal.
To answer your question whether everything you make is stuck in this test portal - not necessarily. While you can't simply transfer a theme from one portal to another, you can still build one in the free test portal, then copy the assets to the folder where you have your main HubSpot account connected and use the "hs upload" command to have that appear in your main portal.
Again, this is an optional step which you can skip and you can connect directly to your existing HubSpot account.
Hope this helps!
✔️ Did this post help answer your query? Help the community by marking it as a solution.
Yes, I can see that the way it is laid out is a little confusing.
In short, it is not a requirement to create a test account. The main purpose of this test account is to have a space where you can experiment without impacting your live website. As the article states: "Create a free test account to build without impacting a production environment."
Additional benefit is that you have access to play around with some tools that are available at Pro/Enterprise tiers - if you want to see whether that would be useful in your own portal.
To answer your question whether everything you make is stuck in this test portal - not necessarily. While you can't simply transfer a theme from one portal to another, you can still build one in the free test portal, then copy the assets to the folder where you have your main HubSpot account connected and use the "hs upload" command to have that appear in your main portal.
Again, this is an optional step which you can skip and you can connect directly to your existing HubSpot account.
Hope this helps!
✔️ Did this post help answer your query? Help the community by marking it as a solution.
