Get an introduction how to create and develop your own style guide for SharePoint, Office Add-ins or web application. It will help you save time during development and for future adoptions.
You will learn how to maintain your code and documentation at the same time. Start to develop maintainable, reusable and re-factorable design patterns now and learn what css frameworks can't do for you.
6. Why Branding?
Internal brand awareness
Official information by the company
Increase identification with the company
Employees become brand
ambassadors
Not only to make SharePoint look not look like
SharePoint
25. Potential problems with Frameworks
• How to add custom CSS?
• Documentation of custom CSS?
• New version of framework?
• What do I need from the framework?
• Subscribe to someone else structure
• What if framework structure fundamentally
changes?
LESS SASS
Static HTML Handlebarsjs
32. We’re not designing pages. We’re
designing systems of components.
– Stephan Hay
33. Responsive deliverables should look a
lot like fully-functioning Twitter
Bootstrap-style systems custom
tailored for your clients needs.
– Dave Rupert
46. Style Guide – The benefits
• State and breakpoint changes
• Useful for future designers, devs & others
• Design and Code consistency and
maintainability
47. The Benefits Of Maintaining
• Easier to test
• Improves workflow
• Shared vocabulary
• Useful reference
64. Style Guide Benefits
• For designer / developers / customer / project Owners
• No extra effort on documenting styles
• Build HTML and Design first
• Useful for future development
• See the side effects of CSS changes easier
• Use same styles for SharePoint and Add-ins
65. Thanks to our Sponsors
Silver
Gold
Bronze
Raffle Organized by