Ramon’s talk at the Digital Pond, “The Responsive Mindset”, centred around getting into the right mindset to start planning and developing a successful responsive website project. This talk also covered common CSS frameworks, and why you should avoid them if you want to achieve a truly responsive website.

1. The
Responsive
Mindset
Ramon Lapenta
@ramono
#RWDPond
Friday, 19 April 13

2. How do we define
responsive?
Friday, 19 April 13

3. To react quickly
and positively.
Friday, 19 April 13

4. A positive reaction
Flickr credit: @whisperwolf
Friday, 19 April 13

5. Responsive web design
is a design approach that
aims to create interfaces
that react quickly and
positively to the user’s
conditions.
Friday, 19 April 13

6. Conferences
CSS3
Media queries
Javascript
libraries
Blog articles
Friday, 19 April 13

7. So where to start?
Friday, 19 April 13

8. What options are available?
Can I do it myself?
Does it work on all devices?
Does it have a fallback?
Does it make the experience better?
Friday, 19 April 13

9. Performance
Flickr credit: @myoldpostcards
Friday, 19 April 13

10. Friday, 19 April 13

11. Big screen
!=
Better connection
Friday, 19 April 13

12. Battery life
Memory
Graphics
Flickr credit: @luxuryluke
Friday, 19 April 13

13. The oooh
shiny effect.
Flickr credit: @intvgene
Friday, 19 April 13

14. Make decisions
based on research
Good for any project.
A must for responsive.
Friday, 19 April 13

15. Flexibility
Flickr credit: @lyntally
Friday, 19 April 13

16. We always find ways to make our work faster and efficient.
http://imgur.com/gallery/Q8kV8
Friday, 19 April 13

17. The next big thing TM
Friday, 19 April 13

18. Flickr credit: @donshall
Trying to do everything.
The next big thing TM
Friday, 19 April 13

19. A self contained black
box of no-touchiness
Eric Meyer
Friday, 19 April 13

20. If a framework doesn't do
exactly what you need, it's
probably best not to use it.
Friday, 19 April 13

21. Accessibility
Flickr credit: @furbyx4
Friday, 19 April 13

22. Assume less about your users
and their environments.
Friday, 19 April 13

23. We don’t have any non-Javascript users
No, all your users are non-JS while they're
downloading your JS
Jake Archibald
Friday, 19 April 13

24. Accessibility pro-tip:
Leave styling to CSS and
use JS only to change the
“state” of an element.
Friday, 19 April 13

25. Knowing your code from top to bottom is
essential to have total control over it.
Using frameworks doesn’t help with that.
Friday, 19 April 13

26. Standards
Flickr credit: @rawmusic
Friday, 19 April 13

27. Standards are there to make
us more organised with
file structure, class names,
modules, methods,
do's and don't s.
Friday, 19 April 13

28. CSS for RWD can get
pretty messy, pretty fast.
Friday, 19 April 13

29. A code style guide help us
keep projects tidy and
future-friendly.
Friday, 19 April 13

30. So, responsive is...
Friday, 19 April 13

31. Receptive
Understanding
Sympathetic
Friday, 19 April 13

32. These three words
will make us be more
careful about the user
needs.
Friday, 19 April 13

33. Caring about our users
=
Happier users
Friday, 19 April 13

34. Thanks.
Ramon Lapenta
@ramono
#RWDPond
Friday, 19 April 13