Fixing Sharepoint 2007

I’m sorry for all the Sharepoint 2007 posts lately, if you’re not interested, just skip to the next post :). Anyway. The Sharepoint team recently announced further support of an addon called Accessibility Kit for SharePoint (abbreviated AKS) in a blog post about the future of Sharepoint on their official blog.

I thought I’d comment on the future plans, and get a bit more constructive and point to things that are rather easy to fix. Perhaps I can affect what gets focus in the next version? With a release cycle of 30-34 months (!), any changes won’t get implemented anytime soon, but I guess getting on the right track is a first step.

Shift focus from accessibility to customization

First of all, I’ve only briefly touched accessibility on my two posts about Sharepoint (Default HTML in Sharepoint 2007 and Sharepoint 2007 from an interface developer’s view. But to me, accessibility is the second step, being able to customize things, is the first. Let me repeat that I care more about being able to customize the Sharepoint interface, than the default interface being accessible. Right now, large parts of the interface are locked down, deep inside of the Sharepoint core. If I could customize things, I could correct the accessibility issues myself. I really think the focus should be customization first, and accessibility second.

But it’s possible to customize some parts!

Lots of people have commented on my previous posts saying that it in fact is possible to get Sharepoint to produce valid HTML. It’s possible to some extent, by rewriting all masterpages and many default controls that come with Sharepoint. Of course you can build a good interface if you only use Sharepoint for storage, and build the interface from scratch. But that’s skipping a lot of the things you bought Sharepoint for, all the existing components!

And you still can’t change the collaborative parts. And as soon as you want to add content to the site or change settings, you’re back in lock-in, no control, Sharepoint interface land.

Deliver as a service pack, not an addon

So, back to the announcement. I think it’s a shame that AKS is delivered as an add-on, and not as a service pack to Sharepoint. Accessibility is a user concern (they are the ones that need stuff done), not one that developers desperately need. So the focus should be to push this one to as many users as possible, and make it very easy to enable it for developers. A service pack would accomplish that much more effectively than an addon does. Most developers won’t even know the addon exists!

Control adapters are not the best solution

In the announcement is something called Smart adapters, from what I understand a way to automate replacing .NET controls with your own controls. So when Sharepoint calls that breadcrumb control, you redirect it to call your own breadcrumb instead. The problem here is that I have to rebuild the whole control from scratch, instead of just changing how it’s output.

Instead, if Sharepoint could expose a .NET List (the breadcrumb links) to me, I could decide the rendering myself. That’s customization!

Don’t repeat yourself, use master pages

More suggestions of changes: One of the biggest annoyances in Sharepoint is the bad implementation of master pages. Sharepoint only allows each site to have one Master page set, so you really can’t use your master pages for controlling things like number of columns. Putting that in the masterpage would means you would need to use that number of columns on all your pages. In Sharepoint, you instead have to wash out the bare essentials that all your pages have (a html and body element?), and set that in the masterpage. If two of your pages are similar, copy/paste the code between them. Terrible! What I want to be able to do, is to set several masterpages per site, and use inheritance between those masterpages. That’s fundamental master page concepts, that Sharepoint is lacking.

Organization of CSS and Javascript

When you ship code to your customers (Sharepoint is a framework, so Microsoft is essentially selling code to developers), you need to make sure that code is readable, and understandable. That does not only apply to C# code, it applies to the full interface as well. That’s simply not the case with Sharepoint. There’s two humongous files, core.css and core.js, where most CSS and Javascript have been poured into, with no consideration of organization or namespaces. There’s no indication how certain C# components interact with the CSS and Javascript and very very little documentation (often added after the fact, by annoyed developers like me). This just have to change, we need organization, modules, separation. We need an interface that we can understand without reverse engineering!

Another thing, releasing controls that are thought to be reused, really mean that they need to work in standards mode. All controls, even webparts. It isn’t reasonable to have to patch things inside your Javascript chaos to make basic things work! It isn’t reasonable to have to patch CSS for standards mode either. It shouldn’t have relied on quirks mode in the first place!

Examples are good, but…

The announcement also mentions examples. Releasing examples of how to make Sharepoint validate, conform to WCAG 2.0 AA (really?), or any other standard, can of course be of help. A lot more help than no documentation. But it’s also pushing over the problem to the customers. “We couldn’t make our product validate, but you can fix that, but doing this, this, then this, and that”. A default site shouldn’t have 200 errors out of the box, you can do better than that.

WYSIWYG editor and Firefox

The Accessibility Kit also mentions a new WYSIWYG editor, “aRTE”, that can be used instead of the default editor. It’s of course well needed, the default editor doesn’t work at all outside of Internet Explorer, and I really doubt that it’s accessible. So why is this released as an addon? You’ve built a better content editor, give it to people!

Also, the new editor takes you another step closer to supporting Firefox. You’re pretty near, but not being able to edit content in a CMS with Firefox really is bad. That should be the baseline. Really, I could understand if the ActiveX über-COM Silverlight Vista integration didn’t work, but editing content, or maybe interacting with webparts? To cling to Internet Explorer in this day and age is not going to work.

In summary

I hope that some of the improvement areas mentioned in this post will be taken into consideration in the development of the next version of Sharepoint. My tone is harsh, but that’s because I’ve really been slowed down my Sharepoint in my daily work. Customers complain because tiny interface changes takes days to complete. I hope you can see past my frustration, and see that there are big areas where you really can improve how Sharepoint work. I’m willing to help pointing in (what I think is) the right direction.

2 responses to “Fixing Sharepoint 2007

  1. The company I work for also uses SharePoint and I feel your pain. SharePoint is hot and customers want it and are willing to pay for it because it’s a Microsoft product backed up by their huge marketing machine.
    I’ve made a promise to myself that if MS does not make SP easy to program to in it’s next version I am abondoning it. I’m a developer and the developing experiene is is bad. I have to install SharePoint on my development machine to get anything done.
    I find m find myself programming on the server machine many times… this is simply not right.
    MS technology has a lot going for it but the next iteration of the product has to be focused on standard oriented designers and developers.
    Atm I see all of these problems as a challenge to solven, using DDD for example, (I’m a moderate optimist) but I also see that php/open source friends are cranking out beautful solutions with CMS systems like Drupal & co.
    MS, do the right think please! Developers, developers, developers?

  2. Pingback: O Futuro do Sharepoint | RuanWeb
Comments are closed.