Liquid VS hydrogen

Liquid is a template language created by shopify. In my use case I use it for generate html that is almost similar looking but differs in data. So when iterating over my HTML, I need to preview the changes I made combined with my data.

Inside the blog directory, create an index.liquid file. This will be our blog’s homepage. Eleventy provides a number of options when selecting a template engine. For this project, we’ll use Liquid.

Templating engine: SSGs rely on templating engines to define the structure of web pages. These engines enable developers to create reusable templates and incorporate dynamic content. Popular templating engines include Liquid, Handlebars, Mustache, EJS, ERB, HAML, and Slim.

Assuming I understand the ask, I think my approach would be to have a trigger fire when a ticket's custom field is set to "add user to the application." That trigger would notify a webhook. That webhook would be set to the Organization API endpoint with a payload that uses liquid markup to add 1 to the existing Organization's value.

For example, their theme templates use Liquid, which is a html templating system for Ruby. Activemerchant also was released by Shopify, and it provides a interface to major payment providers like PayPal.

In the meantime, Liquid v4.0.4 has been released, and allows building a Jekyll site with the latest Ruby.

Liquid docs - https://shopify.github.io/liquid/

Then, let’s create the simplest template for our static Eleventy page. We’ll write it using Liquid, but since it’s so simple, it won’t take advantage of any useful templating tags for now. Let’s call it index.liquid:

Previously I have used Jekyll for blogging and it has served me well for simple blogs and static websites. Jekyll is a static site generator that relies on Markdown, Liquid, HTML, and CSS. Which means no JavaScript -- a Jamstack without the J. With GitHub Pages you can even host Jekyll sites directly from your repository.2

This acquisition is very much in the context of https://hydrogen.shopify.dev/roadmap/#first-quarter and https://github.com/Shopify/hydrogen - Shopify very much wants to move to the modern era.

And to address your point, it's not gaslighting to say that React enables interactions that would be essentially impossible if restricted to server-side templating. But there's certainly some degree to which trendiness and a desire to attract developers into their ecosystem is driving this as well.

I would say its main selling point is obviously the integration with Shopify. It comes with hooks, components and types to make it really easy to interact with the Shopify API. (They also use an XState state machine for the cart.)

Shopify's got their own headless framework for storefronts built on React called Hydrogen. Just recently came out of beta. Has a built in React hook for GraphQL queries to the storefront.

All the activity around V8 Isolates + "workers" is so cool-- exceptional performance, don't need to think about regions, and CDN-like benefits

Shopify's new store-builder thinks this way too: https://github.com/Shopify/hydrogen

Not sure what documentation you're looking at, because we have a ton here: https://shopify.dev/custom-storefronts/hydrogen

Full Docs and Image Source