I love the simplicity of SP Wiki. I have further enhanced the wiki page by adding an additional column/field to categorize each page. I then embedded:
- a CEWP to include SCRIPTS and STYLES,
- a list to create a heirarchy (breadcrumb navigation)
- a document library to highlight resources applicable to that page.
The dynamic effect is acheived by:
1. setting my resource doocuments and breadcrumb list to that exact category and
2. filtering the list/library web parts via 'connections'.
Whilst it was easy to this set up on 2 or 3 wiki pages, it is time consuming and would be confusing for the person to whom I would soon be handing over this function to create and manage hundreds of pages.
Is there a way to combine all the 3 web parts (and their customization) and export it as a single web part? Or any other way to achieve this?
Note: Unfortunately I am a front end user only - I dont have access to the backend admin access or SP Designer.
Save the site as a template :)
Reference: http://msdn.microsoft.com/en-us/library/office/jj938033(v=office.15).aspx
You create one template wiki, save it as a template including content and you can then create a new site, based on that template.
Related
My team is trying to build out a Web Template which includes an instantiated Wiki Page with some default Web Parts added to it; but we're unable to get this behavior to happen.
In brief, we're looking to add some default.aspx (or Home.aspx, the name is unimportant, just the functionality) to the SitePages directory, GhostableInLibrary; so it's visible to all SiteCollections made from this Web Template.
It is of note that we're basing our Web Collection off the Team Site, and that the Wiki will be the default Home Page for the new site.
Site templates can be used to customize newly created sites except for the top site of a site collection. Since site templates are all managed in site collection's Solution gallary, so a site template CAN'T be used to define its own container.
You need a Site Definition to customize the first site of your site collection.
For how to use site template, you can goto, http://weblogs.asp.net/soever/archive/2009/10/19/sharepoint-2010-site-exporting-as-wsp-solution-part-1.aspx
For how to create a site definition, you can goto, http://msdn.microsoft.com/en-us/library/gg276356.aspx
If you want to strap onto an existing template without creating a new copy, or you don't have the original site template to access. You use a process called feature stapling.
When you create a sharepoint solution it would contain two features, one for your actual functionality and one that simple staples it to an existing template.
Here is an article discussing it some more. http://mssharepointtips.com/tip.asp?id=1065
Effectively I am looking to change the viewed Document Library within an exsisting List View Web Part from 'Document Library #1' to Document Library #2'. I want to do so without having to re-create the entire web part (e.g. settings & views) as I would have to do this multiple times.
Sharepoint version is 2007 and Sharepoint Designer is not avaliable.
Context: I am currently building a Sharepoint area which will consist of multiple ASPX pages all based off an original layout. This layout includes a List View web part that directly views a Document Library.
Each ASPX page has a Document Library attributed to it (e.g. Page1.aspx and DocLib1), which I wish to display within this List View web part.
Page1.aspx was setup just fine (effectively the original). When setting up Page2.aspx as a direct copy of the first, I am unable to change the List View from DocLib1 to DocLib2 as there seems no option to do so.
The list view web part isn't easily customizable unless you can edit the xml for the web part and change some guids. If you want to be able to change the source list through the browser you will need to use a different web part - the content query web part is an out of box option, though obviously that is quite different from the standard list view.
You may also be able to do something with with list templates - if you can use a custom template instead of the standard document library template, you may be able to alter AllItems.aspx to do what you need.
I have developed a publishing portal in sharepoint.I have a requirement wherein I need to create sitemap for the entire web application.
This should be dynamic, in the sense, whenever we update the contents of any given page in our web application, it should be reflected immediately in the sitemap page. What are the possible ways to achieve this and which is the best possible solution considering the scalability and easy configuration?
Thank you.
If you don't want to use a custom webpart, you could use normal navigation list to create your sitemap and it is automatically updated. You only need to style it in a way to resemble some kind of sitemap.
Here are some links to get you started with customizing your navigation:
Custom Navigation in SharePoint - The Full Monty
How to: Customize Navigation
Also there is the portal site map which provides the data source for your custom menu. Just read up on custom navigation and stuff like PublishingNavigation:PortalSiteMapDataSource and SharePoint:AspMenu.
There is a nice PowerShell script to create a sitemap for SHarepoint 2010, if you want to submit your sitemap to Google: Generate A Sitemap For SharePoint 2010 Using PowerShell'.
You can also install and customize the SharePoint Web part ("Table of Contents") to your liking. Read up on it here...
Take a look at our ECS product, it is close to what you need
http://www.infowisesolutions.com/product.aspx?id=ECS
It was built as a system of cross site collection navigation, with security trimming and permissions inheritance between site collection.
The New SharePoint Site page has a Template Selection section which can contains multiple tabs. For example, Meetings and Collaboration. These are controlled in webtemp.xml using DisplayCategory. While hiding and unhiding different OOTB templates, I somehow ended up switching the order of the tabs so that Meetings show up first. Can't seem to find any references on how to control the order of the tabs and make Collaboration first again.
Has webtemp.xml been reordered or edited so that Team Site, Blank Site, and Document Workspace are now either below the Meetings sites or are marked as hidden? I captured the output of GetAvailableWebTemplates for a test Team Site and the first 12 templates match the contents and order of an OOTB webtemp.xml. If any of those Collaboration templates are visible in your list, try moving it above the Meeting templates, save, and recycle the app pool.
Is this a Publishing Site? If so, check Site Settings > Page Layout and Site Template Settings to see if any Site Templates are being restricted. From what I can tell in Reflector, the TemplatePicker control calls SPWeb.GetAvailableWebTemplates, which should consistently return OOTB templates first followed by any custom templates. TemplatePicker then loops through the templates and creates a tab each time it encounters a new SPWebTemplate.DisplayCategory.
I have a website in Sharepoint 2007 (it is a publishing portal).
I want to create a site with more specific info than what it comes with Sharepoint.
You know, when you create a new site, the only info you can enter is title and URL.
I would need an image and a description.
The solution is not a custom list, because i need to have pages inside and other lists.
How can i extend this site list?
Write an application page or web part that creates the new site. Programmatically update it with what users enter in your custom form.
Creating the site
The SPWebCollection.Add() method creates the site from a site definition. Create a custom definition that includes the site columns, content types and lists required. These will then be created as part of the site.
Further customisations
This won't perform all customisations however - for the rest develop a feature receiver. On activation it will run any arbitrary code on your new site.
For example as you are using a publishing site, retrieve its default page with the DefaultPage property. This is an SPFile object which has an Item property that can be edited like any other SPListItem. Update the image field and description field for the item based on its content type. The page will then render these properties.
All of the above can be wrapped in an SPLongOperation for a nicer user experience.
There are other options as well, for example the SPWebProvisioningProvider. The two separate steps above of creating a site definition and activating a feature receiver could be tied into one with this.
There is more information on the above techniques (plus others) and their pros and cons in part 3 and part 4 of this series by Raymond Mitchell.