I’m writing this and another post about doing development on the SharePoint user interface and the overall user experiences to display some of my disappointment with issues I thought would’ve been resolved in this upcoming version.
Microsoft has said on record they are supporting browsers that are XHTML 1.0 compliant, and they haven’t said officially (at least where I can find and validated by others) that it will validate as XHTML 1.0. Regardless, we have a new default master page that uses both the strict XHTML 1.0 DOCTYPE as well as it uses the IE 8 X-UA-Compatible META tag that puts
(read more...)Click for Post Details
- January 9, 2010
- Design, SharePoint, User Interface
- 2010, best practice, CSS, development, doctype, javascript, Standards, validation, Web Design, xhtml
- Chris Poteet
- 602 Words
The public beta of SharePoint 2010 is out there for all of us to try who don’t have privileged access, and so now starts the time of deciphering the impact the next version of this very important software package will have on us. One of the things that excites me the most is improvements in the ability to architect information across your entire SharePoint farm with a metadata management service application (formerly SSP), and improvements in navigation by metadata. One thing I was not expecting to improve but has is the use of folders in SharePoint.
The Controversy
SharePoint 2007 brought us
(read more...)Click for Post Details
Stephanie Lemieux wrote an interesting post about the optimal amount of content types to use in SharePoint. This is an interesting discussion, because I’m now fixing the content type taxonomy for a client because the original design firm didn’t give them enough granularity in their content types or metadata. I discuss along these lines with every potential client explaining and justifying the time necessary to do a proper content type taxonomy.
Unlike the author’s recommendation in this post I would venture on the side of over-architecting then under architecting. Let me justify it by the following reasons.
Necessary Granularity
Creating content types that
(read more...)Click for Post Details