So here is the lowdown so far. We are trying to find an effective, repeatable way to easily customise SharePoint form pages, so that we can hide fields or form elements when we need to. The goals were to:
- Allow hidden fields based on identity
- Avoid use of SharePoint Designer
- Avoid customisations to the form pages that unghosted the pages from the site definition
So how have we progressed thus far?.
So let’s knock the rest of this over and pick up right from we left off…
Metrosexual web developer
Socially inept technical guy
[Quick Navigation: Part 1, Part 2, Part 4, Part 5 and Part 6]
|Metrosexual web developer
|Socially inept technical guy
|Luddite IT manager
(sorry … why are you here anyway?)
[Quick Navigation: Part 1, Part 3, Part 4, Part 5 and Part 6]
But there are several problems with the method that prevent it from getting a better CleverWorkaround rating than “Meh”. They include:
- One size fits all, fields are hidden for all visitors irrespective of need.
- You need to modify auto-generated pages
- You need to modify a page from its site definition
- Insecure, relying on client side to hide content/controls is not a secure solution
Well, here we are! After delving into dark arts where everybody but metrosexual web designers fear to tread (HTML and CSS), we then delved into the areas that metrosexual web designers truly fear to tread (packaging, deployment and even some c# code!). Finally, we get to the area where everybody is interested until it happens to get in their way! (Ooh, I am a cynical old sod tonight).
That is Governance!
Continue reading “SharePoint Branding Part 7 -The ‘governance’ of it all..”
This is version 2 of this article, after I went and accidentally blew away my first masterpiece that took literally days to write. If this has ever happened to you, don’t you hate it, that your second version is never as good as your first?
Quick Links: [Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7]
Anyway, this is (attempt 2 of) part 1 of a series of articles that cover SharePoint branding in some detail. Kudos has to be given Heather Solomon especially for her wonderful site and articles on this subject (and author of the book to your left . In Addition, Andrew Connell and Mike have done some great work that helped me in this area.
So, SharePoint branding was the catalyst behind my deciding to make a blog and call it cleverworkarounds. The whole experience at times made me want to change careers, but I ultimately got there. I would go down one path, only to be stumped by a problem, and think I have the solution, only to find another quirk that needed another workaround. So the aim of cleverworkarounds is to determine the least dodgy way to implement branding of a SharePoint installation. No doubt people will disagree with the conclusions I’ve reached, but that’s expected since the cleverness of a workaround really depends on your needs.
So this series of articles will cover a few issues. First some basic master page theory, then I will talk about the difference between branding in WSS3 (the freebie version) and MOSS07 (the pricey one). I will then take you through the quirks of CSS and master pages. Subsequent articles will get into the details of branding techniques and finally finish off by covering the governance issues surrounding branding.
Continue reading “SharePoint Branding – How CSS works with master pages – Part 1″