× press ESC to close

Jul 18

Hanno

Hanno has three sites that make up their main site, hanno.co. Each of those sites had a cumbersome, heavy workflow attached to legacy systems that resulted in inefficiency and more than a few headaches. As the Hanno team looked for solutions to unify their workflow and improve speed and security, they found Netlify.

Now converted to the JAMstack, Hanno has simplified their workflow resulting in peace of mind and better performing sites. See their process to leave behind various legacy systems and start the journey to spread the JAM.

Tools & Frameworks:

  • Gulp
  • Webpack
  • Babel
  • Metalsmith
  • Middleman
  • React
  • Sass
  • Autoprefixer
  • JS modules
  • DatoCMS
  • Github

Netlify Features used:

  • Versioning
  • Rollbacks
  • Continuous Delivery
  • Branch Deploys/ Deploy Contexts
  • Asset Post Processing
  • Proxying
  • Inbound webhooks
  • Zapier integration
  • Outbound Webhooks & Integrations
  • Git Integration
  • Custom Script Injection
  • Form handling
  • Web UI
  • HTTPS
  • Deploy Previews
.
.

Hanno

Hanno has three sites that make up their main site, hanno.co. Each of those sites had a cumbersome, heavy workflow attached to legacy systems that resulted in inefficiency and more than a few headaches. As the Hanno team looked for solutions to unify their workflow and improve speed and security, they found Netlify.

Now converted to the JAMstack, Hanno has simplified their workflow resulting in peace of mind and better performing sites. See their process to leave behind various legacy systems and start the journey to spread the JAM.

A few words with Jon from Hanno...

Could you tell us about your project?
Netlify
We’ve used Middleman for a long time to host our main site but were always deploying this to ‘traditional’ hosting using a deployment service to DigitalOcean. When we found out about Netlify, we jumped at the chance to get hassle free deployment and to no longer have to worry about server security and optimisation.

Our main website at Hanno is actually several sites:

  • hanno.co: running on Middleman and most content managed by DatoCMS
  • hanno.co/playbooks: a Metalsmith static site with content in DatoCMS and JS plugins to handle instant search.
  • hanno.co/blog: A legacy WordPress blog which we’ve merged under our main domain for SEO reasons.

Netlify’s proxies and speed are the big draws. With the growing power of JS tools, we’re gradually moving away from legacy setups (Middleman in Ruby, WordPress in PHP) and rebuilding components in JS. When building the latest version of our Playbooks, for example, we wanted to use a more optimised stack for rapid deployment and to create a UX that would make it easier to consume and manage the content. We didn’t want to push this content through our existing Middleman setup which powers our main site. Netlify proxies allowed us to easily set up the new /playbooks site as a fresh Netlify site with its own deployment process. We could then launch this to our main domain without needing to worry about integrating fully with the existing codebase, which would have really slowed down our launch time, since we’re not a Ruby-focused team.

We have big plans for improving our stack in the future and switching much more over to a JAMstack approach: when we have the time to take on the rebuild, we’ll hopefully soon be able to ditch our WordPress install and move all our content to RooftopCMS or another service. Then we can focus totally on building an amazing, responsive user experience on the frontend in JS, without having to worry about PHP templates and sluggish, overloaded WordPress servers which crash under heavy load.

Our site deploys automatically when changes are merged into our master repository branch. And we’re using Netlify forms to hook into Zapier - this powers our main contact form and also our job applications system:

  • We create job postings in DatoCMS
  • Middleman dynamically creates pages for those postings, along with an application form for each of them.
  • Netlify tracks submissions on any of those forms and notifies Zapier
  • Zapier adds an Asana task for each job application

That alone is a vastly simpler way to handle building a job portal and gives us way more flexibility than we could find when we were looking at hosted hiring platforms.

Jon Lay Co-Founder
Why did you choose Netlify?
Netlify
Speed and hassle-free management were key. No matter how experienced your engineering team is, managing traditional servers is a time-consuming burden and you never know when you’re going to hit a problem and need to patch something up. Netlify allows us to focus our time on what we’re best at: building frontend user experiences. We don’t need to manage servers and all our content is still easily accessible in a headless CMS. Why spend hours and valuable headspace trying to keep on top of maintaining servers when you can just outsource all of that and be confident that your site is always going to be blazing fast, secure, and reliable? I guess Netlify is the exception to that old “fast, cheap, reliable: pick two” rule!
Jon Lay Co-Founder
What’s your favorite thing about Netlify?
Netlify
Speed and reliability. But I do love the proxies and redirects handling and we used those on a few other sites too.
Jon Lay Co-Founder

All these sites are fast & secure. Join the club.