Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Branding SharePoint for Evolving Internet Devices
Similar a Branding SharePoint for Evolving Internet Devices (20)
Último
Último (20)
Branding SharePoint for Evolving Internet Devices
- 1. Your SharePoint Branding Experts Branding SharePoint for Evolving Internet Devices Eric Overfield SharePoint Branding and UI Lead PixelMill
- 2. Introduction – Eric Overfield • Founder and SharePoint Branding Lead, PixelMill • Working with SharePoint since 2004 • Web Designer since 1998 • Located in Davis, CA blog.pixelmill.com/ericoverfield @EricOverfield linkedin.com/in/ericoverfield
- 3. PixelMill • Developing SharePoint solutions since 2004 • SharePoint Branding and UI Specialists • Developer of Cost effective SharePoint Templates • Your SharePoint Branding Experts
- 4. Agenda • Difference between Devices • Why We Care • Possible Solutions with SharePoint • What about SharePoint 2013?
- 5. What is the Difference Between Devices? "There’s a plethora of devices out there with widely differing abilities – it’s never been more confusing or challenging to create brilliant interfaces that work across them all.” ~ Jeffery Zeldman • Screen Size • Functionality • Usability
- 6. Why Do We Care? • Mobile Devices are Invading • If not now then in a few years. • How old is your Intranet? • Build towards the future, not the past
- 7. So What Do We Do?
- 8. Available Options • Device Specific Interfaces • SharePoint 2010 has Mobile Detection • SharePoint 2013? • One design to rule them all, one design to bind them • Responsive Web Design anyone?
- 9. The Mobile Interface • SharePoint 2010 has a mobile interface • Allows access to documents, lists, calendars, search, SMS alerts • Controlled by USERAGENT • App_Browserscompat.browser • Custom Web Parts, _layouts likely won’t work • Difficult to customize
- 10. Code Once Use Everywhere •Two primary methods • Progressive Enhancement • Responsive Web Design
- 11. Progressive Enhancement • #1 trend for 2012 - .net Magazine • Coined by Steven Champeon in 2003 • Content first, then add styling • Separate Content from Presentation
- 12. SharePoint and Progressive Enhancement • SharePoint was not built with PE in mind • JavaScript and SharePoint • Too much presentation baked into html • i.e. Tables, Inline styles
- 13. Responsive Web Design • #2 trend for 2012 - .net Magazine • Coined by Ethan Marcotte in May 2010 • Use fluid grids to adapt to viewing environment • Uses CSS3 and JavaScript • All devices load same page, use CSS3 to adapt
- 14. Responsive Design Examples
- 15. www.its.ms.gov
- 16. www.its.ms.gov
- 17. www.ariensco.com
- 18. www.ariensco.com
- 19. www.gse.it
- 20. www.gse.it
- 21. SharePoint and Responsive Design • Uses CSS3 (media queries) and possibly HTML5. • SharePoint already has a mobile view • Configure with compat.browser • Generally only one Master Page for all devices. • Wide lists and Site Settings pages are not mobile friendly • Primary issues are with RWD itself!
- 22. SharePoint and Responsive Design • Additional overhead • Does require CSS3 • Bandwidth Concerns • Are mobile users and desktop users the same? • Separate mobile vs Responsive? It’s political?
- 23. What to do? • PE vs RWD vs Separate Mobile • One site is difficult enough to maintain • SharePoint limits our options • Responsive Web Design is worth considering • Define Project • Limit overhead • Find a CSS guru will be key
- 24. Device Channels Anyone? • New to SharePoint 2013 • Interfaces tailored and maps to specific device(s) • Custom Master Pages per Channel • Custom DeviceChannelPanels
- 25. Devices Channels, the Good and Bad • Tailored interfaces • Only works with Publishing Sites • Maintain multiple Master Pages and/or sites • New devices? Maintain that list too?
- 26. The Best of Both Worlds? • Responsive Design and Device Channels • Built a Responsive site for all devices • Use DeviceChannelPanels • Create a Device Channel for special cases • But we have to wait
- 27. Summary • Build towards the future, not the past • Mobile devices will penetrate the corporate firewall • SharePoint 2010 – Response Design • SharePoint 2013 – Responsive Design w/ Device Channels
- 28. Resources • "Responsive Web Design" by Ethan Marcottes http://bit.ly/bcKwQS • Ethan Marcottes’ 20 Favorite Responsive Designs http://bit.ly/ngkI8D • v5, the Responsive HTML5 Master Page for SharePoint 2010 by Kyle Schaeffer http://bit.ly/n8VQZw • SharePoint 2010 Responsive Web design Template by Luis Kerr http://bit.ly/NKPjwX • Configure SharePoint Server 2010 for Mobile Device Access http://bit.ly/cg6fYo
- 29. Your SharePoint Branding Experts Thank You Eric Overfield @EricOverfield blog.pixelmill.com/ericoverfield eoverfield@pixelmill.com
- 30. SharePoint Saturday Redmond • September 22nd, 2012 • www.sharepointsaturday.org/redmond • Branding SharePoint in the Real World – A Panel. 10:50am • Ask the Experts Panel 3:30pm
Notas del editor
- Recording session Slides will be available from blog and twitter Overview talk of SharePoint and new devices Light on tech and howto Don’t worry tech folks, many resources at end.
- Recording session and will make available on blog and twitter, so if you remember one of those then you can always review everything we discuss tonight
- Mr Zeldman founded A List Apart , best practices and innovations in web design. sure, you can zoom in on many smart phones or tablets, but what if you can make tailored expereince for each device? Modern devices share basic ability with css, js though which his a plus
- mobile is invading, for the good, all organizations. if not now then in the next few years. Iphone is estimated to provide 1/3% of gdp. What, you think your next web initiative is only going to last a few years? How long did you last intranet or public facing site last? Built towards to future, not the past, you MUST consider tablets and smart phones.
- Let’s look at what we have OOTB as well as with just minor modifications. Stay away from total code re-write
- Build particular interfaces for specific devices SP 2010 has mobile detection, but it's not good, and difficult to brand What about 2013? We will get to that Design and code an interface that can scale itself to different devices
- Based only on specific user agents Mobile pages do not use master pages, you can modify redirection create mobile control template based on site definition create a mobile adapter for web part Leaving a lot out because I don’t like it, too basic
- Html is very clean and simple Using javascript to determine functionality and add on features as allowed. Yahoo, amazon, etc
- A true PE site should work without JS, SP will not do that. Tables and inline styles breaks the idea of separating content and presentation.
- fluid proportion-based grids (which use percentages pixels) to adapt the layout to the viewing environment All clients effectively load the entire page but using css, hides or replaces elements to tailor the experience to the screen. DOES NOT USE USERAGENT, browser detection, rather works of screen width. Early adopter AIDS.gov
- Mississippi Department of IT
- Midwest and European brand that manufactures outdoor power equipment
- European renewalable energy company
- Uses css3 media queries and js, which is ok with SP. Turn mobile view off in compat.browser found in web applications directory. Look it up. Issues are on next slide.
- Also a lot of overhead, but SP already has a lot of that as well. Not IE7 and IE8 friendly Require CSS3? There is a js ability with jQuery’s help. Does a mobile user need the same information as a desktop user? Adding information vs consuming information. Less real estate and is the navigation necessarily the same? http://mobile.smashingmagazine.com/2012/08/22/separate-mobile-responsive-website-presidential-smackdown/
- Coding techniques to get around some overhead combine files, minimize scripts use wrapper divs that keep large images off mobile browsers
- Device Channels work only with Publishing Sites Allow for one interface for all desktops and another for most tablets let's say. Only 10 device channels per site collection, but do you really want to maintain 10 MP’s?
- I propose that sites be built using RWD principles If you organization will have primarily one mobile device, say an ipad or iphone, then look to create a device channel just for that device. this way you have a site that will respond to almost all devices but a tailored experience towards your primary devices.
- In 2010 I suggest RWD as it is the most compatible with SP allows for the targeting of most devices, Needs one Master page In 2013 still use RWD, but you can think about DC for particular devices if the need arises One primary interface that will work with most devices have the ability to allow a target for a few particular devices easier to manage 2-3 branding efforts rather than many if you attempted to tailor your site to all devices.
- Html5shiv
- Thank You! Don’t forget to check out my blog where you can download this presentation or the recording. Easiest way to get to the material I referenced