SharePoint 2010 is coming up to its 2 year birthday, so it worth talking about Ribbons. Too often solutions concentrate on pages, Web Parts, lists, libraries and workflows. A SharePoint solution should be more than this – each of these components should be combined to provide users with a holistic solution, where the components work together and not as discrete entities.
Who are the end users in the SharePoint world? This answer differs from time to time when I poll the attendees in my conference sessions and classes. Here are the three choices for you:
Responsive web design is about making your web site adapt the layout to the viewing context, typically the browser window or the device that renders it. In other words, whether I watch the web site on a mobile, a tablet or a pc, and no matter what resolution I use, I should see something useful. It should respond to the context. Lately I’ve redesigned my blog to make it responsive, and here is what I’ve done.
The best part of my job as an evangelist is that I am able to connect and talk with some of the brightest minds in the SharePoint community, tapping into their extensive backgrounds to better understand their unique perspectives to some of the more difficult business problems facing SharePoint teams. One of the more common problems — which sounds simple, and yet it sits at the core of the majority of failed enterprise application deployments — is the failure of the organization to have a shared understanding of what is to be accomplished.
In SharePoint 2010 WIKI page infrastructure, you get to modify the WIKI page in a standard free-text format.
The WIKI page is a list item in the WIKI page library. As every list item, WIKI pages can have custom fields, both content type inherited and specific library fields.
I’ve seen plenty of technical mistakes when implementing SharePoint, particularly in larger environments when the risks of failure are higher. Here’s a countdown of my top ten “favorite” SharePoint mistakes:
In the last week I’ve been asked for this information a few times, so I decided to go ahead and blog it. I’ve been hesitant to put out an official blog post on this, because I don’t think it’s ready for prime time. But, it keeps coming up, so here it is, the steps I follow when I install SharePoint 2010.
Yaroslav Pentsarskyy, Technology consulting Manager at KnowledgeTech and Virtual Technology Specialist for Microsoft (@spentsarsky) shares his thoughts on the one thing that people need to know about Office365. This is part of ‘The One Thing’ video series produced by Christian Buckley (@buckleyplanet) and the Axceler team.
In a previous post I shared some thoughts regarding changes to authentication providers in SharePoint 2010. As I worked through the issue of removing Claims/FBA and reverting to NTLM I discovered a number of issues that manifested themselves in strange ways. The first problem I encountered was the inability for a Farm account to make changes to the Authentication Providers settings in Central Administration. The System Account couldn’t even view the dialog – each attempt resulted in a 403 error. This was bad news as a lot of things happen behind the scenes when changing authentication settings in this dialog – not the least of which is propagation of changes to all the web servers. This meant I would have to undo all of the Claims settings manually and repeat them on each server. Not my idea of a fun afternoon.
In SharePoint 2010, providing users have sufficient permissions, they can add various web parts available on the site. In larger organizations, various users have different skill levels and although some categories of users might be allowed to edit the page – you might want to restrict who can add which web parts to the page.
