Back in the day we touched on some of the wonderful upsides of implementing Gulp into your workflow. If you have been following along and happened to install the latest version of Gulp, you may has noticed something horrible happen: nothing worked. I probably should’ve mentioned that the latest major update to Gulp, Gulp 4, is actually a breaking
Building views in NodeJS by incorporating layouts, partials, and everything in between.
Writing HTML sucks, thus we should do everything to minimize the time we spend writing it as much as possible. Thus, we have Handlebars: a lightweight templating system for Node. Handlebars allows us to avoid repetitive code by compiling the final DOM structure of our site via logic, typically compiled by task runners such as Grunt or Gulp.
Node’s most popular package interacting with the most popular file store on the world’s most popular cloud.
We here at H+S are dedicated to one simple cause: creating posts about oddly specific programming scenarios. Somewhere in the world as sad soul is looking to programmatically access files from an S3 server while keeping their bucket private. To that person: we heard you.
There are plenty of reasons you'd want to access files in S3. For example,
Automate tasks to make frontend code production-ready
NOTE: This tutorial was written for Gulp versions <4.0.0. Check out this post for Gulp >4.0.0
Perhaps the whole obligatory-Gulp-tutorial on [Some Coding Blog] thing has become a bit cliché at this point. Haters may do as they will, but I 'll take any opportunity to jam as many SEO keywords I can get
Get started customizing your themes with simple widgets
Here at H+S headquarters, we're pretty into the Ghost blogging platform. It's a lot like Wordpress, except without everything that sucks about Wordpress. It's a Node app, isn't bloated with widgets, is more secure, smarter, prettier, and so on. If you're a dev looking to get a quick clean CMS running, Ghost is pretty much a no-brainer.
Installation guide for ExpressJS with popular customization options
Over the past few months I've found myself spinning up tons of new servers and walking through the process of pushing express apps live.
Because this process always comes at unexpected times, I've never bothered documenting the steps it takes to get a blank box running express. Surprisingly it seems as though few have bothered to walk through every step