Simplicity

Harcourt Hamsa — Sun, 30 Apr 2023 18:28:06 +0000

Sometimes the best answer is the simple answer. I know we all know this but according to André Gide, a French author and Nobel Prize winner in literature,

"Everything that needs to be said has already been said. But since no one was listening, everything must be said again."

So, my friends, I'm here to say it again. Last week, I was working on a app and I ran into a case where I wanted users to login first before taking a course. In the event that they are not already logged in, they should be redirected to the login page. If they login successfully, I want to redirect them back to the page they were.

I'm sure this is easy peasy for some of you. Please bear with me. So, I thought about different ways to go about this. I even checked stack overflow. Some people recommended creating a custom hook and writing some mad ass code. Others recommended a library.

At first, I went with the custom hook route. But things got complicated real quick. Incase you haven't figured it out, yes, I am a lazy developer. I figured maybe I'll pickup another task.

While working on the other task, it dawned on me that I can simply pass a parameter in my URL that stores the previous route. So let's say I am in the \courses\:id\ route, when I get redirected to the login page, the URL becomes \login\?next=\courses\:id\

How did I think of this? Anyways, you get the point.

Bye for now,

Why use a Headless CMS with JAMstack

Harcourt Hamsa — Fri, 05 Feb 2021 15:02:09 +0000

This rise in content consumption using new channels, such as smart watches, POS, kiosks, gaming, consoles, voice-activated devices etc. are creating problems for the traditional CMS. This is because the traditional CMS was explicitly created for delivering Web content to websites. Consequently, the demand for a better solution was sought after which was the Headless CMS.

What is a Headless CMS?

A headless content management system, or headless CMS, is any content management system that separates the content layer (backend) from the presentation layer (frontend). Unlike traditional content management systems, a headless CMS is flexible and highly scalable. This is because developers retrieve data from the headless CMS and present it the way they want, which opens up many more possibilities.

The term “headless” comes from the concept of chopping the “head” (the front end , i.e. the website) off the “body” (the back end , i.e. the content repository).

What is JAMstack?

According to the JAMstack official documentation:
JAMstack is an architecture designed to make the web faster, more secure, and easier to scale. It builds on many of the tools and workflows which developers love, and which bring maximum productivity.

The JAMstack is able to achieve this because it does not require an origin server. It is not a "technology stack" because it does not dictate what technology to use.

Why JAMstack and Headless CMS?

The following are reasons to use a Headless CMS with JAMstack:

Frontend Flexibility

Unlike traditional content management systems , Headless CMS separates the presentation layer from the content of the site. Thus, developers are not bound to a specific framework. Similarly, JAMstack does not restrict developers to specific technologies. This, in the long run, helps business and organizations stand-out because they have personalized user experience

Future-proof

With Headless CMS, developers can stay up-to-date with current technologies. This is because the presentation layer is separate from the content. As a result, JAMstack architecture is a perfect match.

Extra security

Since JAMstack sites require no origin servers, it makes them hard to attack. Also, security is provided internally by the various CMS providers. Thus, using a Headless CMS together with JAMstack makes a site extra secure

Performance

It's no news that the JAMstack architecture makes sites very high performant. This is due to the fact that sites are served directly from a CDN. JAMstack, when used with a Headless CMS creates a great user experience. This in turn leads to a high conversion rate, hence growth.

Getting Started

There are a lot of options out there, and picking the right Headless CMS can be challenging. Here are some of the best options available according to G2 Crowd customers reviews:

Agility CMS

Agility CMS is a Jamstack-ready, Content-First API-based Headless CMS. In the world of pure headless CMS and traditional monolithic CMSs, it is designed to offer the best of both worlds: fast and flexible environment for developers as well as easy and powerful tools for marketers. Agility CMS gives both developers and marketers the tools to build, manage, and maintain their content with ease offering built-in Page and Sitemap/URL Management.

Contentful

Contentful is an API-driven headless CMS designed to create, manage and distribute content to any platforms. It gives developers the tools to organize and structure the content their way. Contentful focuses on providing users with the tools to build custom content models for maximum customization.

Kentico Kontent

Kentico Kontent is a headless CMS that simplifies content production for marketers so that they can focus on creating high-quality content without requiring developer involvement. This frees developers to focus on what they do best—building engaging online experiences that look great in every channel.

Jamstack.org provides a comprehensive list of Content Management Systems for JAMstack Sites

Conclusion

Using JAMstack with a Headless CMS is a great solution for organizations that want to scale. There are a lot of tools available to help get started. You can try to build a JAMstack Site with Gatsby or Next.js here .

DEV Community: Harcourt Hamsa