So, the last post talked about the hubspot set up. This part talks about how we used grunt to automate certain aspects of the build process.
Recently, we’ve started using Hubspot, which is a service that helps companies with their inbound marketing. It provides a content management system (which they call a ‘content optimization system’ :p) that can be hooked in to fairly easily. For me, its syntax is very similar to twig, a popular php templating language. It provides control structures, filters, functions etc. There’s some nice bits and some truly flakey bits – here’s what I’ve learnt so far…
I recently had to do some work with a flat html site that, previously, required loads of copying and pasting identical bits of html (headers, navs, footers). This quickly became tiresome so I turned to good-ol grunt.
I’m trying to follow john papa’s excellent angular design principles article. One aspect to this is setting up routes that resolve service calls that can immediately be called by controllers using the ‘controllerAs’ syntax. However, the question arises of how to test these? After trawling round loads of different articles, I’ve cobbled together a solution that works (for better or worse).
This post is a continuation of this one. It discusses how to output a generic content page that loops through all properties of that page and outputs them automatically. So, for document types that are quite similar, only 1 template is required instead of 1 for each. Also, I’ve been looking at the zurb foundation reveal component, specifically using ajax to load content into it.
This post is about a fix I found for the issues that arise when using zurb foundation’s orbit and interchange plugins at the same time.
This post is about a jQuery auto-suggest plugin I developed that can look up multiple sources and return data.