views:

57

answers:

0

Hello all, I've been working on a project that has just been outsourced about 1/2 into SharePoint integration. My role is UX/design and all front-end development (HTML/CSS/JavaScript).

This outsourcing is a first for me and I'm wanting to compile some handoff materials that will help the new folks doing the integration. I'm imagining they're not going to use a single line of our back-end code as we were integrating this into SharePoint 2007 and they'll be using SharePoint 2010 and most likely rearchitecting the back-end for their integration.

Here's what I'm come up with so far:

Style Guide:

  • Different page layouts
  • Typography
  • Color palette
  • Images/Photos
  • Buttons
  • Icons
  • Error messaging
  • Forms - label placement, submittal behavior, required field indication

Document all JavaScript - what it does, what pages it appears on (with screenshots).

Instructions like:

  • The site should still work with no JavaScript, document the no JS messaging on all modules (with screenshots).
  • Form validations should all be client-side first, and if no JS, fall back to server-side.
  • Printer-friendly pages - document what should print, what should not print in various sections of the site.

I also have general questions to ask them like:

  • Will they be using jQuery? Do they have jQuery/JavaScript expertise? Will they be re-using my JS code or re-writing everything from scratch? If the latter, I don't need to worry about documenting this aspect so much.
  • What's their cross-browser/platform testing?
  • What will they be doing in regards to accessibility?
  • What will they be doing in regards to site performance.

Wondering what else anyone can come up with. Again, this is the first time I've worked on a project that's been outsourced. The design/front-end is all done, though we now have some opportunity to implement some changes based on user testing we did (an upside) before we hand things off. We'll just be handing off functional, front-end, everything works/looks as it should, but obviously it's not tied to any back-end (you can just run it locally).