There are many approaches you can take for this depending on sites structure
OOTB Content Deployment will publish selective content from intranet to authoring site but selection has to be at sub-site levels and not below that. E.g. OOTB cannot say that publish so and so lists from a site. On the other hand free codeplex tool http://spdeploymentwizard.codeplex.com/ can help you publish content with granularity. This tool is scriptable and you can choose what all items you want to send. Again the content deployment process can be a pain if some items are dependent on others. Option I would look is if I can move things I do not want on web site to sub-sites and make sure the website does not have dependence on them. Then in job settings exclude the sub-sites containing intranet related stuff. If too much complexity than publish just everything and then hide things in web site via permissions. If you have some confidential documents etc which should stay on intranet than create a new sub-site and move the content to the sub-site and then exclude the sub-site from the deployment job. On Tue, Jun 1, 2010 at 5:19 PM, Peter Milliner <[email protected] > wrote: > Thanks for that. Just need clarification. I have had a look at content > deployment and understand the process of publishing from authoring to > production via content deployment. > > > > We will be having an authoring site (maybe a staging site) and a production > website. > > > > Can we publish content (some not all) from our intranet site to the > authoring site without 3rd Party tools – just need to know if this is > possible with OOB functionality. > > > > I.e. we are considering having course information etc stored on intranet > and managed on the intranet but require it be published to our authoring > site and then to our website. > > > > Cheers > > Peter Milliner > > Bendigo TAFE > > SharePoint Administrator. > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Jeremy Thake > *Sent:* Tuesday, 1 June 2010 2:02 PM > *To:* ozMOSS > *Subject:* RE: SharePoint 2010 Web publishing > > > > Take a look at Content Deployment Jobs and Content Deployment Paths. This > can handle this to a certain degree OOTB. > > > > 3rd Party tools are available such as RepliWeb to handle this also. > > > > Cheers, > > > > *Jeremy Thake* > > *SharePoint Evangelist* > > *Microsoft Virtual Technology Specialist* > > m: +61 400 767 022 – b: wss.made4the.net – t: @jthake > > Founder of SharePointDevWiki.com > > > > [image: Description: Beschreibung: Beschreibung: Beschreibung: > Beschreibung: Beschreibung: cid:[email protected]] > > [image: Description: Description: cid:[email protected]] > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Peter Milliner > *Sent:* Tuesday, 1 June 2010 7:45 AM > *To:* ozMOSS > *Subject:* SharePoint 2010 Web publishing > > > > Hello all, > > > > Just need some advice. We are at the moment in the planning stage for > SharePoint 2010 implementation. > > > > We will be using it for our intranet/extranet and website. > > > > The question that has been asked is can we publish from intranet to staging > site then to website with out of the box functionality and workflows (and > maybe a bit of custom workflow using SharePoint designer). > > > > The marketing department want to keep all their assets on their intranet > site i.e. articles, pictures, pages but when ready to publish are sent to > staging website and then eventually to website etc. > > We will also have certain policy pages that are stored on intranet and that > will need to be published to web > > > > From what I have researched and read I thought this could be achieved by > content types and web publishing features of SharePoint 2010 but my manager > has received conflicting advice – advising that more in depth > *custom*solution would need to be implemented for this to occur OR all > content and > assets for website would need to be on the staging site and edited and > stored on the staging site. > > > > Any advice appreciated > > > > *Peter Milliner* > > _______________________________________________ > ozmoss mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss > >
<<image001.png>>
<<image002.jpg>>
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
