I hope you guys can help as I'm new to Sharepoint development and it appears to have a million and one ways to achieve any goal!

I need to provide our staff a place on the intranet to enter product documentation (wiki?), where they can write about a particular component, relate it to other components (used a lookup column pointing to dependencies in the same list), relate it to which products it applies (lookup to a product list) and indicate whether it is for public consumption (yes/no).

If it is to be for public consumption, its content should appear on a non-authenticated, public facing site and it also needs some navigation options produced from the lookup data, i.e. hierarchical tree views.

I have tried to achieve this with Foundation but it appears too lacking in features, i.e. I had two separate web applications set up, one for the intranet and another for the public but sharing data wasn't possible using stored authentication. Also, the lack of templating makes navigation options difficult.

Note that I am primarily a developer so code options are not a problem, if less desirable as changes will require dev time.

What would be the best way to:

1) Share the public data with the public, while retaining it and the rest under the auth'd site for editing

2) Enable templated views of the wiki data, to allow the nav to display

3) Alter the content of web parts on a page, i.e. have a web part that displays just the dependencies of the component being viewed

I believe I've answered 2 - Office 365 Enterprise Wiki but still awaiting go-ahead on that but it would be great to have a page that displays a web part to the left with a nav menu, then clicking it changes web parts on the right to display content, dependencies, etc.

Any solutions gratefully received!

  • 3
    You have really asked at least three questions here. I think you would have a better chance of getting an answer if you asked a two or three more concise and specific questions. Remember, you are free to ask as many questions as you like. See ask for general guidelines.
    – SPDoctor
    Nov 25, 2011 at 17:49

1 Answer 1


+1 to SPDoctor's comment, it's a lot of questions for a single post! I'll just reply to 1/

I have the same issue. The easy answer is to use a Page Viewer Web Part (aka iframe) to display a view of your intranet on your public site. Of course it means that you need to enable anonymous access on your intranet, at least for the items you want to make public.

If this doesn't work for you, then you'll have to create two lists, one intranet and one public, and keep them in sync. There is no out of the box option for this, so you'll need to write your own code (for example using Web Services), or have a semi-manual process (through Excel, Access or SharePoint workspace dfor example).

If you just need to push new items to the public site, consider using inbound e-mail.

  • Good point, I'll ask about other issues separately, this post can focus on the page viewer :)
    – Gene
    Nov 28, 2011 at 9:06
  • I might end up just having the information on the public site and administered from there but I would like to follow this page viewer idea for a bit. If I have the page viewer show the data from the internal site, I could publish it using a blank page to show the content only, to avoid headers appearing, etc. If I then have a navigation control in another web part, alongside the page viewer web part, how would I have the navigation commands (querystring?) from the navigation web part alter what content is displayed in the page viewer web part?
    – Gene
    Nov 28, 2011 at 9:38
  • What do you mean by alter? Point to a different list?
    – Christophe
    Nov 28, 2011 at 16:43
  • Perhaps alter was the wrong word, I would like it to set the page viewer's navigation url to whatever page was clicked in the navigation web part. So far I have only been able to have the page viewer simply display the content, all navigation being carried out inside the iframe. It might not be possible but I am coming from a position of ignorance here!
    – Gene
    Nov 28, 2011 at 17:01
  • One option is to have multiple PVWPs on your page, each pointing to a specific page. Then your navigation will simply show the appropriate PVWP and hide the others. You could also have a single PVWP and change its source, but this is more technical. For the record, a PVWP is just an iframe.
    – Christophe
    Nov 28, 2011 at 17:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.