[opencms-dev] R: Re: Detail pages
gnorrus at libero.it
gnorrus at libero.it
Tue Jul 24 15:52:05 CEST 2012
Hi Alex
Your answer is clear, but I have some other questions about detail page.
Why the url of the resource is not lowercase?
I mean, in your example "Some-great-title". The first letter is uppercase, like the resource title. Is it possibile to have it lowercase? If not, do I have to create another field inside xsd where put the "SEO title" so the user can write it lowercase?
The other question is about the position of the detail page.
Imagine this site structure:
- products
|- Type A
|- Type A1
|- Type A2
|- Type A3
|- Type B
|- Type B1
|- Type B2
|- Type B3
If I use categories I can have all produts categorized in the right way and I can display them inside List content in the right way
But if i have a page where I should have the list of all products of Type A + Type B (and this page is inside products folder), where do I have to put the
detail page?
If I put inside Type A folder, also product of type B will have this url:
/products/TypeA/product-name and this is not correct.
In this case I should have another detail page inside products folder in order to have urls like this:
/products/product-name. But, with sitemap, the detail page is created always inside a folder, so I would have /products/product/product-name.
This is not a good solution (expecially for SEO).
The detail page is named always index.html, so If i move the detail page inside products folder (having the correct url: /products/product-name) i can't have a index.html page that is the list of all products (i should name it for example "list.html"), because if i try to rename the detail page, then i get an error when clicking on one product in the list (resource not found)
So in this case I must create 3 detail pages, one inside products folder to display all products of type A and B, then another one inside Type A folder and another one inside Type B folder. But also this is not good for SEO, because in this case the same content is reachable with different urls (/products/product-name, /products/TypeA/product-name)
And I can go on creating other detail pages inside every other child folder i create in order to have, for example:
/products/TypeA/TypeA1/product-name etc...
which is the right way to use detail page in this case?
Thanks
----Messaggio originale----
Da: alex at opencms.org
Data: 24-lug-2012 14.58
A: "The OpenCms mailing list"<opencms-dev at opencms.org>
Ogg: Re: [opencms-dev] Detail pages
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Verdana","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
@list l0
{mso-list-id:1164588791;
mso-list-type:hybrid;
mso-list-template-ids:805976482 67567631 67567641 67567643 67567631 67567641 67567643 67567631 67567641 67567643;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
->@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Verdana","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
@list l0
{mso-list-id:1164588791;
mso-list-type:hybrid;
mso-list-template-ids:805976482 67567631 67567641 67567643 67567631 67567641 67567643 67567631 67567641 67567643;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
->
-->Andy, sorry we have no better guide at the moment but maybe I can help explain the broad concept. The container page you got pretty correct. Basically the container page allows you to combine several pieces of content in one page. This is suitable for all pages that make up the main navigation. All container pages are therefore managed “by hand” in the OpenCms sitemap. Now think of a “News ticker”. The individual news messages are usually not part of the main navigation / sitemap. That is where the detail page comes into the picture. You define one page as the detail page for a specific piece of content, e.g. the “News detail page”. This detail page has a place in the sitemap. So all individual news messages are automatically displayed using this detail page, and their URL is calculated automatically. The mechanism that shows the news on the detail page is in pretty much the same as on a standard container page, with the difference that the content for this specific container is selected dynamically and not by hand. What I'm unclear on is when I use an internal link to a specific piece of content, where this goes to, what's loaded, and the use of detailpages to provide a specific formatting/template/rendering for all resources of the same type. Let’s say you have a content type “News”, and this has the URI /.content/news/news_00012.html in OpenCms. If you directly link to this content in OpenCms 8, then the following happens: 1. OpenCms recognizes that you are in an OpenCms 8 ADE enabled sitemap.2. Depending on the sitemap you are currently in, it will look up the configured detail page for news. Let’s say this detail page has the path “/news/”.3. OpenCms will now generate a link, based on the path of the detail page and the mapped title of the news. Let’s say the title of the news was “Some great title”, the so the link created would be “/news/Some-great-title/”.4. When this link is followed in the browser, OpenCms recognizes that “/news/” is in fact a detail page, and will then load the news based on the rest of the URL “/Some-great-title/”. For this there exists a title-to-id mapping table in OpenCms 8.5. In the template used for the detail page you need to specify the container for the detail view. The content of this container will be automatically filled by the formatter used for the selected news. Hopefully this helps a bit. Feel free to ask more questions. Kind Regards,Alex. -------------------Alexander Kandzior Alkacon Software GmbH - The OpenCms Experts http://www.alkacon.com - http://www.opencms.org From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Andrew Adams
Sent: Tuesday, July 24, 2012 8:06 AM
To: opencms-dev at opencms.org
Subject: [opencms-dev] Detail pages Hey all, I was curious if there was a guide to setting up detail pages on-line. The documentation is a bit ambiguous and in all honestly I'm finding some difficulties grasping the concept within itself. What I understand so far is that at it's core you have container pages in OpenCms which has container elements; these are hooked up to templates via the "template" property. You provide this container elements with data through the use of the ADE navigator and creating structured xml content, which is formatted through the page through formatters which are specified in the content's schema. What I'm unclear on is when I use an internal link to a specific piece of content, where this goes to, what's loaded, and the use of detailpages to provide a specific formatting/template/rendering for all resources of the same type. Thanks,Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20120724/99bc222d/attachment.htm>
More information about the opencms-dev
mailing list