Photo by Jonathan Pielmayer on Unsplash

Welcome to this three part series on how to build a simple JAMstack site. Over the three articles, we will cover everything needed to build a very simple JAMstack site; from installing the required tools, though to deploying to a CDN. This series is the result of coming from a place of not knowing anything about the JAMstack and wanting to learn through researching and building my own very simple site — which thanks to the wonderful JAMstack community, I was able to do by way of articles, video tutorials, and one-on-one conversations. …

Photo by Jonathan Pielmayer on Unsplash

Welcome to the third and final part of this series, where we build a very simple JAMstack site. To recap our journey so far; in part one we installed Gridsome and created content in Kentico Kontent. In part two we got stuck into Gridsome and created a skeleton HTML website. In part three, we will configure the connection between Gridsome and Kontent, use GraphQL to query Kontent and hydrate our site pages, and finally we’ll deploy our website to Netlify.

Integrate Kontent into Gridsome project

First off, we need to integrate Gridsome with Kentico Kontent and if you remember from article part one, we installed…

Photo by Jonathan Pielmayer on Unsplash

Welcome to part two of this three part series on how to build a simple JAMstack site. In part one, we set up a Kentico Kontent headless CMS project, installed the tools required to develop a JAMstack website, and created a Netlify account in anticipation of deploying to and hosting our website. In part two, we will dive into our Gridsome project and start writing code — this article will focus on setting up a skeleton HTML website in Gridsome.

Seat belts on, we’re gonna build a (very simple) HTML skeleton 💀 website.

Website Development

Now that we’re done with setting up…

Photo by Campaign Creators on Unsplash

Welcome to part three of this guide. In part one — contact segmentation — we learnt how to segment our audience into meaningful groups: personas and contact groups. We created a contact group Millennial Men and we created a persona Victoria. In part two — content personalisation — we created a personalised home page for site visitors in the Victoria persona. In this final part of the series, we will target our contact group with a good old fashioned email newsletter by way of an email campaign.

I remember in the early days of the Internet, unless someone worked in…

Photo by Campaign Creators on Unsplash

A big step in increasing website visitor engagement is to provide a personalised experience. I don’t mean that the home page should address the visitor by their first name, ask how the family is doing, then proceed to discuss the philosophical topic from the previous session. That would be unnerving…

Photo by Campaign Creators on Unsplash

Tools centred around user engagement have become synonymous with the modern content management system (CMS). You would be hard-pressed to find a CMS offering out there that does not come with some form of automated marketing baked into the fibre of the product and the ubiquitous term “experience platform” is a tag-line to most CMS products. In today’s digital day and age, unless a website is actively utilising a level of user engagement — whether it be from simple content personalisation through to complex marketing automation - it is no different than a brochure site from the year 2000. …

Photo by Austin Distel on Unsplash

Re-thinking our approach to the ‘traditional’ website development method resulted in an improved end product and a better outcome for our clients.

Sitting on the Microsoft stack for most of my web development career, I can be forgiven for being of the opinion that the real work happens on the server-side. This has been the convention for a long time as, at an enterprise level at least, application tiers have traditionally been the domain of server-side business logic. Once a traditionalist and a firm believer in the back-end (BE) emphasised approach, I can’t help but be excited about the powerful…

Photo by Ross Sneddon on Unsplash

In this post I want to present the case for a microservice architecture-based website. Such an architecture allows for a powerful CMS to be decoupled from specific user-centric services, providing the flexibility to choose a mix of different best of breed microservices rather than being forced to use those that come OOTB with the CMS.

As these services become more affordable and powerful it makes sense to utilise the best of the best instead of having to compromise on feature set or functionality by using the built-in CMS alternative. …

Jake Kula

DXP Lead at Melbourne digital agency Revium and Kentico Xperience MVP. A knack for digital transformation, the web and all things CMS.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store