Guides RFC - #3 Multisite Scenarios

Sitecore / jss

Software development kit for JavaScript developers building web applications with Sitecore Experience Platform

https://jss.sitecore.com

Apache License 2.0

261 stars 273 forks source link

Guides RFC - #3 Multisite Scenarios #434

Closed anastasiya29 closed 2 years ago

anastasiya29 commented 4 years ago

RFC background

We have published the 1st version of JSS Guides & Recommended Practices. This content will ultimately be merged into the JSS Documentation site, and we'd love for the community to be a part of this milestone. We welcome your feedback, questions, change suggestions, and additional content.

Category - Multisite Scenarios

We’ve create GitHub issues for the 7 topic categories to facilitate group discussion - this issue is for discussing the Multisite Scenarios category.

Topics in this category:

How to contribute

Post your comments here, or
Use this link to leave inline comments in the markdown files, or
Use the Edit this on GitHub link at the bottom of each guide page to submit edits for specific pages, or
Submit pull requests to the guides branch

:arrow_left: Go to previous category ----- Go to next category :arrow_right:

nickwesselman commented 4 years ago

Some thoughts:

Nothing here on use of a single app/bundle for multiple sites, which we get asked about and some have implemented. Is there any community content on this? Or should we just discourage?
Content patterns and discussion of shared content was confusing to me, because it seems to be more about shared design elements.
That said, should we point people to Helix guidelines w/r/t how to structure your templates and renderings to be shared between sites, particularly if not using SXA?
Microsites under the same domain is confusing to me, not sure what this use case is... does it mean the same domain for the Layout Service call? In that case it's not just about Micro sites right?

8or15 commented 4 years ago

The challenge is that from the code side, each app only sees it’s own code, so achieving actual sharing capabilities requires some customization.

The fact that applications only can reuse their own code is quite a difference coming from the traditional .NET development with Sitecore (not headless). Although this is mentioned it would be great to put more emphasis on this, as it requires a slightly different thinking for the Sitecore veterans. Perhaps more visual examples would be beneficial.

stale[bot] commented 2 years ago

This has been automatically marked as stale because it has not had recent activity. It will be closed if there is no further activity within 30 days. You may add comments or the 'keep' label to prevent it from closing. Thank you for your contributions.