Sitecore item DisplayName is valid used as a page title
up vote
0
down vote
favorite
We are working on Sitecore application. There is our vendor team is using sitecore item DisplayName as a page title. As per my knowledge this is wrong approach. But i need your help please give me a strong reason i can prove this approach is wrong.
If this is right way then please suggest that also.
Thanks in advance.
sitecore sitecore8 sitecore7 sitecore7.2
add a comment |
up vote
0
down vote
favorite
We are working on Sitecore application. There is our vendor team is using sitecore item DisplayName as a page title. As per my knowledge this is wrong approach. But i need your help please give me a strong reason i can prove this approach is wrong.
If this is right way then please suggest that also.
Thanks in advance.
sitecore sitecore8 sitecore7 sitecore7.2
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We are working on Sitecore application. There is our vendor team is using sitecore item DisplayName as a page title. As per my knowledge this is wrong approach. But i need your help please give me a strong reason i can prove this approach is wrong.
If this is right way then please suggest that also.
Thanks in advance.
sitecore sitecore8 sitecore7 sitecore7.2
We are working on Sitecore application. There is our vendor team is using sitecore item DisplayName as a page title. As per my knowledge this is wrong approach. But i need your help please give me a strong reason i can prove this approach is wrong.
If this is right way then please suggest that also.
Thanks in advance.
sitecore sitecore8 sitecore7 sitecore7.2
sitecore sitecore8 sitecore7 sitecore7.2
asked Nov 17 at 10:45
satnam singh
137
137
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
As opposed to using item Name
(which has a lot of restrictions, like disallowed characters and not being able to have different values per language), using DisplayName
for page title can, in fact, be a good choice, for the following reasons:
- It can be any UTF8 string, which helps with internationalization of the site
- It can have different values per language.
- DisplayName can be used for url->item resolutions, which would result in having your title as a part of the url. This is beneficial both for SEO and for user-friendliness of your urls.
The only possible downside is the fact that DisplayName
field is unversioned, which means that you won't be able to have different values per item version.
add a comment |
up vote
0
down vote
There is nothing inherently 'wrong' in using the Display Name of an item for a page title. As @Piotr Wicijowski mentions, it is better than using the item name. The Display Name can also be used for different languages, unlike the item name.
However, there are a few issues (in addition to Piotr's post) with using Display Name as the page title:
No personalization. A separate datasource would be needed on the component in order to support personalization of the page title. It is very uncommon to personalize the page title, however, so this is not a big issue.
Impacts Content Editor. The Content Editor interface will show the display name in the hierarchy of the content tree. This can be helpful that the user will see a page title in the content tree, but sometimes page titles can be quite long and you may want a shorter name in the content tree.
Impacts Multilingual URLs. In order to support different URLs in different languages, I have always enabled the links to be generated using display name and then provide the proper link value in the display name. A link is not always the text you want to display as the page title.
On the flip side, there are some benefits to using the Display Name:
- Easy for content editors to find (ribbon button already there in content editor)
- Shows up in the Content Editor for easy seeing of page titles
- No template customization of Sitecore required to add new fields
- Less code required to model custom fields
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As opposed to using item Name
(which has a lot of restrictions, like disallowed characters and not being able to have different values per language), using DisplayName
for page title can, in fact, be a good choice, for the following reasons:
- It can be any UTF8 string, which helps with internationalization of the site
- It can have different values per language.
- DisplayName can be used for url->item resolutions, which would result in having your title as a part of the url. This is beneficial both for SEO and for user-friendliness of your urls.
The only possible downside is the fact that DisplayName
field is unversioned, which means that you won't be able to have different values per item version.
add a comment |
up vote
0
down vote
As opposed to using item Name
(which has a lot of restrictions, like disallowed characters and not being able to have different values per language), using DisplayName
for page title can, in fact, be a good choice, for the following reasons:
- It can be any UTF8 string, which helps with internationalization of the site
- It can have different values per language.
- DisplayName can be used for url->item resolutions, which would result in having your title as a part of the url. This is beneficial both for SEO and for user-friendliness of your urls.
The only possible downside is the fact that DisplayName
field is unversioned, which means that you won't be able to have different values per item version.
add a comment |
up vote
0
down vote
up vote
0
down vote
As opposed to using item Name
(which has a lot of restrictions, like disallowed characters and not being able to have different values per language), using DisplayName
for page title can, in fact, be a good choice, for the following reasons:
- It can be any UTF8 string, which helps with internationalization of the site
- It can have different values per language.
- DisplayName can be used for url->item resolutions, which would result in having your title as a part of the url. This is beneficial both for SEO and for user-friendliness of your urls.
The only possible downside is the fact that DisplayName
field is unversioned, which means that you won't be able to have different values per item version.
As opposed to using item Name
(which has a lot of restrictions, like disallowed characters and not being able to have different values per language), using DisplayName
for page title can, in fact, be a good choice, for the following reasons:
- It can be any UTF8 string, which helps with internationalization of the site
- It can have different values per language.
- DisplayName can be used for url->item resolutions, which would result in having your title as a part of the url. This is beneficial both for SEO and for user-friendliness of your urls.
The only possible downside is the fact that DisplayName
field is unversioned, which means that you won't be able to have different values per item version.
answered Nov 18 at 12:48
Piotr Wicijowski
2264
2264
add a comment |
add a comment |
up vote
0
down vote
There is nothing inherently 'wrong' in using the Display Name of an item for a page title. As @Piotr Wicijowski mentions, it is better than using the item name. The Display Name can also be used for different languages, unlike the item name.
However, there are a few issues (in addition to Piotr's post) with using Display Name as the page title:
No personalization. A separate datasource would be needed on the component in order to support personalization of the page title. It is very uncommon to personalize the page title, however, so this is not a big issue.
Impacts Content Editor. The Content Editor interface will show the display name in the hierarchy of the content tree. This can be helpful that the user will see a page title in the content tree, but sometimes page titles can be quite long and you may want a shorter name in the content tree.
Impacts Multilingual URLs. In order to support different URLs in different languages, I have always enabled the links to be generated using display name and then provide the proper link value in the display name. A link is not always the text you want to display as the page title.
On the flip side, there are some benefits to using the Display Name:
- Easy for content editors to find (ribbon button already there in content editor)
- Shows up in the Content Editor for easy seeing of page titles
- No template customization of Sitecore required to add new fields
- Less code required to model custom fields
add a comment |
up vote
0
down vote
There is nothing inherently 'wrong' in using the Display Name of an item for a page title. As @Piotr Wicijowski mentions, it is better than using the item name. The Display Name can also be used for different languages, unlike the item name.
However, there are a few issues (in addition to Piotr's post) with using Display Name as the page title:
No personalization. A separate datasource would be needed on the component in order to support personalization of the page title. It is very uncommon to personalize the page title, however, so this is not a big issue.
Impacts Content Editor. The Content Editor interface will show the display name in the hierarchy of the content tree. This can be helpful that the user will see a page title in the content tree, but sometimes page titles can be quite long and you may want a shorter name in the content tree.
Impacts Multilingual URLs. In order to support different URLs in different languages, I have always enabled the links to be generated using display name and then provide the proper link value in the display name. A link is not always the text you want to display as the page title.
On the flip side, there are some benefits to using the Display Name:
- Easy for content editors to find (ribbon button already there in content editor)
- Shows up in the Content Editor for easy seeing of page titles
- No template customization of Sitecore required to add new fields
- Less code required to model custom fields
add a comment |
up vote
0
down vote
up vote
0
down vote
There is nothing inherently 'wrong' in using the Display Name of an item for a page title. As @Piotr Wicijowski mentions, it is better than using the item name. The Display Name can also be used for different languages, unlike the item name.
However, there are a few issues (in addition to Piotr's post) with using Display Name as the page title:
No personalization. A separate datasource would be needed on the component in order to support personalization of the page title. It is very uncommon to personalize the page title, however, so this is not a big issue.
Impacts Content Editor. The Content Editor interface will show the display name in the hierarchy of the content tree. This can be helpful that the user will see a page title in the content tree, but sometimes page titles can be quite long and you may want a shorter name in the content tree.
Impacts Multilingual URLs. In order to support different URLs in different languages, I have always enabled the links to be generated using display name and then provide the proper link value in the display name. A link is not always the text you want to display as the page title.
On the flip side, there are some benefits to using the Display Name:
- Easy for content editors to find (ribbon button already there in content editor)
- Shows up in the Content Editor for easy seeing of page titles
- No template customization of Sitecore required to add new fields
- Less code required to model custom fields
There is nothing inherently 'wrong' in using the Display Name of an item for a page title. As @Piotr Wicijowski mentions, it is better than using the item name. The Display Name can also be used for different languages, unlike the item name.
However, there are a few issues (in addition to Piotr's post) with using Display Name as the page title:
No personalization. A separate datasource would be needed on the component in order to support personalization of the page title. It is very uncommon to personalize the page title, however, so this is not a big issue.
Impacts Content Editor. The Content Editor interface will show the display name in the hierarchy of the content tree. This can be helpful that the user will see a page title in the content tree, but sometimes page titles can be quite long and you may want a shorter name in the content tree.
Impacts Multilingual URLs. In order to support different URLs in different languages, I have always enabled the links to be generated using display name and then provide the proper link value in the display name. A link is not always the text you want to display as the page title.
On the flip side, there are some benefits to using the Display Name:
- Easy for content editors to find (ribbon button already there in content editor)
- Shows up in the Content Editor for easy seeing of page titles
- No template customization of Sitecore required to add new fields
- Less code required to model custom fields
answered 2 days ago
Jay S
6,98222946
6,98222946
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53350453%2fsitecore-item-displayname-is-valid-used-as-a-page-title%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown