Here’s a list I’ve created on Twitter for those interested in Front-end Development. The list includes handles for many front-end experts, blogs and websites of interest to Front-end developers.
Subscribe to this list to get tweets from all these Front-enders and stay abreast with latest and coolest developments in front-end.
Answer to a question on Quora
Answer by Aniket Suryavanshi:
The Sold team has joined Dropbox
Automatic: Your Smart Driving Assistant
It's a simple landing page with some JS for the carousel at top, and for the smooth scroll effect on clicking the "What is Automatic" link. The layout is not fluid and not responsive.
This is a responsive landing page. A responsive page is fluid, and in addition uses extra browser capabilities like detecting browser width/height, detecting device type, detecting device orientation (landscape/portrait in case of mobile and tablet), number of colours supported by the device, etc. Responsive pages use media queries to conditionally style a page according to all these critera.
View Answer on Quora
Strict indentation is good primarily for two reasons:
- Avoids nesting mishaps.
Helps produce valid HTML.
- It enforces good readability of code.
Helpful when a programmer revisits that code.
Some languages used in front-end development which enforce strict indentation:
- Haml, an HTML template language.
- Jade, another HTML template langauge.
- Stylus, a CSS preprocessor.
Due to the enormous diversity of devices being used for accessing Web Apps, it has become imperative to develop Web Apps in a way such that they are usable and attractive on devices of varying screen sizes and capabilities. Here’s a presentation which will provide a bird’s eye view of the techniques useful for building Responsive Web Apps. It is based on the talks I have given on the topic.
The presentation is made using Impress.js. It offers better visual effects and control over the flow of slides than apps like Powerpoint, so decided to give it a try. The website runs on a bare-bones Node.js app hosted on OpenShift.
There are many advantages to using ID attributes in your HTML that are unique not only to a page, but unique to the entire app.
This is especially more useful while working on someone else’s project. Whenever styles for a specific ID are changed, one can be sure that the new styles won’t be affecting any of the elements on other pages.
Application-wide unique IDs also help reduce testing time and efforts. One doesn’t have to check the entire app to be sure that they haven’t messed up anything due to their recent changes.