Liquid VS Sass

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

SASS(.scss) [ https://sass-lang.com ]

Traditionally CSS lacked features such as variables, nesting, mixins, and functions. This was frustrating for Developers as it often led to CSS quickly becoming complex and cumbersome. In an attempt to make code easier and less repetitive CSS pre-processors were born. You would write CSS in the format the pre-processor understood and, at build time, you'd have some nice CSS. The most common pre-processors these days are Sass, Less, and Stylus. Any examples I give going forward will be about Sass as that's what I'm most familiar with.

CSS stands for Cascading Style Sheets, and is a scripting language used to style web pages. SCSS stands for Syntactically Awesome Style Sheet, and is a superset of CSS. You can think of SCSS as the more advanced version of CSS, which comes with several features that CSS does not support, such as the SCSS nested syntax, as shown below.

Scss

In the past, you’d need to rely on pre-processors such as SaSS or Less, but not anymore… Native CSS nesting has landed on all major modern browsers.

Sass is also a css preprocessor. Op is likely confused

sass -> An improvement over CSS. It provides nice features for managing CSS. good for mid-sized or even larger projects.

Sass (Syntactically Awesome Style Sheets) - A CSS preprocessor that simplifies and enhances your CSS workflow. Website: https://sass-lang.com/

Personally, my preference is Sass: I find that the mixins, partials, and operators are hugely useful when it comes to creating re-usable snippets of code for a design system. And, since it’s “just” a pre-processor and not a framework, it’s not opinionated in a design sense and there’s no default values (colors, spacing values, etc.) that will need to be overwritten.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.