Understanding Galadriel CSS and Nenyr: A Comprehensive Guide to Declarative Styling

In the fast-paced world of web development, creating maintainable, scalable, and optimized code is more important than ever. For developers who value modularity and clarity, Galadriel CSS presents a powerful solution. At the heart of Galadriel CSS lies Nenyr, a domain-specific language (DSL) designed to simplify the creation of styles in a declarative way. In this article, we will explore the core functionalities of both Galadriel CSS and Nenyr, diving into their unique design philosophies, the mechanisms that drive them, and how they work together to create efficient, utility-first CSS. We will also demonstrate how these tools interact by defining two basic Nenyr documents: one central and one module, each serving to highlight the key principles of Galadriel CSS.

Introduction to Galadriel CSS and Nenyr

Before delving into the specifics of how Galadriel CSS and Nenyr operate, it is crucial to understand the problem they aim to solve. In traditional CSS workflows, style definitions can become tangled and repetitive, making it difficult to manage large-scale projects efficiently. By introducing a modular and hierarchical approach, Galadriel CSS seeks to overcome these issues, leveraging the power of the Nenyr language to bring clarity and flexibility to web design.

What is Galadriel CSS?

Galadriel CSS is a framework designed to optimize the process of styling websites by creating a modular and scalable system for writing CSS. It breaks down the design process into distinct contexts—Central, Layout, and Module—each serving a specific purpose in managing style rules. This hierarchical system ensures that styles are applied consistently across various parts of the website, reducing the likelihood of conflicts and redundancies.

The core feature of Galadriel CSS is its Nenyr integration. Nenyr is used as the language to define styles declaratively, allowing developers to create clear and reusable code. Unlike traditional CSS, which requires imperative definitions of styles, Nenyr allows for the declaration of style properties in a way that mirrors the structure of the document itself.

What is Nenyr?

Nenyr is a domain-specific language that facilitates the creation of styles in a more intuitive and modular manner. Its primary goal is to provide a declarative syntax for defining styles that will later be parsed by Galadriel CSS and transformed into an optimized, utility-first CSS output. Nenyr documents contain classes, breakpoints, variables, aliases, themes and other definitions that define the rules for styling HTML elements, but instead of manually writing each rule in CSS, users define their styles in a structured and hierarchical format.

Nenyr simplifies the process of writing styles by enabling reuse of classes and reducing the complexity of traditional CSS. It works in tandem with Galadriel CSS to transform these high-level, declarative style definitions into a final CSS file that is both optimized and free of redundancies.

How Galadriel CSS and Nenyr Work Together

At the heart of Galadriel CSS lies a system that parses Nenyr documents, generates an abstract syntax tree (AST), and applies specific rules for inheritance, extension, and unicity. Let's break down this process in more detail.

Parsing Nenyr Documents: The Role of the Nenyr Parser

The first step in the Galadriel CSS workflow is parsing the Nenyr documents. When a Nenyr document is processed, it is fed into the Nenyr parser, which generates an abstract syntax tree (AST). This AST represents the structure and content of the Nenyr document, breaking it down into individual style rules that later will be transformed into utility CSS classes to be applied to HTML elements.

The Nenyr parser processes each document, extracting the class definitions, properties, and values. Once parsed, the resulting AST contains all the style information necessary for Galadriel CSS to proceed with the next steps. The key advantage here is that the Nenyr language allows developers to define styles in a declarative manner, leading to more efficient and readable code.

Applying Extension, Inheritance, Context-Aware, and Unicity Rules

Once the AST is generated, Galadriel CSS applies several important rules to ensure that the final CSS output is clean and efficient.

