Anything from Mr. Addy Osmani is worth taking a look. From the homepage:
Jump-starting jQuery plugins development
A pretty solid project structure for your next jQuery project, and of course using a Yeoman generator, so me likey.
Anything from Mr. Addy Osmani is worth taking a look. From the homepage:
Jump-starting jQuery plugins development
A pretty solid project structure for your next jQuery project, and of course using a Yeoman generator, so me likey.
A build process
We’ve had an implicit build process in the WordPress codebase for a considerable time now. Most of that process is now contained within bumpbot, a little script that lives on the WordPress.org servers. Whenever we update CSS or JavaScript files, bumpbot comes around, minifies them, and commits the result. Despite bumpbot’s efforts, this process is less than ideal. Our source files (in this case, JavaScript and CSS) live alongside our production-optimized files, which causes confusion and makes contributing to core considerably more difficult. Our built output—the files optimized for machines—shouldn’t live alongside the source code that’s optimized for developers, and beyond that, shouldn’t be tracked in source control.
We’re adopting Grunt to write a real build process and help us manage and run our various tools. Grunt is a JavaScript task runner that has a robust ecosystem of plugins focused around building modern web applications. We can include tools such as integrated testing, minification, linting (for PHP, JS, and CSS), image optimization, and LiveReload—and that’s just the beginning.
Using Grunt will be an optional but encouraged part of WordPress development. These tools are all built atop Node.js, which Grunt needs in order to function.
Yes! Grunt is the tool that should be a part of every frontend engineer’s toolbox. Glad to see that core Wordpress is now using it.
A nice collection of tools for front end developers.
From the homepage:
every javascript project you should be looking into.*
*with examples, categories, install commands, CDN links, project and author stats, and more.
Not really a fan of the design, but I do like the functionality of the site, such as the ability to sort by “new”, “tweets”, “watchers”, “contributors”, and “forks”. Nice to be able to see that information clearly.
Dmytro Navrotskyy on Github, has a great repo with a ton of great links for frontend engineers. Definitely worth a look.
Trevor Orsztynowicz on the Caliper.io blog:
The most important takeway?
2013 is going to be an excting time for Webapp developers!
You know it. JavaScript Frameworks are exploding lately. It is turning into a firehose of new technologies for frontend engineers.
I’m a huge fan of CSS preprocessors. They allow you to work faster, and smarter with what is considered frustrating limitations of CSS, and these preprocessors are influencing what will hopefully be baked-in to CSS in the future.
I still think I prefer SASS, for it’s feature set, and Compass. But it’s hard to argue that LESS is made more popular for two big reasons:
Garann Means writing for A List Apart:
Wouldn’t it be nice if we could go from just designing layouts and interactions to designing the whole client side of the application during the same process?
This is where Node comes in.
It seems, when people start using Node.js they fall into one of two camps:
I’m still waffling between the two. Some days I’m person #1, other days I’m person #2.
From the official website:
FRED stands for FRont End Developers, and is (as far as we can tell) the first multi-city meetup for front-end devs.
FRED provides an outlet for front-end developers to talk and share about this exciting and crucial new craft.
Here here. Looking forward to being part of this community.