# genaker/theme-frontend-tailwind-luna

> Tailwind Luna — Genaker frontend child theme of Magento Luma (Composer-installable)

`composer require genaker/theme-frontend-tailwind-luna`

Canonical URL: https://packagento.com/genaker/theme-frontend-tailwind-luna

## At a glance

- **Vendor**: genaker (https://packagento.com/genaker.md)
- **Latest version**: 1.0.7 — released 2026-04-22
- **Pricing**: Free
- **Package type**: Magento 2 theme
- **Status**: active, accepting new buyers

## Installation

Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them.

1. **Sign in or create an account** at https://packagento.com/customer/account/.

2. **Add the package to your account.** Open https://packagento.com/genaker/theme-frontend-tailwind-luna and complete the free checkout. A licence is minted automatically.

3. **Create or pick a project, then activate the licence on it.**
   - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/.
   - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project.

4. **Add the project credentials to your Magento codebase.**

   Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`:

   ```json
   {
     "http-basic": {
       "packagento.com": {
         "username": "ppk_live_...",
         "password": "psk_live_..."
       }
     }
   }
   ```

   Add the Packagento Composer repository to `composer.json`:

   ```json
   {
     "repositories": [
       { "type": "composer", "url": "https://packagento.com" }
     ]
   }
   ```

5. **Install and apply.**

   ```bash
   composer require genaker/theme-frontend-tailwind-luna:*
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```

## What it does

Tailwind Luna — Genaker frontend child theme of Magento Luma (Composer-installable)

## README

![LUMA powered by Tilewind CSS](docs/tilewind-luma-banner.png)

Composer-installable **Magento 2** theme: **`Genaker/tailwind_luna`** (`genaker/theme-frontend-tailwind-luna`), child of **`Magento/luma`**. **Source / issues:** [github.com/Genaker/Tailwind-Luna](https://github.com/Genaker/Tailwind-Luna).

#### Story

**Tailwind Luna** is from the creators of [**React Luma**](https://github.com/Genaker/Luma-React-PWA-Magento-Theme) — a storefront theme built around speed. This project is the **Tailwind** take on **Magento Luma**: same **Open Source** foundation and **child-of-Luma** inheritance, **no Hyvä**, **no Alpine.js**, and **no magento compliance issue OSL 3.0 license with preservied magento copiryght** on top of Magento — just **Tailwind CSS** (plus small legacy  CSS like `checkout.css` adn some native styles) on top of Magento’s own templates and **Knockout / RequireJS** where the core still relies on them. You can also disable Adobe JS by using React Luma module and use it with any JS.

The goal is **Luma-level comaptability** with a **much leaner CSS payload** and a fast path to a modern utility-first stylesheet — performance you can measure on *your* stack (hosting, FPC, and deploy all matter).

Sample **mobile** Lighthouse screenshots (**Tailwind Luna** vs **Hyvä**) are in **[Lighthouse: sample PDP](#lighthouse-tailwind-luna-vs-hyva-sample)** below (scores vary by hosting, CDN, and cache).

<a id="tailwind-luna-vs-hyva"></a>

#### Install Tailwind Luma Theme For Existing Magento Installation:

If you already have Magento 2.4.x running with demo data or not:

```bash
## 1. Install Tailwind Luna theme via Composer
composer require genaker/theme-frontend-tailwind-luna --ignore-platform-reqs

## 2. Enable the theme module
bin/magento module:enable Genaker_ThemeTailwindLuna

## 3. Run setup upgrade to register the theme
bin/magento setup:upgrade --no-interaction

## 4. Set as default theme (choose one method)

**First, find the Tailwind Luna theme ID:**
```bash
## List all available themes and their IDs
bin/magento theme:list
```

**Example output:**
```
Themes:
Magento/blank - ID: 2
Magento/luma - ID: 1
Genaker/tailwind_luna - ID: 4  ← Use this ID
```

**Now set Tailwind Luma as default:**
```bash
## Method A: CLI (recommended) - replace 4 with your theme ID if different
bin/magento config:set design/theme/theme_id 4

## Method B: Direct database - replace 4 with your theme ID
mysql -umagento -pmagento123 magento -e \
  "INSERT INTO core_config_data (scope, scope_id, path, value) VALUES ('default', 0, 'design/theme/theme_id', 4) ON DUPLICATE KEY UPDATE value=4;"

## 5. Deploy static content
bin/magento setup:static-content:deploy -f n_US

## 6. Clear caches
bin/magento cache:flush
```

#### Tailwind Luna vs Hyvä



| Dimension | **Tailwind Luna** (Luma + Tailwind) | **Hyvä** |
|-----------|-----------------------------------------------------|------------------------------------------|
| **Relationship to Magento Luma** | **Child of `Magento/luma`**: incremental CSS modernization, reuse Luma layout and behavior where it still fits. | **Throws away** the classic Luma storefront theme stack — you **re-platform** the theme, not a light touch-up. |
| **Templates** | **Keep** core `.phtml` patterns; migrate classes and partials **gradually** (Tailwind utilities + optional SCSS merge). | **Big-bang rewrites**: new markup conventions; most of the storefront must be **re-authored** to Hyvä’s template style. |
| **JavaScript** | **Knockout / RequireJS** stay where Magento core still depends on them; you can pair with **React Luma** or other strategies separately. | **Alpine-first** stack **does not** map 1:1 to legacy Knockout flows — **more rework**, not a drop-in swap. |
| **Third-party themes & extensions** | **Luma-compatible** extensions and layouts often work with **targeted** template work — closer to “classic” Magento expectations. | **Extra spend and glue**: Hyvä-only modules, compatibility shims, and vendor-specific upgrades **pile on** cost and maintenance. |
| **Checkout** | **Standard Magento checkout** path (`checkout.css` + core flow) stays familiar; you optimize CSS around it. | **Stock checkout story is gone** unless you pay and integrate **Hyvä Checkout** — another product, another budget line, **drift from core Magento**. |
| **Licensing & compliance** | **OSL 3.0**-friendly path: **child of Luma**, preserve Magento copyright and extension compatibility expectations as usually understood for Luma children. | **Vendor lock-in**: proprietary theme + ecosystem; **ongoing fees** and **dependence** on Hyvä’s roadmap — **not** open-source Luma economics. |
| **Magento Open Source / OSL expectations** | Stays inside the **same** model as other **Luma child** themes: you ship theme code under the **Magento ecosystem rules** you already use for extensions and storefronts. | **We do not treat** Hyvä’s **commercial** theme stack as meeting the **same OSL / source-distribution expectations** as working **on top of** Magento Open Source the way a normal Luma-based theme does — **not legal advice**; verify with counsel. |
| **Proprietary vs “the Magento fork”** | **No** alternate “Magento”; you use **real** Magento Open Source + Luma + this theme’s CSS pipeline. | **Closed commercial product**: Hyvä is sold as **proprietary** software — **not** a gratis, fully open fork of Magento. Historically, **closed** commercial storefront packages have been **sold** in this ecosystem **without** the **same obligations** as the **Magento Open Source** distribution itself; **we are not lawyers** — confirm facts for your org. |
| **Learning curve for Magento teams** | **HTML/CSS + Tailwind** on top of **known** Luma structure — less “new platform” training. | **Steep retraining**: Tailwind + Alpine + Hyvä rules — **wasted** if your team already knows Luma/Knockout. |
| **Migration risk** | **Low blast radius**: ship utility CSS, tighte

_(README truncated for .md surface. Full README on https://packagento.com/genaker/theme-frontend-tailwind-luna.)_

## Recent Versions

| Version | Released |
|---|---|
| 1.0.7 | 2026-04-22 |
| 1.0.6 | 2026-04-22 |
| 1.0.5 | 2026-04-22 |
| 1.0.4 | 2026-04-22 |
| 1.0.3 | 2026-04-22 |
| 1.0.2 | 2026-04-22 |
| 1.0.1 | 2026-04-22 |
| 1.0.0 | 2026-04-22 |

## Dependencies

### Require

| Package | Constraint |
|---|---|
| magento/framework | 103.0.* |
| magento/theme-frontend-luma | 100.4.* |
| php | ~8.2.0\|\|~8.3.0\|\|~8.4.0 |

## Quality

Latest release (1.0.7) fails the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers.


### Compatibility

Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | Pass | Pass | – | – |
| 2.4.8 | – | Pass | Pass | – |
| 2.4.9 | – | – | Pass | not tested |


### Code Quality

Advisory checks against the module's source. Never affect the Compatibility verdict — a phpcs finding can't make a module incompatible.

#### Static Analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 4545 | 59 errors, 4486 warnings (ruleset: Magento2) — 3165 auto-fixable with phpcbf |
| PHPMD | Warning | 2 | 2 rule violations (CyclomaticComplexity:1, NPathComplexity:1) |
| Cpd | Pass | 0 |  |
| Composer validate | Pass | 0 |  |

#### PHPStan

Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | 2 | 2 | – | – |
| 2.4.8 | – | 2 | 2 | – |
| 2.4.9 | – | – | 2 | N/A |


### Tests

Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately.

#### Unit Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |

#### Integration Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |


### Security

Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| Composer audit | Pass | 0 |  |
| Malware scan | Pass | 0 |  |

## Licence and pricing

Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step.

Refundable within 14 days of first purchase via https://packagento.com/account/refunds/.

## Install via Claude Code or any MCP client

The Packagento MCP server can run the licence + project + Composer steps above in one tool call:

```
purchase_and_install_packages(
  composer_names=["genaker/theme-frontend-tailwind-luna"],
  project_id="proj_xxx"
)
```

This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup.

## Vendor

genaker is a Magento 2 vendor on Packagento. See https://packagento.com/genaker.md for their full catalogue.