23

There isn't a way - really. Not an out-of-the-box one, anyway. To achieve it; Sitecore would need to record a delta of item changes - which it doesn't. Remove a rendering - Sitecore removes it; but leaves no paper trail of the event. What you're asking for is akin to what Item Clones does - except that it does not keep track of an entire item structure, ...


18

In my opinion, these are the scopes you need to consider: Global (across multiple sites) Site (across an entire site) Pillar/Section (used across an entire subtree of a site) Page (Used only on this page) Using only one location does not allow you to scope your security appropriately for your authors. If you have a single global folder, that means giving ...


13

Both options are valid and more of a principal discussion. As the page hasn't ever existed, a 301 redirect (moved permanently) may not be the right option, but from a user perspective, the /about may (or may not) be redirected to most important item under that group. a 404.0 (page not found) may the better option from a principal perspective, as, the page ...


12

I could get up on a soap box and speak for days on this. In fact I have. The Page Template Mistake. The role of Information Hiding The first concern you must address (from my viewpoint) is: You need to separate this decision making from your actual code build. Or put differently: Your components should make as few assumptions about the Information ...


10

You don't actually need a package - Sitecore gives you this ability out of the box. What I normally do is; I have a "global" area, and a "page local" area for datasource content. The way you set it up, is to go to your "Datasource Location" field on your rendering definition, and pipe | the different data sources - one of them bing relative to your context ...


9

If your items do not have any layout then they should throw a 404 error. You can update the LayoutNotFoundUrl setting to match your 404 page on your site so that the user is presented with a friendlier looking error page than the default Sitecore one: <setting name="LayoutNotFoundUrl" set:value="/url-to/404" /> Using this setting there is no need to ...


9

It is too much information to provide in one answer or one article. I can suggest you to start with this diagram created by David Morrison(I have added only few things related to Sitecore Analytics): Diagram is actual for Sitecore 7. But in a way, how page is rendered, not too much changed in Sitecore 9. So, it can be good starting point. Processor and ...


8

Yes that is possible. I created two sites in one sitecore instance. One is SXA based and the other one is on Habitat. These sites are on Sitecore 8.2 update-3 instance with SXA 1.3. As such there wasn't any conflict other than the controller name that should be different from the SXA components for example if you need to build an accordion then the ...


8

While a very detailed question, there are still quite many "it depends" open ends. I'm going to make some assumptions based on experience, and give you my view. I'll start by shaking the box to try and do some outside thinking ;-) Shaking the box You don't really want to do page level personalisation on 100k scaling to 1m product pages. You want to do it ...


8

Some concerns that I always take in to consideration when designing architecture and templates, and where the content should live. Reusability - Is this content going to be used on more than one page? Some examples such as call to action boxes, focus areas, blurbs, descriptive copy about categories in the site, and so on. If the content is likely to be ...


6

You are correct. The master database contains all versions of any given item per language. In normal senario and before sitecore 8.1, The web database only contains a single version of each item, per language. But, from sitecore 8.1 onwards, there is a scenario where multiple versions of a single item can exist. i.e. when item have an Active Test ...


5

In the past I would have advocated for using a single place to store blocks of content used as data sources. It makes administration easier including things like access rights and it keeps the "page tree" clean. Today I think a little differently. Since Sitecore 7 and the introduction of the new Content Search and bucket folders, I'm often inclined to ...


5

As already mentioned in the answer from Mark Cassidy, this is available "out of the box" with Sitecore. You need to watch out for the fact that the folders need to exist though. One way to ensure this is to use Branch Templates, but this can become quite become quite difficult to manage if you have a lot of different templates. An alternative is to ...


5