• 
  Extension Rules: These rules allow for the inheritance of styles from parent contexts. In Galadriel CSS, a style rule can extend other rules, ensuring that common styles are reused across different parts of the application. This reduces the need for repetitive code and keeps the style definitions DRY (Don't Repeat Yourself).


• 
  Inheritance Rules: Similar to extension, but focused to classes not context, inheritance allows a class to inherit styles from their ancestors. This makes it easier to manage styles at a higher level and propagate them to child elements.


• 
  Context-Aware Rules: Context-aware rules are designed to apply styles based on the closest context; if Galadriel CSS does not find a value inside the same context, it will look for it higher in the hierarchy until it finds the first value and will use it. This feature applies for variables, animations, aliases, and classes.


• 
  Unicity Rules: One of the most important aspects of Galadriel CSS is its ability to prevent redundancy. The system checks whether a style rule already exists in the global AST. If the style is already present, Galadriel CSS does not create a new rule. Instead, it simply links the existing rule to the Nenyr class, ensuring that the generated CSS is free of redundant styles. This mechanism contributes to the overall efficiency of Galadriel CSS by reducing the size of the final CSS file.

Generating the Final CSS

After applying the extension, inheritance, context-aware, and unicity rules, Galadriel CSS generates the final CSS output. This output is optimized for performance, ensuring that only the necessary style rules are included and that no redundancies are present. The resulting CSS file is utility-first, meaning it contains reusable, atomic classes that can be applied to various elements across the website.

Practical Example: Defining a Central and Module Documents in Nenyr

In this article, we'll walk through the process of setting up Galadriel CSS with Next.js and demonstrate how to create two simple Nenyr documents: one central document for global styles and one module document for a specific component. This basic setup will give you a comprehensive view of how Galadriel CSS works and how to use Nenyr for styling.

Setting Up the Environment

Before we start, ensure you have the Galadriel CSS development server installed and properly configured. You can refer to the

This command sets up the backend server that will process the Nenyr files and generate optimized CSS.

Start the Next.js Development Server: In a separate terminal window, navigate to your Next.js project directory and run:

.

Global CSS Configuration: In Next.js, the global styles are typically defined in the global.css file. To ensure Galadriel CSS styles are included, add the following directive at the top of your global.css:

You can place the central.nyr file inside the src folder, but for this example, we’ll keep it in the root directory for clarity.

Writing the Central Nenyr Document

Inside the central.nyr file, we will define the Central context and create a Nenyr class to style the <body> element. This class will apply flexbox styling to center the contents of the body and set the body’s height and width to 100% of the viewport.

Here, you must use the type “:body”. The Webpack integration client replaces this marker with the appropriate utility class names during the build process.

Defining the Module Document

In addition to the central context, Galadriel CSS also allows you to define module documents. These are used to define styles specific to certain components or parts of your application. For this example, we will create a module document to style a <div> element that displays the text "Styled With Galadriel CSS".

Writing the Module Nenyr Document

Create a file named page.nyr inside the src/app folder. In this file, define a module context and a class for the <div> tag:

Here, we must specify the location of the class in the Nenyr documents, in this case it is located inside a module context named “page”. Then, we need to use the “@module” type to indicate that it is located in the modules map, and then we must specify in what module the class is located, in this case, it is located in the “page” context, and finally specify the actual class we want to use, here is “box”. The final markup will be: className=“@module:page::box”. The integration client resolves this marker to the appropriate utility class names located at the modules map in the page node during the build process.

These examples demonstrate the simplicity and power of Galadriel CSS for modular and hierarchical styling. By separating global and component-specific styles into distinct Nenyr documents, you can achieve a clean and scalable codebase.

The integration client operates as the backbone of Galadriel CSS’s workflow. During development, it scans application components to identify Nenyr-specific placeholders, or "markups," such as “

Here, the class attributes use Nenyr markups, a declarative syntax provided by Nenyr to define the application of styles to HTML elements. This clean and readable approach is invaluable during development, allowing developers to focus on structure and functionality without worrying about utility class clutter.

Output Build Code Example

:body" and "@module:page::box", are no longer present in the class attributes. Instead, the class attributes now contain the actual utility class names that style each element. This transformation is handled by the integration client, which replaces the Nenyr markups with the corresponding utility classes. The build components consist solely of static content, with no direct references to Galadriel CSS or Nenyr remaining in the final output. Each utility class applied to the body and div tags corresponds to a property-value pair defined in a Nenyr class. This streamlined and efficient system highlights the true power of Galadriel CSS: enabling clean, maintainable development code while producing optimized, performance-focused build output.

Generated CSS: The Power of Optimization

The CSS generated by Galadriel CSS during the build process exemplifies its commitment to efficiency. Below is an excerpt from the CSS file located in .next/static/css:

For more about Galadriel CSS:

Thank you for taking the time to learn about Galadriel CSS! I’d love to hear your thoughts and feedback—feel free to share them in the comments below.