Hi,
Thanks for the reply. We are trying to avoid duplicating content - we have thousands of 'stories' and don't want to have to create two different documents for each story.
So we've gone an imported the stories into the 'Article' document type, and are looking for a way to reuse the content easily, without duplicating it - creating two documents requires twice the effort of creating one.
Your suggestions are excellent, but I don't think they are suitable for our scenaio; here's why:
#1 - interesting, but we'd have to redesign the entire site. Quite a bit of extra work.
- each 'template' would inherit everything from the masterpage - we don't want the mobile site to have the burden of all of the css and js and other assets. I know we could pull out all the css and put them in the great 'head html' web parts and hide them selectively.
- Maybe if I would have thought about this eariler, I could have partitioned the template regions differently.
#2 - Means we need to duplicate the content.
So either way means extra work; #1 - we do a bunch of redesigning the zones and regions and #2 means duplicating content.
I am intrigued by #1 and seeing if I could get it to work - we have a 'mobile' heirarchy:
home
news
mobile
->/news
->/stories
->/etc...
events
etc...
So the mobile users will be directed to /mobile, and if we use #1, the content will actually be somewhere else in the tree, so I guess we'd use 'linked' documents with custom Document Aliases.
Hmmm, I just had another idea about #2 and how to get it to work for us - if we have two document types (as you suggest):
Article
mobileArticle
Then we can apply a unique template to each. If I make the mobileArticle type only have a single field of 'parentArticle' (that points to the original Article), I can use some Macro and Query magic to pull the information from the Article to display it in the mobileArticle transformation!
This would give us the ability of having different templates and layouts without having to deeply redesign the existing site.
Thanks for helping me work through this!
Lance