purewebmedia.biz - Victoria Web Development with LibSass, Node.js, Gulp

Victoria Web Development with LibSass, Node.js, Gulp | Pure Web Media | Web Design and Drupal CMS Web Development, Victoria BC

Purewebmedia.biz Spined HTML

Victoria WebMinutiaewith LibSass, Node.js, Gulp | Pure Web Media | Web Design and Drupal CMS Web Development, Victoria BC Skip to main content ServicesPortfolioAboutHomeArticlesSupportContact Analyze Design Develop Launch Victoria WebMinutiaewith LibSass, Node.js, Gulp Printer-friendly version Thursday, January 7, 2016Our Drupal WebMinutiaeTools At Pure Web Media, we are unchangingly looking to wastefulness forward thinking with practicality in our tideway to coding within web development. Traditionally, we have been fans of the Omega subtheme framework since version 3, going when many years, but we're particularly fond of version 4 in combination with the "bleeding edge" default starterkit. At the time of this writing, Drupal 8 is capable for small projects but currently not nearly as mature in terms of advanced capabilities than Drupal 7 due to the thousands of modules misogynist for it. This vendible gives an overview of our use of LibSass for Sass compilation in combination with the task-runner, Gulp. LibSass instead of Ruby We've been long time users of Sass and Compass, which get installed as Ruby gems. Ruby Sass and LibSass are similar with the main differences being the implementation and compiling speed. LibSass is a library, a C/C++ port of the Sass engine which was built to bring Sass to many other languages instead of just Ruby. LibSass allows us to compile our stylesheets without having to depend on Ruby, which is a good thing considering managing variegated version of Ruby can be a pain and wilt quite slow. LibSass was the wordplay for developers who want something faster to compile Sass.  The Mac OS and Linux come with Ruby once installed. It's typically painful to get things going on Windows, but sooner it too makes it to the Ruby party. If you have been developing with these tools, you're probably familiar with RVM (Ruby Version Manager) which will indulge you to switch between variegated Ruby versions for various projects. However, as we have been paying sustentation to LibSass and without using it on a few projects, we find it much faster and involves less management than Ruby. Closely pursuit minutiae virtually LibSass, it appears to us that LibSass will overtake Ruby Sass in terms of overall performance, and so for the time being, we are sticking with those tools especially since the Omega subtheme with the "bleeding edge" starterkit is designed to take wholesomeness of them. Task Runners: Gulp, Grunt with Node.js Both Grunt and Gulp are known as 'Javascript task runners' and are used widely within web development. What these tools can do is indulge you to fire off some worldwide tasks you want to perform when you save a file. For example, we use Gulp to incorporate tasks such as browser-sync to refresh our pages in all unshut browswers automatically after saving our Sass files; node-sass-globbing accounts for the SMACSS structure of our stylesheets; gulp-shell allows us to incorporate drush commands into our tasks to well-spoken the enshroud surpassing the browsers refresh. The list goes on and you can tailor these tasks for your own purposes. We were just getting cozy with Grunt when withal came Gulp which showed unbearable promise to get our sustentation and from a few projects we've tried with it, Gulp has lived up to expectations. Both task runners use Node.js (a JavaScript runtime built on Chrome's V8 JavaScript engine) and both work powerfully well, so I would say for for now whichever task-runner you segregate is largely arbitrary, but as mentioned, we're unchangingly looking ahead. Daniel Pataki has written an spanking-new vendible on the comparison of these two task runners, so trammels out his vendible to learn increasingly well-nigh the two technologies from a increasingly in-depth perspective. Node.js comes with NPM, which handles all your Node packages, like Gulp and Browsersync (but note that Windows users need NPM3 considering theoretically Windows can't deal with the multilevel nesting structure of node_module dependencies). What Should You Use? The tools whilom are just one combination of many tools that are out there for web development. We are not advocating that you should use these tools specifically but in our experience, the use of LibSass and Gulp has drastically sped up our minutiae time. Of undertow we are acknowledging that you have to put the time in to learn these tools first but realistically it took us well-nigh two days of solid reading and experimenting to learn these approaches. We feel it's a worthwhile effort which allows us to both stay up to stage with wearing whet technologies and ultimately wilt increasingly efficient at our work considering in the end, we all want to work smarter and have increasingly time for things like getting outside with your friends for that bbq or the road trip, or that glass of wine on the patio... Stay tuned for future wares on how to setup your environment with these tools. Resources The Omega 4.x Manual Streamlining theme minutiae with Omega, LibSass and Gulp Gulp for Beginners Testimonials Pure Web Media was a pleasure to work with. Raj is professional, creative and extremely fast! I felt like I was in capable hands through the whole process... Vanessa Lianne Designs read increasingly RecentWaresVictoria WebMinutiaewith LibSass, Node.js, Gulp Drupal 8 CMS Has Landed Drupal 6 Support to End in Feb 2016 Responsive Inline Images with the Picture module and CKEditor 4 How to Setup Drush on Shared Hosting 1 of 6next › read increasingly © 2018 PureWebMedia.biz Links Services PortfolioWell-nighHomeWaresSupport Contact Social Media facebooktwitterlinkedin Contact 308 - 1138 View St. Victoria, BC V8V 3M1 250-208-5898 info@purewebmedia.biz