New answers tagged

0

jss create command by default pulls application template from master branch from JSS github repo (which contains the latest version). To override this behaviour you can use jss create -b or jss create -s switch: -b is to select application template from specific branch from JSS github repo, -s is to use local folder with JSS application template (which you ...


1

I will try to answer to @Jeeby's questions: did you go with SXA?--->No (it may be possible but we haven't use it) How did it work out for you? ---> We ended up with a single JSS App and 3 sites under /sitecore/content with common components outside of them under one Universal folder. Sitecore Support helped us with sharing components between sites, ...


0

JSS does not alter the SQL database schema. Sitecore modules rarely, if ever, do. It does install a number of items and alters permissions on /sitecore/content. It does not directly alter the Solr indexes, but the managed schema may be updated based on the additional templates and items included in the JSS module.


1

TL;DR I think you forgot to extend Page template with appropriate field (_Sitemap) Current status Right now SXA (10 and lower) doesn't support officially Sitemap feature in JSS sites. There is no feature parity between SXA and JSS. Both are technically separate types of sites which have different set of scaffolding actions. You can compare what modules/...


0

I saw the same error while doing import. Just make sure config file name '/sitecore/config/*.config' matches to your site's 'name' property in config. For ex. /sitecore/config -> **sitecore-jss**.config And inside config: <site patch:before="site[@name='website']" inherits="website" **name="sitecore-jss&...


Top 50 recent answers are included