Publish template question

Question

Hi all,

This is a pretty basic question on developing a internet facing web site. I am developing a web site that has an "Intranet" face and "Internet" face. I am going to use the "Publishing Template" for the "internet" site. Now the question is

a) Should the UI designer do the changes to the design of the page ONLY in the internet portal and submit for workflow - What else are the options ?

b) In some blogs I read that you can publish content in the "Intranet" site and then move them to "Internet" site. I presume they are talking about word documents / excel sheets as contents. How do we do that... Is this feature already available or should we write code to move files from my intranet portal to internet portal

c) Convert word document to web page which would eventually show in internet site ... Can the word document be edited and approved at the intranet site and somehow moved to the "Internet" site ? How can i achieve this.

Thanks for reading. Any help as links / articles / blogs / anything would be much appreciated.

Thanks,
VJ

Answer 1

Hi VJ,

If you want to use the Intranet site as a staging environment you can use the Content Deployment features of MOSS.
Check out this web cast for an explanation on how this works:
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032396926&Culture=en-US

---

Mirjam
www.sharepointblogs.com/mirjam

Answer 2

Thanks Mirjam vam Olst for the reply. I will surely check the link and the web cast.

If you can be kind enough to answer me an allied question.

One can create two zones for a sharepoint site (Intranet zone / Internet zone) where the internet zone is the public facing site and Intranet zone is the authoring site. Here both the web applications are accessing the same content.

On the other side, many blogs talk to create two "separate" web applications with their "Independent" site collections and then move / publish content using jobs between them.

Can you let me know is there any particular disadvantages with Option A coz as far as I see Option B seems to be the most discussed and preferred.

Thanks again for the earlier reply.

Regards
Vijay

Answer 3

Hi Vijay

 

In my opinion, I think there is no such “disadvantage” with the first method. The first method provides a convenient way to manage the sites, while the second method provides a more secure and feasible way to manage the sites. Which method to be adopted is dependent on your requirement.

 

There are some scenarios when we need to use a dedicated application pool:

l  To separate authenticated content from anonymous content.

l  To isolate applications that store passwords for and interact with external business applications (for example, Business Data Catalog connections).

l  To isolate applications where users have great liberty to create and administer sites and to collaborate on content.

 

There are some references to help you plan the infrastructure of the SharePoint,

http://sharepointmagazine.net/technical/administration/best-practices-of-sharepoint-farm-configuring-and-deployment-part-1-architectural-and-logical-planning

http://technet.microsoft.com/en-us/library/cc261834.aspx

Hope this helps.

 

Lu Zou

Answer 4

Hi Vijay,

The disadvantage of option A is that you haven't got a separate authoring environment.
* So say you've got a custom component that you want to deploy and you want to see what that would look like with live content on it on your authoring farm. In the case of just one web application it would be visible to your anonymous users right away as there is nog approval on custom development that's either deployed to the server or it isn't.
* Also, as soon as your content is approved it's live data. You can't setup a content deployment schedule as there is nothing to deploy your content to. It's already there. As soon as the content is approved it's available to anonymous users. And content will be approved per page. So if you were making a lot changes to your site and you want to launch the new content say July 1st that would be difficult. If you would be using 2 farms you could easily achieve that using a content deployment job that would deploy all approved changes to all pages at the same time.

---

Mirjam
www.sharepointblogs.com/mirjam

Answer 5

Thanks Lou Zou and Mirjam for taking your valuable time to answer a newbie question. I really appreciate it ... I am sure i will bit back with more questions .. but yes .. the answers does give a lot of clarity ...

Thanks again
VJ