Literra Magento 2 Manual | Installation, Responsive Emails & Configuration

Chapter 01

Overview and features

Literra is a Magento 2 extension that applies a consistent visual design to standard HTML emails that have already been rendered . Rather than replacing every Magento template manually, you select a design in the admin. Literra applies its styling through the supported Magento template renderer.

One design for customer communication after checkout.Literra handles presentation. Magento and your installed store modules continue to supply message content, order values, shipping details, payment information and email delivery.

Design

12 + 1 options

Twelve visible presets from the Classic, Modern and Minimal families, plus Custom / Store Colors.

Configuration

Per Store View

Design, primary and accent colors, and activation are configured within the selected scope.

Preview

21 email types

Sales and status emails use real data; other standard emails use safe sample data.

Daily workflow

Preview and test email

Preview in the Literra dashboard or directly from an order; test sending for suitable real emails.

Additional features include storefront color detection, the existing Magento email logo, responsive styling, carefully structured payment information, a test address saved per Store View and a deliberately streamlined admin interface.

No new mail engine: Literra is not an SMTP provider, a newsletter system, a drag-and-drop editor or a generator for invoices or PDFs. It does not replace the content of Magento email templates or modify prices or payment methods.

Chapter 02

Requirements before installation

Area	Requirement	Notes
Magento	Magento 2 with a working admin and email templates	Verify your specific Magento and PHP combination in a test environment. This manual does not provide an exhaustive verified compatibility matrix.
PHP	A PHP version supported by your Magento installation	Follow the system requirements for your Magento version and the technical requirements of the Literra package supplied to you.
Permissions	Shell access to the Magento root directory and suitable admin ACL permissions	Required for module installation, compilation, deployment and cache operations.
Email delivery	Configured Magento mail transport	Test emails use the existing delivery configuration. Literra does not install an SMTP server.
Color detection	cURL and a publicly accessible storefront	Color detection reads storefront HTML/CSS only when explicitly requested. Password-protected staging sites may not be fully analyzable.
Frontend	No specific storefront theme required	Literra is not limited to Hyvä. Still test customizations and third-party modules.
Store operation	Working Magento orders and, where relevant, existing shipment, invoice and credit memo documents	Required for realistic previews and test emails.

Before installing in production: Create current file and database backups, retain the previous module version and test the package on a staging instance first. Run commands as the Magento file owner.

Chapter 03

Installing Literra in Magento 2

Magento installation commands

Shell · Initial installation

php bin/magento module:enable Vermonta_Literra
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy -f de_DE de_CH en_US
php bin/magento cache:flush
php bin/magento module:status Vermonta_Literra

The module files must already be present in app/code/Vermonta/Literra/ before you run these commands from the Magento root directory. Include your actual admin locales when deploying static content; your installation may need additional locales. In development mode, static content deployment may not be necessary after every change. For production, it is part of a proper release process.

Installation successful: module:status lists Vermonta_Literra as enabled, Literra appears in the Magento admin and the design previews load correctly.

Chapter 04

Deploying to production

Deploying a module to a live Magento 2 store should be controlled. Back up the store, transfer the tested module and follow your Magento environment's normal maintenance procedures. The commands in Chapter 03 include compilation, static content deployment and cache clearing.

Maintenance note: If you use Magento maintenance mode during deployment, leave it enabled until the commands have completed successfully and you have performed a functional check. If errors occur, resolve them or restore the previously tested version.

Why static content deployment matters

The Literra dashboard uses admin CSS and JavaScript for design tiles, color detection, previews and interactions. Missing assets after an update can cause an unstyled screen or nonfunctional controls. Compilation alone does not reliably publish these browser assets.

Shell · When admin assets are missing

php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy -f de_DE en_US
php bin/magento cache:flush

Manually deleting entire directories such as vendor/ or generated/ is not necessary for a normal Literra installation. Respect existing CI/CD workflows, file ownership, symlinks and release directories managed by your hosting provider.

Chapter 05

Opening Literra in the Magento admin

In the Magento admin, navigate to Marketing → Communications → Literra. The main Literra dashboard contains Store View selection, design tiles, custom colors, activation, email previews and test sending.

Select the Store View at the top left

Choose the specific Store View for which you want to configure Literra. Existing orders retain their original Store View context.

Choose a design

All twelve presets are displayed at once in large tiles. Select Custom / Store Colors to use your own colors instead.

Set colors if using Custom

Enter a primary and an accent color manually or start the built-in color detection.

Save settings

Use Save settings to apply your selection. Simply clicking a suggested color does not save it permanently.

Check the email preview

Choose an email type, select a real order if needed, and generate a preview. Also test delivery for eligible emails.

Enable Literra

Enable Literra in the selected Store View only after successful testing, then save your settings again.

