Designing in MOSS 2007/WSS 3.0 – “The Pitch” …

Coming from a web “designer” / graphic designer background, I have my fair share of beefs with SharePoint technologies as a web based platform.  I’ll have a fairly detailed post outlining some of that in the next day or so, in the interim I wanted to share a positive experience I had today while a colleague and I were mulling about under the hood, and something just clicked.

I have spent the last several weeks/months and continue to spend my days immersed in Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0. Of course a major part of my focus is dealing with “customizing” the interface.

I am asked fairly often – What makes the next version better in terms of customization – today it finally sunk in and I have my pitch for designing in 2007.

“In past versions of SharePoint technologies I could strip a page down and customize it to the point it was unrecognizable as a “SharePoint” site.  With 2007 technologies, I can not only strip a page down and customize it, but I can also empower users to “Create” pages based on the customized versions without ever writing a single line of code.  That is a huge selling point 2007/v3 has over 2003/v2.

Don’t worry if you have no clue what I am talking about – I will be writing many step-by-step guides and articles on master pages, page layouts, content types, and how they can be leveraged using SharePoint Designer 2007 in the coming weeks.

Stay tuned – I have several other nice treats in the pipe which I’ll be able to share more on soon.

5 comments on “Designing in MOSS 2007/WSS 3.0 – “The Pitch” …

  1. Mike says:

    Cool, looking forward to it!
    I’m wondering.. how do you deal with the placeholders a standard portal installation is expecting on a page? I found out that as soon as I went fiddling around in the master pages broke on the front end because they were missing al kind of placeholders…

  2. shane says:

    Mike,

    It is certainly a pain point at the moment, basically you need to learn what each placeholder is by going through your page layouts/pages matching up the control ID’s.

    If your page layout/page has a control which is supposed to be merged into a content placeholder in the master page and it’s removed, you will get the error you are speaking of.

    I am personally heavily involved with the internet publishing side of things right now, but the WSS v3 (regular sites) seem much the same minus the WCM features. The good news is there are not “too many” pages for you to sift through.

    I’ll certainly share any information I find via the blog as I uncover more! :)

  3. Robin says:

    Well you’ve got my attention ;)

  4. pete says:

    I am wondering where the master pages are for the “My Site” sites and why they are contained on a different port than the rest of the portal.

    Julie have you any experence here?

  5. Mike says:

    Just to add some of my experiences so far…
    Strange thing I discoverd, the url to images in core.css is still _layouts/1033/images but when you look on the file system the images aren’t there, they are actually in the image folder one level above the layouts folder!

    The background images used in the classes .ms-templatepickerunselected div, .ms-templatepickerselected div and .ms-laction in core.css don’t exist on the file system!

    There is (still) no documentation on what purpose the classes used in the css files serve, besides the css is still a mess, I was hoping that with the integration of CMS that would have been fixed. Since the old CMS is using a really neat css…

Leave a Reply