I would suggest different approach because yours might be vulnerable to SXA updates (custom dialog might miss some functionalities).
Instead I recommend extending existing scaffolding.
When you open New-Site dialog you can see modules/features section.
It lists all the modules that will be installed during site scaffolding operation (examples: Page Content, ...
It looks like you are using two different indexes and expect the same results.
Compare translated search queries and pay attention to _indexname field.
This is unfortunate but queries in Build Search Query dialog are executed against Sitecore index, while these in Preview/Publish (in SXA context) will use SXA indexes.
There is no good solution/hotfix for ...
You are missing variants definitions for your rendering.
To fix it you have to create Rendering Variants folder under your site
Use your custom rendering name as its name just like other RV enabled renderings do and you should see them in rendering parameters dialog.
If it will be something different you can debug it ...
It is possible if you adjust insert rules, scaffolding... but that would require quite some effort and so I would like to suggest a different approach.
SXA has the functionality of site cloning. This means you create one "base" site with all the pages and settings as you want in the ecommerce site. Each time you want to create such a new site ...
From what I can tell, all the guids are lowercases in Solr.
I don't know how you built your query, but I saw it in the past that query didn't work if guids where not lowercases in Solr query.
If you still ...
You can send Sitecore Items in .Net Class with Scheduler items and within the scheduler, you can access those items and perform your functionality.
In the Scheduler task, you need to specify the Sitecore item in the Items field. If you want to pass a single item, then you can write either Item GUID or Path of that Item. In case if you want to pass multiple ...
I understand that you are talking about SXA/JSS sites, right?
If yes, then I'm surprised that it works for the Rich Text fields. We've never migrated content tokens to SXA/JSS sites, you won't find the Content Token field under a data for such site:
Implementation details: Sitecore.XA.Feature.ContentTokens.Pipelines.RenderField.RenderContentToken
This is a limitation of OOTB Tag cloud (sxa 93), also noticed this was not corrected in sxa10 as well.
Clone the SXA TagCloud component and override TryQueryFacet from TagCloudRepository (Sitecore.XA.Feature.Taxonomy.Repository.TagCloudRepository) to make the query aware of the context Item language.
protected override bool ...
Even though you have two partial designs, SXA works on how the Page Design is rendered. So in Page Design, you can add 2 base partial designs.
The first Partial design has logo and navigation
The second partial design has only breadcrumb
and make sure the order is correct in the page design selection.
Not possible with OOTB Navigation as you already discovered, however I had a similar scenario where I cloned the SXA Navigation to render Nav Items based on a data source which gives some flexibility to control Nav Items from outside Home.
Clone the OOTB Navigation
Override GetModel (Sitecore.XA.Foundation.RenderingVariants.Repositories)
public override ...