Minimal settings: There is no separate salutation option. Existing Magento email text and greetings remain authoritative. Continue to manage the email logo in Magento.

Chapter 06

The twelve email designs and Custom

Literra includes twelve ready-made designs divided into three style families. The entire selection is visible in the admin at once. There are no hidden groups or tabs to navigate.

Style family	Design presets	Appearance
Classic	Classic Navy Classic Olive Classic Burgundy Classic Charcoal	Understated, classic color schemes with clear visual hierarchy.
Modern	Modern Ocean Modern Coral Modern Violet Modern Forest	More vivid color accents and contemporary spacing.
Minimal	Minimal Ink Minimal Sand Minimal Blue Minimal Moss	Restrained color palettes and calm email layouts.
Custom	Custom / Store Colors	Your own primary and accent colors based on the Modern layout.

What “twelve designs” means: Literra provides twelve coordinated presets, not twelve independent email rendering engines. Differences come from the style families, their colors and presentation. All use the same central Magento email process.

Choosing a preset

Select the correct Store View, click your preferred design tile, save the settings and check the result using a real email preview. Enable Literra for that Store View only when both design and content look right.

Chapter 07

Automatically detecting store colors

The thirteenth option, Custom / Store Colors , provides exactly two key values: primary and accent color. You can enter both manually. Literra can also check the public storefront and suggest suitable colors.

Select a Store View

Color detection uses the configured public URL of the selected Store View.

Choose Custom / Store Colors

Open the option with your own primary and accent colors.

Click “Use colors from my store”

Literra retrieves the publicly accessible storefront and a limited number of relevant CSS files.

Review the suggestions

Choose suggested primary, accent and, if offered, alternative colors. Check whether the detected values match your brand.

Save settings

Apply the chosen values and then check an email preview.

How color detection works

Literra examines HTML and CSS from the public storefront, including CSS variables and prominent colors used in buttons and navigation. It does not run continuously in the background or rely on an external AI service. The request happens only when initiated in the admin.

Network protection: Requests are restricted to the configured store domain and permitted public destinations. Time, size, redirect and CSS-file limits help prevent unintended access. Internal networks and arbitrary third-party hosts are not allowed as analysis targets.

If suitable colors cannot be found: Password-protected staging sites, blocked SSL connections, CSS hosted outside the store domain, or colors generated only by JavaScript can limit detection. Enter primary and accent colors manually instead.

Chapter 08

Store Views and activation

Magento stores can serve different languages, countries or brands through Store Views. Literra respects these boundaries, allowing a German Store View to use a different email design from an international one.

Setting	Effect
Store View selection	Sets the store context you are currently editing.
Enable / disable Literra	Turns Literra styling on or off for the selected Store View.
Design	Selects one of twelve presets or the Custom option.
Primary color / Accent color	Sets the Custom colors for the selected Store View.
Test address	Saved separately for each Store View; Magento's General Contact address is used as a fallback if none has been saved.

Order Store View: A preview opened from an order uses that order's Store View. Take care not to evaluate a design under the wrong store context.

Recommended order for multiple Store Views

Start with one Store View. Test order and shipping emails, enable Literra and repeat setup for each remaining relevant Store View. Pay special attention to different languages, logo configurations and sender addresses.

Chapter 09

The 21 email types in Literra Preview

The admin preview provides 21 selectable standard email typesthrough one central selector. You do not need to trigger every Magento email just to evaluate its general design.

Two preview data sources: Sales-related messages and their status updates are rendered from suitable real orders or associated documents. Other email types use safe sample data. Sample previews are for visual inspection only and cannot be test-sent.

Category	Preview content	Data source
Orders	Order confirmation and related status notifications	Real order from the selected Store View
Shipments	Shipping notification and related status updates	Real order with an existing shipment
Invoices	Invoice notification and related status updates	Real order with an existing invoice
Credit memos	Credit memo notification and related status updates	Real order with an existing credit memo
Customer accounts	Welcome email, account confirmation, passwords, account information changes and related Magento account messages	Safe sample data
Newsletters	Subscription, confirmation and unsubscribe messages from Magento standard templates	Safe sample data
Contact	Standard message from the Magento contact form	Safe sample data

Previewing an order email

Choose a Store View

Select the Store View to which the order belongs.

Choose an email type

For example, order confirmation, shipment, invoice or credit memo.

Find a suitable order

Use the order picker. The order must belong to the selected Store View.

Use existing documents when required

Shipment, invoice and credit memo previews require the corresponding Magento documents to exist.

Show preview

Check the header, logo, products, prices, totals, addresses, payment details and mobile layout.

Sample previews

Account, password, newsletter and contact messages can be previewed without accessing someone else's account or triggering real password actions. Literra uses neutral sample data for these. Test sending is disabled in this mode.

Chapter 10

Literra Preview directly from an order

