Why SiteCollectionsand the implications of doingthem or notWhat types of navigation are there? How shouldnavigationbedone, andhowcanManaged Metadata help you? All in SP 2010
Site CollectionsallowscalabilityMostviable option toseperateyourstructureSubsiteswill hit limits in largerenvironementsWebapplications means multiple URL’s, confusingfor end users ..Farms is overkill
Quota’s mean that you can monitor the size
2,000 Site Collectionsrecommended; with a maximum of 5,000 2,000 * 300 = 600 000 site collections in a webapplication200 GB recommended, 4TB maximum Checkout: http://technet.microsoft.com/en-us/library/cc262787%28v=office.14%29.aspx More site collections means More data to storeMore unique permissions to store
Out of the box contains the TopnavallsubsitesLeftnavalllists & libraries The view selectorcontains the Site Title, Document Library or List Name andCurrent view (includingviewselectorto select other view)Breadcrumbcontains the Site Collection Name / Subsite name, Library nameIfyouadd a portal site map connectiontosomeotherlocation; yetitwillnotbeshown on the rootsite collection
Scenario
Typical setup, 1 site collection per client, clients are somehow setup in a region (Europe, America, Asiaetc). Besidedclients we also have internalprojects3 levels of navigationTop willcontainallprojectsforthisclientLeftnavwillcontainall content in a project (subsite) Breadcrumbwillcontainstructureand view selectorifneeded
Basic functionality, the structure is in the managed metadata, so the structure itself is useable in 2013, but there will be some fixing to do before it works ..