nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Has anyone used segmentation successfully?

Bowker

I have a very simple requirement.

We are building two sites (One Desktop, one Mobile)

The site map for the two sites are the same but the content is very different. (We can't use the same pages with different CSS, so that's not an option)

Has anyone implemented a pre-controller to do anything like this?

Find more posts tagged with

Comments

Crsb

I am not sure what exactly your question is, your post title sounds little different from the details. but i will give it a try:

Basic implementation of segmentation would be that you would define in sitepublisher sitemap different segments, then add a precontroller to figure out what segment the user belongs to (mobile vs desktop). the components appearance including site sitemap (navigation components) will have different display based on whatever segment the precontroller detects.

do you already know what will be displayed to the mobile user (mobile segment in sitemap) and how it will look like (mobile segment skin or xsl logic)?

Bowker

(I was in a hurry to get out last night so I didn't add enough details to the original post.)

Here's an example of what we want:

We have a segment called "mobile".
When a user comes to the site at http://www.****.com/site/mypage as a mobile user, we would like the page http://www.****.com/site/mobile/mypage to display.

The Sitemap for each site will (hopefully) be 100% compatible, page for page.

Rick Poulin

I've done something similar, but not quite the same: wrote a precontroller to do geolocation on the incoming IP and redirect to the appropriate locale. In your case, I don't think the segment will be all that useful because you're going to be determining that in the same code and based on the same request context (the thing that identifies segment=mobile could just as well not identify a segment and redirect anyway). As Csrb mentioned, segments are usually for use in components, rendering different content or L&F.

Crsb

When a user comes to the site at http://www.****.com/site/mypage as a mobile user, we would like the page http://www.****.com/site/mobile/mypage to display.page.

does this mean you physically have 2 sites? or at least a set of mobile version pages under /mobile/? if that is the case you need a redirect and don't worry about segmentation since you already created a full mobile ready pages.

If you were working with one set of pages with logic to render different things depending on a segment, then it makes sense to look into segmentation. but if you already created a mobile version in a separate file then it is just redirect.

nipper

does this mean you physically have 2 sites? or at least a set of mobile version pages under /mobile/? if that is the case you need a redirect and don't worry about segmentation since you already created a full mobile ready pages.

If you were working with one set of pages with logic to render different things depending on a segment, then it makes sense to look into segmentation. but if you already created a mobile version in a separate file then it is just redirect.

Should not need two different sites. If he can set up the sitemap to segment based on the mobile/non-mobile then one site will work. If the content it kept in DCRs then you can easily share the content (whether it is two sites or not).

tec_iwov

segmentation is part of targeting so you need to define the segment rules in order to do this. you will need to extend the data model via RequestContextWrapper to add you logic for processing the user agent value.

there is a controller:

com.interwoven.livesite.runtime.controller.impl.RulesEngineController

that you can put on the site to execute the segment rules.