Hot answers tagged branding
5
James, what Sig posted works for both things that you are looking for. The only change I would suggest would be to omit the use of !important in the style statements. You want to try to avoid using that as much as possible.
/* Hide web part title border on hover */
.s4-wpcell:hover .ms-WPHeader td,
.s4-wpActive .ms-WPHeader td,
.s4-wpcell .ms-WPSelected ...
4
In the head section of the master page you need to define a tag prefix in the style of:
<%@ Register Tagprefix="Yourwebpart" Namespace="yournamespace" Assembly="yourassemblyname, Version=1.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
Also don't forget to change the PublicKeyToken and version number.
In the location where you want to ...
4
Untested across the whole gamut of browsers, but if you're using the OOTB DOM, you have to do much more than just set the quick launch height. The #s4-leftpanel-content div contains the content and background color of the quick launch, so this has to be given a height of 100% (which sizes it to the height of the #s4-leftpanel div. #s4-leftpanel needs to be ...
4
Basically, it can be done with css with header and table changing:
.s4-wpTopTable {
background:
#FEE;
}
.ms-WPHeader {
background:
#FEE;
}
If you want to apply this to particular web-part, you can add additional css-marker class on you web-part render methods to find you web part instance later or use js/jQuery-client bases techniques to apply/change ...
4
You need to move the list Url to your module definition:
<Module Name="Style Library" Url="Style Library" RootWebOnly="true">
for GhostableInLibrary to work properly. You should of course then remove it from the File Url, since it is now defined on module level.
If you have no Url in the Module tag you can only use type="Ghostable" on your File ...
3
Moussa,
That all depends on your requirements and scenarios.. Let's say you have a website and you created some pages and webparts, did some branding and now you want to use this website for other SharePoint farm or same farm with different applications then you can SAVE SITE AS TEMPLATE and use the template to create new sites!
You can see what is ...
3
Customizing Meeting Workspaces is not as straight forward as one could expect unfortunately (both SP2007 and SP2010).
First of all you cannot use Web Templates or Custom Site Definitions because Outlook often will be the one creating the sites using web services, and it is only aware of the OOB site definitions.
As i stated in comments elsewhere, feature ...
3
The class you need to override is 's4-ca s4-ca-dlgNoRibbon'. This is the runtime class that comes from the corev4.css . This class contains a style with background-color set to white and background-image set to 'none'.
Try changing this class through an override by the following two approaches:-
Dedicated Custom Layout Page - You can create a custom ...
3
The trickiest part of this is making sure the brand gets used for all new mysites created from this point on. To do so you need to make sure your branding conforms to a key prerequisite. Is your brand packaged up in a visual studio .wsp and can it be applied to a given site collection by activating one or more features? If so then you can apply it to all ...
3
There is a out of the box content placeholder containing the site name that can be placed inside your masterpage. I believe Randy has it included in the block of content placeholders at the bottom of the page, and you can just bring it up to where you want it.
<asp:ContentPlaceHolder id="PlaceHolderSiteName" runat="server"/>
3
The "/_layouts/15/settings.aspx" has a user control "~/_controltemplates/15/TopNavBar.ascx" included in top navigation and it will hard code a top navigation, override the one you have set in the master page. Like this:
<SharePoint:AspMenu
ID="TopNavigationMenuV4"
Runat="server"
EnableViewState="false"
DataSourceID="topSiteMap"
...
2
Every web part has a TitleUrl property. I bet this is not set correctly in the blog template.
You will find how to add a web part to SharePoint programatically in an event receiver on another thread. How to programmatically add a webpart to a page?
In your case you need to loop over all web parts returned by the LimitedWebpartManager on the page, find the ...
2
The following CSS worked for me.
To hide the active Web Part border:
.s4-wpActive .s4-wpTopTable, .s4-wpActive .ms-WPSelected
{
border: none !important;
}
To hide the Web Part title bottom border on hover:
.s4-wpActive .ms-WPHeader td, .s4-wpcell:hover .ms-WPHeader td
{
border-bottom: 1px solid transparent !important;
}
Note the use of ...
2
Insert <SharePoint:ProjectProperty Property="Title" runat="server"/> into the masterpage where you want it.
Or if you want it like the default v4.master with a being in the PlaceHolderSiteName ContentPlaceHolder as a link, then use
<asp:ContentPlaceHolder id="PlaceHolderSiteName" runat="server">
<SharePoint:SPLinkButton runat="server" ...
2
There are two possible options, depending on what you are attempting to do and what you have available to you. You could take nearly full control or you could go the more common route and merely add your own styles to the pick list. The latter approach is usually done by specifying a custom CSS file for the site and including the '.ms-rteCustom-ZZZZZ' ...
2
Branding is as easy or as hard as your company wants to make it and can range from simple recoloring of common UI elements via Themes to a total overhaul of all master pages and page layouts with completely custom CSS and Javascript. Given this virtual canyon that is possible, it is hard to offer one kind of advice.
However, there is an excellent book out ...
2
As you say, pointing to the same content. Even though this translates to 2 different IIS sites, in terms of SharePoint, they both target same Content Database, as well as settings for the same Site Collection.
In your case, you could rather use Explicit Paths (Intranet vs Extranet), with 2 site collections and then setup individual settings, but at the ...
2
this is easily done.
Look up master page branding, you can deploy a separate template on every site collection you create. You can create custom authentication, navigation, profiles, metadata, sites, you think it a different site collection is just different and can house a totally different solution.
In theory you can have 100's of site collections all ...
2
All you need to do is to follow these steps :)
Open the master page, find the div tag:
Put the following around it:
<Sharepoint:SPSecurityTrimmedControl runat="server" Permissions="ManageWeb">
<div id="s4-ribbonrow" …</div>
</SharePoint:SPSecurityTrimmedControl>
or you can follow this Blog, it shows you three ways of doing it ...
2
The WebPart class has properties for background color and background image URL.
http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.webparts.webpart_properties
2
You are only setting the property on the root SPWeb object, that property is not accessible or propagated down to sub sites.
If you want to apply your master page you will need to write some code in your feature receiver to enumerate child SPWebs and set the property on each child, don't forget to call update on each SPWeb.
2
Use an EditModePanel to display two different controls when editing and displaying:
<PublishingWebControls:EditModePanel runat=server PageDisplayMode="Edit">
<SharePointWebControls:TextField FieldName="Title" CssClass="emedia-spwc-global" runat="server" />
</PublishingWebControls:EditModePanel>
<PublishingWebControls:EditModePanel ...
2
I general you will find all on my blog that needs to be done: http://www.n8d.at/blog/centered-fixed-width-design-in-sharepoint-2010-the-fast-way/
What you need to do is:
div.s4-title.s4-lp,
body #s4-mainarea,
#s4-topheader2,
#s4-statusbarcontainer{
margin: 50px;
padding: 0px;
float: none;
background-image: none;
...
2
There is no way to accomplish this in a way that suits your goal. SharePoint will always add its CSS to each page. You could remove it client-side, but that doesn't solve your issue of reducing page size.
For public-facing sites, I have used Aptimizer (now owned by Riverbed): http://www.riverbed.com/us/products/stingray/stingray_aptimizer.php
Tools like ...
2
The styling should be done with css and of course if you create your own Page Layouts you can easily control each web part zone so whatever web part you put inside of that web part zone will get the style you are after. Without the creation of control adapters or any custom deployed code.
Example:
<div class="content-zone news-area">
...
2
Sounds like I am a little late with this response but you do not have to make it a publishing site just to apply branding. Most branding can be achieved with CSS which can either be applied at a site level or on specific pages as needed. If a custom master page is actually required then you can still access the page to select a master page using ...
2
You seriously do not want to start messing with the Ribbon in this way. That critter is like a great white and once you tangle with it, you will bleed for years from places you didn't know existed. Trust me on this: I have the scars to prove it. If you need to add or remove things from the ribbon, follow the XML Feature examples on the web or use the ...
1
It is possible to create your own path seperator.
Follow this blog - Improving Navigation in SharePoint 2010 — Part 1
In the PathSeparatorTemplate insert your own seperator or seperator control.
Hope this helps :)
1
This wabpart uses XSL transformation. Basically, it uses main.xsl file to render HTML. You can find this file into 14 folder. But I donot recomend to do changes in this file. The best solution is to coppy main.xsl, rename it and then add reference to a new file in the webpart property or list definition. Also you can use SharePoint designer to make changes. ...
1
CKS has a branding template for SharePoint. Apart from it, we can structure our project solution and categorize the elements say masterpages, pagelayouts, Scripts, Styles, Images, Webparts, List Definitions and similar way create features to deploy independently.
master pages, page layout, styles, scripts, images - Feature 1 (Web\Site - scoped)
Webparts - ...
Only top voted, non community-wiki answers of a minimum length are eligible
