Tag Info

Hot answers tagged

13

Here are my 2 cents: Make sure SharePoint still looks and feels like SharePoint. Don't mess about with default font sizes. Even if SharePoint deals with it well, your third party add-ins may not. Try to limit them to just change the colour scheme to whatever the company uses, a customised top (header) area and an optional footer. Don't go nuts, you'll ...


8

You are working with CSS3, this is only supported from Internet Explorer version 9. For older versions of IE you need to have a fallback solution. One of the fallback is CSS3 Pie. More information can be found here: http://css3pie.com/ http://css3pie.com/about/ It requires you to add and reference an additional file (pie.htc) to your environment. ...


6

As already mentioned in another answer, Internet Explorer, up to and including version 8, does not provide support for any CSS3 based styling. While Internet Explorer 9 comes with limited CSS3 support (like border-radius and box-shadow, but neither text-shadow nor background gradients) it would require to change your masterpage as mentioned in another ...


6

Courtesy of Randy Drisgill: http://blog.drisgill.com/2008/02/favicons-in-sharepoint-master-page.html Drag a favicon.ico file to the Images directory of your MOSS site with SharePoint designer. Add the following line to your Master Page at the bottom of the head section right before the </head> tag: <link rel="shortcut icon" ...


5

I use layered architecture in all my SharePoint solutions and treat SharePoint generally as the UI layer, keeping it very thin. Any logic goes into the business model and I have DAL wrappers to abstract away the List infrastructure (which also helps with testing). For a good read on layered architecture in ASP.NET check out this article here. It's ASP.NET ...


5

Possible uses of hiding (closing) web parts can be if the web part is creating problems, is broken/unusable, or behaving badly. Or if the web part isn't needed anymore (like for an annual survey, only done once a year during May), you can hide it when it is not needed anymore. If the web part is not needed at all, and you do not plan on re-using it, you ...


4

Option 1: Ditch Visio and draw them by hand and scan them in. I often hand draw documentation these days for clients who appreciate the cutom-look, quick, low-cost, multiple-iteration approach. Option 2: Create the stencils yourself. I've used this approach in network diagrams when I wanted the server icon to represent a web server by adding a world icon to ...


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

I accomplished this by using the steps outlined here. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\DocumentTemplates\ Open wkpstd.aspx in a text editor. Find <SharePoint:RecentChangesMenu runat="server" id="RecentChanges"/> and replace with <SharePoint:RecentChangesMenu runat="server" ...


3

Agree with Bil. Web parts, web controls, application pages etc should only be the UI layer that calls into a layer that is agnostic of the original calling context; calling context could be an event receiver, console application, timer job, workflow, etc. Always ensure that this shared layer you call into does not have a dependency on SPContext.Current ...


2

Well you could mix various Windows version as long as they are using same architecture (32/64bit). But I would recommend an upgrade to 2008 because of following: to ease and uniform patching of your systems SharePoint 2010 will only support Windows 2008, it will be easier to upgrade if you are running 2008 already


2

jQuery is your friend and should be your best buddy when it comes to spicing up a UI (especially SharePoint). Be sure to check out the entire jQuery for Everyone series on End User SharePoint. Also check out the series on converting a free CSS template (Jet30) to SharePoint. Very awesome work! (sorry, link tool not working for me right now) jQuery for ...


2

Alex: Some of the jQuery effects are quick to implement and can give some sizzle. jQuery is cross-browser, so little risk there. I also have a stock set of CSS which I can drop into a master page and customize very fast, letting me reskin SharePoint in about an hour so that people don't even realize it's SharePoint anymore. Just changing some colors and ...


2

Everything that Muhimbi said. Make sure that they're aware that SharePoint is a .NET application, not a HTML website. You can only get so far with customizing the look & feel of SharePoint if you're a front-end designer with HTML & CSS knowledge. You will probably need the assistance of a .NET developer. Have them review Heather Solomon's blog. ...


2