You can open Literra Preview without first visiting the main design dashboard. This is useful when a real order includes particular products, payment methods, shipping options or long billing addresses.

Open Magento orders

Navigate to Sales → Orders and open a suitable order.

Choose “Literra Preview”

Launch the preview using the action in the order view.

Choose an email type and review

Literra automatically uses the order's Store View and displays the saved design using that order's real information.

No order changes: Opening a preview does not create an order, change its status or send the regular customer email.

Chapter 11

Sending a test email from the admin

A browser preview is the first step. Seeing the actual message in Gmail, Outlook or Apple Mail is the second. For eligible real email types, Literra can send a test message to an address of your choice.

Search for an order in the input field

Type the order number directly into the order selection field. Literra displays matching orders for you to select. Choose the appropriate order and an email type for which real documents are available.

Check the test address

The address saved for the current Store View is prefilled. If none is saved, Magento's General Contact address is used.

Change and save the address if needed

You can save a test address for that Store View so it is available next time.

Send the test email

Use the test email function in Literra. Check the recipient inbox, spam folder and rendering in the email client.

General Contact: You can normally find Magento's default address under Stores → Configuration → General → Store Email Addresses → General Contact. This is the fallback test recipient, not automatically the destination for regular customer emails.

Check delivery status: A successful handoff to Magento's mail transport does not guarantee delivery to the recipient's inbox. Also check your email server, sending logs and spam folder.

Chapter 12

Which Magento 2 emails does Literra style?

Literra is designed for common Magento 2 standard HTML emails , including orders, shipments, invoices, credit memos, status notices and many account, password, newsletter and contact messages, provided they use supported Magento template processing.

What Literra deliberately does not replace

Magento rules for sender, recipient and when messages are sent
Order, tax, shipping, discount and early-payment discount calculations
Payment methods and their bank or PayPal information
Magento transactional data and existing documents
Custom plain-text emails, third-party renderers and other mail systems that bypass Magento template rendering

Chapter 13

Store logo and Magento email content

Literra uses the email logo configured in Magento. You do not need to upload a second logo in the Literra admin. Existing Magento email settings remain the source for headers, senders and message text.

Managing the email logo in Magento

Check the logo under Content → Design → Configuration. Edit the relevant Website or Store View and check Transactional Emails , especially the Logo Image field and its dimensions.

Sender settings and standard emails

Sender settings remain in Magento. For order and shipping emails, the usual configuration is under Stores → Configuration → Sales → Sales Emails. Literra does not create new sender identities or default templates for every email type.

Logo missing in a test email: Check the public logo URL, file permissions, domain and any .htaccess access restrictions. A password-protected staging logo may appear correctly in the Magento admin but fail to load in the recipient's inbox.

Chapter 14

Responsive emails and email clients

Literra uses the table structures commonly used in HTML emails and email-client-friendly formatting. The goal is consistent headers, content, product details and totals on desktop and mobile devices.

Recommended testing

Check mobile widths around 320 px, 360 px and 390 px.
Test long product names, bank names and dynamic payment details.
Check Gmail in the browser and in its mobile app.
Test Outlook and Apple Mail where relevant to your customers.
Pay special attention to widths, table wrapping, legibility and visible order totals.

Different rendering engines: Even responsive emails may look slightly different across clients because each renders HTML and CSS differently. No single design can guarantee identical rendering in every application or with every third-party HTML fragment.

Design guidance

Less is more: readability and deliverability

Transactional emails should make information clear and quick to access. Use legible text, clear headings and primary and accent colors sparingly. Additional animation, decorative images and extensive custom HTML are generally unnecessary for order and shipping notifications.

No spam guarantee: A restrained layout alone does not guarantee inbox delivery. Sender authentication (such as SPF, DKIM and DMARC), reputation, actual content and the chosen mail service's configuration also matter. Literra does not change these delivery settings.

The two color pickers on the public Literra product page are illustrative only. They do not send color selections to a server or modify Magento settings. Choose or detect actual store colors inside the Literra admin after installation.

Chapter 15

Pre-launch checklist

Run these checks for each Store View. Use orders with the payment and shipping methods your store actually offers.

Module is enabled; admin CSS and JavaScript load without errors.
Correct Store View selected, preferred preset or Custom option saved.
Custom colors and optional storefront color detection checked.
Magento email logo appears in both preview and real test email.
Order confirmation checked with real items, totals, taxes and shipping charges.
PayPal and bank transfer, including long payment details, tested without duplicate headings.
Shipments, invoices and credit memos checked using existing documents.
Account, password, newsletter and contact previews reviewed.
Test email sent to the correct saved test address and received.
Mobile rendering and at least one real email client checked.
Literra enabled and saved in the relevant Store View.
After launch, verify a regular store email without forcing a test involving live customer data.

Chapter 16

