Hi Carlos,

Yeah one way is to pull data from a specific node by access it by the ID like this

@{ 
 var page = Umbraco.Content(1234); 
 
 @page.PropertyAlias
}

http://our.umbraco.org/documentation/Reference/Querying/UmbracoHelper/#Content%28intid%29

The disadvantage of access data from a specific ID  is of course if the page is deleted with the ID, so will the code where you retrieve data from break.

If your sites have different document types, then you could use them to access the data. If it´s spots that you want to use on all sites, I have seen setups, where you created them on one folder called e.g Content elements, and on the pages, the user can select these elements by using a Multi Node Tree Picker.

Or make a node that contains all the shared content between the different sites.

Hope this can help you at some point.

/Dennis

@Dennis,

That solution where content can be shared is more or less the approach we are looking at taking.  The Multi Node Tree Picker sounds like a good option.

So then the Tree picker can read all nodes in all sites of the Umbraco instance?

Hi Carlos,

I don´t think it´s a good idea to do it that way, because then the user will experience the site change, if you link to something on site 3 and you are on site 2.

The thing I was talking about with the Multi Node Tree Picker was to make a folder under Content (at the root) e.g called shared content, and in the folder you create all the content that should be shared between the sites, and with the Multi Node Tree Picker then pick the elements that you want to each sites.

Hope this make sense.

/Dennis

Oh, so you are talking about doing a structure like this then

Root

--Share Content

--Site One

--Site Two

-- Site Three

Am I understanding you correctly?

I see what you are saying now. I forgot the Root is not actually the site hostname. The subfolders hold the hostnames.

I see what you are talking about.  

is working on a reply...