When fields are unique in multiple data templates

When fields are repeated in single data templates

When fields are repeated in multiple data templates

When field types are repeated in multiple data templates

You need the Experience Database to take full advantage of the available features. It supports the Analytics and Marketing features.

You need nothing additional

You need the Experience Database to take full advantage of the available features. It supports the Analytics and Marketing features.

To define default values for templates

Define fields that Sitecore uses internally but are not shown to the user

To define some fields you will need in all your pages: title, text, keywords, etc.

To define the overall structure of your page

Sitecore will remove these fields into the same field section

Sitecore will merge these fields into the same field section

Sitecore will edit these fields into the same field section

Sitecore will merge these fields into the different field section

In App-Config/Conclude folder, where folders and files are loaded alphabetically

Through IIS Settings

In App-Config/Include folder, where folders and files are loaded alphabetically

Cant be controlled

Sitecore Rocks

Installation wizard/ Control Panel

Both

Only B Option

field definition

field section

field source

data type

Dynamically bind it when you need it to always appear on a layout or rendering.

Statically bind it when you need it to always appear on a layout or rendering.

None

Allow editing content in a sandbox without affecting the content on the live site

To be able to have multiple servers delivering your live site content

To make version upgrades much easier

To separate your own configuration from the standard one that comes with Sitecore

Integration with Visual Studio

Creating and editing items

viewing website file system

All

Html.Sitecore().FormHandler()

Html.Sitecore().ValidateHandler()

Both

None

web

master

core

All

You will get two fields with the same name, which leads to confusion both to users and developers. It should be avoided.

You will get two fields with the same name, which leads to confusion both to users and developers. It should not be avoided.

You will get one fields with the same name, which leads to confusion both to users and developers. It should be avoided.

None

Image

Text

Rich Text Field

All

Name

Template

Location (parent node)

All

Instead of returning a null field value, it will check if the same field in the Standard Value item has a value and then it'll return that value.

Error

403

500 Internal Error

Content Editor

Experience Editor

Control Panel

All

merges fields from all inherited templates

All templates inherit from Standard Template

contains fields that define system properties (like presentation details) and modifying the Content Base template will affect all the items immediately

All

By creating some definition items in the Core db by adding the buttons property to the Field Editor

By creating some definition items in the Master db by adding the buttons property to the Field Editor

By creating some definition items in the Web db by adding the buttons property to the Field Editor

All