Troubleshooting and diagnostics

Symptom	Possible cause	What to do
Literra does not appear in the menu	Module disabled, compilation issue or insufficient admin permissions	`module:status` Check module status, recompile and clear caches, review admin permissions and log in again.
Design tiles unstyled or buttons not working	Admin CSS/JS not deployed or stale browser cache	Deploy static content for the required locales, clear Magento caches and reload the admin page.
Preview displays wrong language or design	Wrong Store View or order belongs to another scope	Check the order's Store View and saved Literra settings.
Shipment, invoice or credit memo preview unavailable	Corresponding document does not exist	Select an order with an existing shipment, invoice or credit memo.
“No HTML MIME part found” / Symfony MIME error	Mail transport or renderer does not return the expected HTML part	Check Magento/PHP mail compatibility, third-party email plugins and the HTML template; inspect the stack trace in `var/log/` for more information.
Store View selector disabled or admin returns 404	ACL or admin session after a module update	Check role permissions, sign out/in, recompile and clear caches.
“Website ID not found”	Invalid Store/Website context	Check that the Store View exists and is linked to the correct website and order.
No suitable store colors detected	SSL, password protection, CSS on other hosts or colors generated by JavaScript	Check public storefront access or enter the colors manually.
Logo missing only in delivered email	Logo URL or header path is not publicly accessible	Check Magento Transactional Emails settings and whether the logo URL can be retrieved publicly.
Test email does not arrive	Magento transport, SMTP or spam filtering	Check the outgoing email configuration and server logs. Successful sending does not guarantee delivery.
Duplicate PayPal label or misaligned payment block	Older Literra installation or different payment HTML	Check the installed Literra module, compilation and actual payment HTML. If necessary, provide an anonymized sample email for analysis.

General diagnostic commands

Shell · Magento root

php bin/magento module:status Vermonta_Literra
php bin/magento deploy:mode:show
php bin/magento cache:status
php bin/magento cache:flush

For PHP errors, inspect the Magento logs under var/log/ and your host's PHP logs. Investigate admin browser errors using the developer console and network tab.

Chapter 17

Literra Updates

Even a code-only update should be handled as a controlled Magento release. Avoid accidentally overwriting customized files. After updating, check payment information, long bank names and display in real email clients.

Update procedure

Back up the previous release

Keep a copy of the installed module, store configuration and a suitable database backup in case you need to restore the previous state.

Control activation while testing

Test in a staging Store View first, or disable Literra for the affected production Store View while validating the update.

Replace the module files completely

Transfer the tested files to app/code/Vermonta/Literra. Do not leave outdated files from earlier releases behind.

Run the Magento commands

Run setup and compilation, deploy admin assets and clear caches.

Retest real email content

Check order emails, PayPal/bank transfer, logo, shipments and test sending before enabling Literra again.

Shell · After transferring the update

php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy -f de_DE de_CH en_US
php bin/magento cache:flush

If a critical issue occurs after updating, restore the last working module release along with the appropriate configuration and, if required, database backup. Run the Magento deployment commands required for that release. Simply copying old code back after database schema changes may not be sufficient.

No one-click downgrade guarantee: Magento setup changes can depend on the version. Discuss restoration procedures for major updates with your technical support provider.

Chapter 18

Operation, privacy and support

Processing email content

Literra processes email HTML within Magento and accesses existing orders for previews using real data. Test emails are sent to an administrator-selected address through Magento's existing mail transport. Treat test orders and preview information as personal store data.

Color detection

The optional color detector retrieves the public storefront. It does not continuously synchronize data or require an external AI cloud service. Network restrictions are designed to prevent unintended access to internal destinations.

Compatibility and limitations

Individual Magento installations may use different templates, third-party modules or custom renderers. These are not automatically covered by standard functionality. Check payment, shipping and SMTP extensions in particular if they modify email HTML independently.

Support and customization

To investigate formatting differences, provide the Magento version, Store View, affected email type, selected Literra design, an error description and, where possible, an anonymized .eml sample email in .eml format. The following services are separate offerings.

Service	Terms	Scope
Technical product support	6 months included	Help with reproducible defects and security issues in the unmodified Literra extension, starting on the purchase date.
Support, updates and compatibility	€249 excluding VAT / additional 6 months	Optional renewal providing technical product support, available bug fixes, security updates and compatibility adjustments for the supported Magento environment.
Personal assistance	Price on request	Individual installation, setup, assessment of custom email templates, modifications and integration into your Magento environment.

Optional renewal: The purchased Literra version remains usable without renewing support. All prices exclude VAT; applicable VAT is added. General Magento issues, third-party modules and customizations are not covered by standard product support.

Enquire about personal assistance and installation

Beautiful emails. No extra work.

Return to the product page to see all 12 designs, the custom option, the feature list and contact information.

Literra product page