You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the suggested/best strategy for the front-end head project to work with headless CMS backend hosting multiple sites?
Assumption:
all sites will share most of the blocks.
all sites will share the most of the business logic.
each site will have different content and assets (but some may be shared).
each site will have a different theme (most of the CSS will be totally different).
Which approach is possible and recommended?
Bundle everything into one Next application and choose different CSS theme on runtime based on domain/site setting. This might lead to unused CSS, but on the other hand there is only one front-end app deployed to hosting provider (like DXP) so the setup is simple.
Customize bundling of Next application, so during build time only selected CSS theme will be bundled into build package. This would be more optimal from lighthouse score perspective, but it would require multiple front-end apps built and deployed to hosting provider. Would DXP support it? (assuming some adjustments to headless proxy).
Have different front-end code for each site (I guess this would be overkill if the only difference between sites is CSS theme, in terms of the deployment and hosting it will similar in the end to point no.2).
Other approach?
The text was updated successfully, but these errors were encountered:
What is the suggested/best strategy for the front-end head project to work with headless CMS backend hosting multiple sites?
Assumption:
Which approach is possible and recommended?
The text was updated successfully, but these errors were encountered: