# Email Themes Overview

Finqu email themes provide a flexible and organized way to customize the emails sent to your customers. By following a clear directory structure and using powerful templating features, you can create branded, localized, and dynamic email communications for a variety of customer interactions.

---

## Directory Structure

Email themes are organized into specific folders, each serving a distinct purpose:

- **assets/**: Custom stylesheets (`.scss.liquid` or `.css.liquid`) for your emails. Styles are compiled and injected into templates.
- **config/**: Contains `settings_data.json` for theme configuration and future graphical editing support.
- **layout/**: Layout files (e.g., `theme.mjml.liquid`) define the overall structure of your emails.
- **locales/**: Translation files for supporting multiple languages.
- **snippets/**: Reusable components to simplify template maintenance.
- **templates/**: The actual email templates, each corresponding to a specific email type or event.

This structure keeps your email theme organized, maintainable, and ready for future enhancements.

---

## Email Templates

Templates are the core of your email theme. Each template defines the content, subject, and structure for a specific type of email (such as order confirmations or password recovery). Templates are organized by context (e.g., `customers`, `orders`), which determines the available variables and special features.

A template file typically includes:

1. **HTML (MJML)**: The main email content, written in [MJML](https://mjml.io/) and Liquid for responsive design and dynamic data.
2. **Plaintext**: (Optional but recommended) A simple text version for maximum compatibility.
3. **Schema**: Defines the subject and preview text, supporting variables and localization.

Templates can use global variables (like `customer`, `order`, or `channel`) and special variables for dynamic content. The schema section allows you to personalize the subject and preview using variables, and to localize them for different languages.

---

## Best Practices
- Keep styles simple and email-friendly.
- Always provide a plaintext version for accessibility.
- Use snippets for reusable components.
- Localize templates and schema fields for multilingual support.
- Maintain a consistent naming convention and structure for easier management.

---

By leveraging the directory structure and template features, you can deliver professional, branded, and effective email communications to your customers in Finqu.