Search Results

One approach you could take, if you are using MVC, is an approach we used to take in multisite a few years ago. You can create a new View Engine for MVC and make it check for Project sites first. ~/V …

If your multisite Habitat solution is using a single IIS site, per the current license model. Then all the web projects (Feature/Foundation/Project) are batched into a single package. That is how we a …

If the two features are so different they need a different view and controller, then they are not the Same feature. Just create the feature in each project layer. If you would like to create a model …

DI Approach We do exactly what you do. We have a dependency injection Foundation project that holds all the bits from Kamsar's post. Then I pull it all in with a config patch. <sitecore> <serv …

I think your best answer here is to use a coded datasource for the speaker field in feature template. And in that code define some vague logic of where the speaker list will be located. i.e. $site/Sit …

You will need to either build this search functionality at the project level, thus being able to see all the feature templates. Or you can move the field you want to search, like Title or Abstract, to …

Just make sure you don't make a view that has logic in it to determine what kind of data you are dealing with. You can have one view that shows generic data, but you need to make sure that your Empl …

Sitecore's dependency injection was introduced in Sitecore 8.2. It appears you are using 8.1.

If the difference between each brand is just UI related, I would put a put a new search view, for each brand, in the project level. And use the data model and services from the feature level. If you …

Anything in the project layer CAN call anything in the foundation & feature layers. And since you could potentially make a feature that would also want to use the rendering parameters functionality, y …

I tried to find a commit when Habitat when it used to be TDS (https://github.com/Sitecore/Habitat) to no avail. But what you want to do is create a TDS project for each Feature/Foundation/Project. In …

With transparent sync, the file system becomes the record for Sitecore. It treats the file system like the master database. For items and children that are monitored by transparent sync, if you create …

What you want to do is take advantage of Sitecore's branching functionality. A branch in Sitecore is basically a prebuilt item tree that will be copied and inserted where you want it. It could be one …

We have not gone into the full editing experience, but we use APIs with security tokens to do work in Sitecore. Then use Ghost inspector to analyze the work. Whether it is a visual pixel by pixel scre …