Balsamiq has a good set of tools and is one of the favorites for some SharePoint designs. Clever Workarounds has a nice review of the tools specifically for using them with SharePoint. There are two pre-built templates that I know of you can use with Balsamiq and SharePoint. This one is for 2007 sites and this one is for 2010. Hope that helps!


2

If you want to see round corners with your solution in IE9, you have to change IE mode. See a similar question about round corners in SP SE. <meta http-equiv="X-UA-Compatible" content="IE=9" /> But IE=9 mode can affect some functionality. If you use IE8 or earlier, you must use alternative methods, (the best links are already provided by EStruyf.


2

The image you mentioned is used across all of the SharePoint v4.master (and not only). The important aspect is that only a small part of this image is ever displayed by using either OffSet properties in server side controls or CSS background-position attributes. One reason for which you see that it might be because it is referenced in any controls on your ...


2

The only reason to use Office 64 bit is if you're working with HUGE documents (usually excel or access) which are to big to losd in the 32 bit version. Otherwise you should always use 32 bit as there are several peices of functionallity which isn't implemented in the 64 bit version, especially around the browser plugins which SharePoint takes advantage of. ...


2

Check this out: MSDN: List Patterns You can also buy a guidance ebook here: Developing Applications for SharePoint 2010 See the SharePoint List Data Models chapter


2

Sean Earp's answer was extremely helpful, but the details were essentially off for my particular situation. Here are the steps I took to accomplish what I wanted: I put a copy of the favicon.ico I wanted to use in the /images/ folder by using SharePoint Designer. I then went into "Master Pages", right-clicked on "v4.master", hovered over "Open With", and ...


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

I inspected the green box with the F12 developer tools and found it: The outer box has id="Ribbon.Calendar". You can search for that in the markup to further inspect the inner elements. Edit Why can't you target them? I just did. I tested with: #Ribbon\.Calendar { font-size:12px; } Is it because you aren't escaping the .? Special characters in CSS ...


1

Usually it'll be better to redirect them to different subsites (probably site collections), based on the client id. Than all content can be security protected without causing any performance problems. The main downsides of doing all of the trimming in code are: Lots of custom code => lots of possible mistakes No search as that might show invalid results ...


1

I think you are taking the wrong approach here. If you can write such a document, it would be extremely valuable to the whole community but havn't you wondered why such a document doesn't exist already?? It's because it will take you forever to formulate. Unless you designers have designed for SharePoint many times before, they're likely to design something ...


1

The biggest problem area I've experienced is the ribbon. It is SharePoint, it can't be removed without removing it's functionality. It can be hidden for anonymous users, but the ribbon itself shouldn't be manipulated. It may end up giving you more headaches than its worth. Otherwise, go to town!


1

A sandbox by design is scoped inside of a site collection, and has no direct access to the GAC or the 14 hive (where the file would be ghosted). Therefore the file will be stored in the site collection database. The only performance hit would be the redundant files in multiple content DBs increasing disk usage but for these templates I don't see it being ...


1

Stuart, when dealing with really large lists, I think it could be a very good idea to use SharePoint Search to query and display these lists. The point is, that CoreResultsWebPart inherits from the well-known DataFormWebPart, so actually you can render very complex views with CoreResultsWebPart and its XSLT, and probably you can even create almost the same ...


1

Microsoft does not officially support Chrome so I would advise against using it in a production environment. You could use IETab for Google Chrome to use the IE rendering engine to display SharePoint pages better. Ultimately you should use IE to test SharePoint UI and in production have users use a supported browser. This will help if you need to make ...


1

A blog and a team site are created from different site templates that define the lists, libraries, pages, features and web parts that are pre configured on the sites. The team site is probably the most common site template used for collaboration. It provides a document library and lists for managing announcements, calendar items, tasks and discussions. A ...


1

I would convert the header and footer HTML to separate .NET User Control and then just embed them in the master page. Simple, straightforward, and clean. Here's a fairly recent post on this topic: http://www.evagoras.com/2011/02/10/smart-headers-and-footers-using-asp-net-user-controls/ Happy to answer any follow-up questions you have.



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