As we don't (yet) know which example you have in mind, I'll give my general opinion: although it is best practice to use datasources, it might not be best practice to use them for everything. Your content editors could go completely crazy if they need to quickly publish a news article and they need to create 5 datasources and a content item to achieve that (...


4

Did some consultancy a few years ago in the travel business - they pushed their data into Sitecore but I'm quite sure they would never do that again.. I would try to go for a hybrid solution where you store some information in Sitecore and keep some (or a lot) in the PMS only. To decide what to sync I would consider: try to keep as much "pages" as ...


4

Without SXA I would build this as a single feature with 4 components, all based off the same data template. Create a template that contains all the fields you require. Lets call it ImageCallout Create 4 renderings that have the razor setup to the 4 different styles that you have specified. They should all use your ImageCallout template as the datasource for ...


4

I know that this is an old post, but I was looking through and just wanted to add some information to help anyone who is actually still hoping to implement similar behavior to this. At a high-level, @MarkCassidy is correct that there is no OOTB mechanism for what you are describing. However, you could achieve a limited version of this functionality by ...


4

Turns out the guys over at SPE though through some of this too. Hopefully others find this answer helpful. Here's a page describing how to manage item languages. Example: The following will query all the items under home and add copy US english to CA english; skips if the language already exists. $root = "master:\content\home" @(Get-Item -Path $root) + @(...


3

For bulk, I'm sure someone skilled in Sitecore Powershell Extensions has an answer. I will give you another approach however. In my most recent project; we implemented the Content Editor and Experience Editor authoring language extensions by Mikael Högberg. Essentially they expand upon the regular warning ribbons in Sitecore, to look something like this: ...


3

Pros and cons of both Interesting article the other day where can use both. http://sitecorecode.com/index.php/2016/09/19/how-to-give-multiple-datasource-locations-to-single-sublayout-or-rendering-in-sitecore/ If under each item then clear what it belongs too, no surprises when update it and only affects that page. If in a repository then promotes idea ...


3

If you want to avoid having to create the folder ahead of time (either in a tenant folder or a relative path), you can tap into the getRenderingDatasource pipeline. The solution I've used for some time now checks if the datasource location is a relative path, and then checks if that path exists under the context item before creating it. A parameter on the ...


3

You have more options and they depends mainly on the requirements Option 1 You can have all fields in 1 template and then depends on the filled fields in preview and normal mode which should be shown, but you show all as editable in Experience Editor. This is a good solution if you want editors to able to change the content dynamicly and you want to use ...


3

This is a similar discussion I've been considering on something we are currently building. Typically another scenario is adding data directly to the Product item for them to configure and then you would pull using the context item. Although in that approach you would also still want a datasource reference, so that things could be personalized or A/B tested ...


3

From the experience I have with Sitecore, we have rolled out 70+ sites on sitecore. Below are the following points/practice we usually follow when implementing our sites. Content Sharing You may have a main content repository which stores all the common content for the different sites. Contents that are specific to a site are created under the site node. ...


3

This is called "Local Datasources" Essentially it is a way to help prevent massively bloated shared folders for content that really only appears on the page in question. It is (mostly) supported out of the box in Sitecore, with only a few minor UI adjustments required for a good experience. One example here: Local Datasources module for Sitecore ...


2

Martin Davies started an overview of the request pipelines (in SC8) on is blog: http://sitecoreskills.blogspot.be/2015/02/a-sitecore-8-request-from-beginning-to.html It gives an overview of the pipelines and pipeline steps. Some are already linked to detail pages (still some work to do to get full coverage but that is a lot of work). I found this article ...


2

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> <services> <configurator type="Sitecore.Foundation.DependencyInjection.ServicesConfigurator.DiConfigurator, Sitecore.Foundation....


2

I have done some similar solutions in the past – and I would suggest that you integrate the data into Sitecore, but create a custom Sitecore DB (without publishing) to hold the data. Also consider using a “brand” field on templates, to filter which brands has access to certain items, so you enable the solution to share content/products between the different ...


2

From what I understand, your content tree looks something like this: Sitecore |_Content |_Home | |_News | |_News1 Page |_SharedContent |_News |_News1 Content This can be a viable way to organise things, but I would only go this route if you really need to and get some real benefit from doing so i.e. if you have a multi-site solution and ...


2

One way to handle this is to define a template or a field called something like "Exclude from URL" and then use a custom link provider and item resolver to skip these items when generating links and resolving requests. To correctly resolve items with this approach you do need to store the custom URLs somewhere though. One traditional approach is to store ...


Only top voted, non community-wiki answers of a minimum length are eligible