Serving different content for different domains
SOLVE
1 Accepted solution
Serving different content for different domains
SOLVEI see, yes you are right.
If you are in the situation where using a common partial/global module or group across different domains/brands or whatever is the case. I like to use a method I figured out a few years ago. You can check it here:
The idea is to use the slug variable to filter over the content and display the right one.
Now, for the module where you want to save all the content variations, you will create a repeatable group (I use it with the internal key lang) and a required simple text field with the key lang_slug that will save the value of the slug to compare with (string_startingwith).
Then you will add as many fields needed for the content to be filtered.
This case assumes the lang propose and uses for example en/ es/ etc as the lang_slug code values. In your case, you want to swap the slug variable for the domain check (for example content.resolved_domain) and use the lang_slug values that match it.
If you have more questions and you are in the dev slack, I am happy to guide you.
If this answer helps you to solve your questions please mark it as a solution.
Thank you,
|
Serving different content for different domains
SOLVEHi there,
It will depend on what do you exactly want to achieve, where to place that and if it will be language-dependent.
For example, if you want to use those domains to split the content based on the language, Hubspot provides a lot of tools to create page variations, including the global header & footer.
It would be completely different and complex if you have several brands serving common languages. And will require custom development to achieve it.
If you can provide some extra info about what are you trying to achieve I am happy to guide you.
If this answer helps you to solve your questions please mark it as a solution.
Thank you,
|
Serving different content for different domains
SOLVEServing different content for different domains
SOLVEI see, yes you are right.
If you are in the situation where using a common partial/global module or group across different domains/brands or whatever is the case. I like to use a method I figured out a few years ago. You can check it here:
The idea is to use the slug variable to filter over the content and display the right one.
Now, for the module where you want to save all the content variations, you will create a repeatable group (I use it with the internal key lang) and a required simple text field with the key lang_slug that will save the value of the slug to compare with (string_startingwith).
Then you will add as many fields needed for the content to be filtered.
This case assumes the lang propose and uses for example en/ es/ etc as the lang_slug code values. In your case, you want to swap the slug variable for the domain check (for example content.resolved_domain) and use the lang_slug values that match it.
If you have more questions and you are in the dev slack, I am happy to guide you.
If this answer helps you to solve your questions please mark it as a solution.
Thank you,
|
