Replies: 2 comments
-
This one and issues #1240 , #1243 actually overlap with some new features we are looking into implementing some time soon-ish. So thank you for raising these (and especially for the POC), we'll revisit them later to see how it all fits together. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@art-alexeyenko Sounds great! Is there anything I can do to make my POCs and PRs more useful? Are there other things, areas, features, etc that I can work on? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
When developing enterprise websites, it is a requirement to share components across sites while allowing some components to implement unique styling on a brand theme or specific site basis.
Describe the solution you'd like
Add the ability for components to have a site or theme specific implementation. This allows for a single codebase to be deployed multiple times supporting multiple sites, while connecting to a single Sitecore CMS instance.
Describe alternatives you've considered
Use a monorepo approach with multiple NextJS apps and a shared component library. This solves the problem, but creates other problems. Using NPM workspaces to access the shared component library breaks running the NextJS apps in docker, because the symlink isn't supported.
Additional information
Beta Was this translation helpful? Give feedback.
All reactions