Ruby on Rails is a web application framework, we all know that. Rails makes us more productive and let's us focus on the task at hand rather than the technology. But sticking to best practices in Rails, especially when starting out, is very important. In this post, we're going to look at some of the best practices in Ruby on Rails.
If you neglect the best practices of a web application framework, you're running the risk of drifting out of the framework without even knowing it. In the worst cases, your applications starts to become a nightmare for you to handle, making it difficult to develop new features, maintain the project, or bring in new developers. Trust me, stick to the best practices to remain effective and efficient, rather than having people (i.e., your team) pulling their hair out.
The name says it all: Best practices. They are the best and most widely used for a reason. Here's some benefits:
Let's get started.
Continue reading %10 Ruby on Rails Best Practices%
Keeping track of which browsers support which features is practically a full-time job. There are great sites out there like caniuse.com to keep us in the loop and amazing automation tools like Autoprefixer that mean you'll never have to write a vendor prefix ever again.
But still, as diligent front-end developers and designers, we need to ensure that our content is accessible to as many users as possible and even if they don't get the super fancy version, they can still consume the content and get the information they need.
These quick tips will suggest areas that you don't need to fret about (for the most part) whilst still ensuring that your projects work across a wide range of browsers and devices.
For the most part animations and transitions should be subtle effects to make the content stand out more, direct the user's attention or add a bit of personality and character to a page. If animations or transitions aren't supported in a particular browser, the elements will just remain static or snap between states on hover of focus.
As long as the initial state of the animation isn't positioning an element off screen or making it invisible (eg. by setting opacity: 0) then the fact that the element won't move in an old browser doesn't really matter.
In the case of animations, you could try and provide a fallback using JavaScript but I'd really have to think hard about whether the extra effort, code and maintenance is worth the hassle.
In a similar vein to the comments about animations and transitions, I'd also not stress too much about making subtle effects like rotations or skews work across every device either.
Continue reading %AtoZ CSS Quick Tip: Achieving Cross Browser Support%
