Tag Info

Hot answers tagged

3

You can create an Authoring Site and extend this site and create a public website. Check out Publishing and Content Deployment Check out this article as well. This is pretty old but you will get some ideas.


2

No, I would even advise to work with subsites to create your navigation structure. Using subsites, it's very easy to group information that belongs in one place, and provides even easier use to display context-sensitive content in a content by query webpart. It's also interesting to use for seo-purposes, because you can make site names descriptive for the ...


2

No it's very common for WCM to use a lot of subsites


1

I believe it might be related to multiple aspects, such as which Content type is the default per each Pages library, to which of your library-scoped content types you added the columns, the actual page layout to which content type is associated, etc. I would suggest you follow: Create your own Content Types at the Site Collection level - inherit from ...


1

What about XPS? Cross Site Publishing now is the preferred way to publish content in these kinds of scenarios. Everything in Waldek blog is gold for this topic: blog.mastykarz.nl


1

Not sure if you have been going through this but Waldek M. has a really nice write-up providing valuable hints on the subject, find it here http://blog.mastykarz.nl/conditional-content-mobile-devices-sharepoint-2010/ also check this for some more details http://www.bloggix.com/archive/2011/01/31/introduction-to-mobile-pages-in-sharepoint-2010/


1

If created at the site collection root, the content type will be available to all subsites. If you create a document library template from a library with those content types enabled, you can provision new libraries in subsites with those set already.


1

I would recommend you to start with on how to create a Publishing page layouts and Content Types. Try packaging them with Master page and Branding using Visual Studio and you're good to go.


1

There are a number of reasons why you might need to create a custom provider. If you do create a custom provider, you will would need to add the security trimming on within your code. This is difficult, but not impossible. MSDN magazine recently had a pretty good overview implementation for a custom provider that leverages the term store to surface the ...


1

Thanks for you comments The answer was actually to add the PageParserPaths section to web.config so that server side scripting was enabled as per http://blogs.msdn.com/b/kaevans/archive/2007/04/26/code-blocks-are-not-allowed-in-this-file-using-server-side-code-with-sharepoint.aspx I have absolutely no idea why it worked before the upgrade as I don't ...


1

This question is really a general matter of design, and how you constrain users or authors. The requirement typically states that a "consistent" design will be provided by professional designers, and authors will slot content into that framework. In SharePoint, this is achieved by creating master pages and page layouts (publishing model) that limit what the ...



Only top voted, non community-wiki answers of a minimum length are eligible