Mirrors/tabler
1
0
Fork 0
mirror of https://github.com/tabler/tabler.git synced 2025-12-21 17:34:25 +04:00
Code Issues Projects Releases Wiki Activity

Minor spelling and grammar improvements to emails docs (#2191)

Browse Source 
Co-authored-by: Paweł Kuna <1282324+codecalm@users.noreply.github.com>
This commit is contained in:
ethancrawford
2025-03-11 04:55:52 +08:00
committed by GitHub
parent e3d68d6aab
commit 922bb0346a
4 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.changeset/quick-taxis-impress.md Normal file
View File

@@ -0,0 +1,5 @@
---
"@tabler/core": patch
---
Minor spelling and grammar improvements to emails docs

2
core/docs/emails/introduction/compiled-html.mdx
View File

@@ -9,7 +9,7 @@ seoDescription: The compiled HTML files from the Tabler Emails package are ready
## Compiled version of the template ## Compiled version of the template
If you only want to change a content - text or images - of the email template, you can just use the compiled HTML files - `compiled.html`. They are ready to use, and you need only a basic knowledge of HTML to modify them. If you only want to change content (text or images) of the email template, you can just use the compiled HTML files - `compiled.html`. They are ready to use, and you need only a basic knowledge of HTML to modify them.
## How to modify the compiled HTML files ## How to modify the compiled HTML files

8
core/docs/emails/introduction/contents.mdx
View File

@@ -44,17 +44,17 @@ The **Tabler Emails** package is organized into a clear and efficient folder str
### 1. Email Templates: `emails/` ### 1. Email Templates: `emails/`
This folder contains <EmailsCount /> email subfolders, each with a specific template. Each email folder contains the following files: This folder contains <EmailsCount /> email subfolders, each with a specific template. Each email folder contains the following files:
* Compiled HTML files for light and dark themes. Read more about its usage in the [Compiled HTML](/docs/emails/compiled-html) section. * Compiled HTML files for light and dark themes. Read more about their usage in the [Compiled HTML](/docs/emails/compiled-html) section.
* Source HTML files for light and dark themes. Find more information in the [Source HTML](/docs/emails/source-html) section. * Source HTML files for light and dark themes. Find more information in the [Source HTML](/docs/emails/source-html) section.
* Screenshot images for desktop and mobile views. * Screenshot images for desktop and mobile views.
* Assets folder with images used in the email template and the CSS file with styles * Assets folder with images used in the email template and the CSS file with styles.
### 2. Images: `images/` ### 2. Images: `images/`
It contains 4 subfolders with images used across the different email templates: It contains 4 subfolders with images used across the different email templates:
* `chart-donuts/`: Images of donut charts with different fill. * `chart-donuts/`: Images of donut charts with different fills.
* `icons/`: [Tabler Icons](/icons) used in the email templates, in PNG version. * `icons/`: [Tabler Icons](/icons) used in the email templates, in PNG version.
* `illustrations/`: PNG versions of [Tabler Illustrations](/illustrations) for light and dark themes. * `illustrations/`: PNG versions of [Tabler Illustrations](/illustrations) for light and dark themes.
* `overlays/`: overlay images used in the email templates. * `overlays/`: Overlay images used in the email templates.
### 3. License: `license.txt` ### 3. License: `license.txt`
This file contains the license information for the Tabler Emails package. This file contains the license information for the Tabler Emails package.

8
core/docs/emails/introduction/source-html.mdx
View File

@@ -3,8 +3,8 @@ title: Source templates
order: 3 order: 3
seoTitle: Tabler Emails - How to use the source HTML email templates seoTitle: Tabler Emails - How to use the source HTML email templates
description: Learn how to use the source HTML email templates from the Tabler Emails package. description: Learn how to use the source HTML email templates from the Tabler Emails package.
summary: The source HTML files from the Tabler Emails package needs a bit more work that the compiled ones. Learn how to use them. summary: The source HTML files from the Tabler Emails package need a bit more work than the compiled ones. Learn how to use them.
seoDescription: The source HTML files from the Tabler Emails package needs a bit more work that the compiled ones. Learn how to use them. seoDescription: The source HTML files from the Tabler Emails package need a bit more work than the compiled ones. Learn how to use them.
--- ---
## Source version of the template ## Source version of the template
@@ -14,9 +14,9 @@ If you want to make more advanced changes to the email template, you can use the
## How to modify the source HTML files ## How to modify the source HTML files
1. Open the `source.html` file in your favorite code editor. 1. Open the `source.html` file in your favorite code editor.
2. Open the `theme.css` file from `assets/`* directory in the same editor. 2. Open the `theme.css` file from the `assets/`* directory in the same editor.
3. Change all the content and styles as needed. 3. Change all the content and styles as needed.
4. Use a selected tool to inline the CSS styles into the HTML file. There are a lot of options, like: 4. Use a selected tool to inline the CSS styles into the HTML file. There are a lot of options, such as:
* Online tools like [Juice](https://automattic.github.io/juice/) or [Mailchimp CSS Inliner Tool](https://templates.mailchimp.com/resources/inline-css/). * Online tools like [Juice](https://automattic.github.io/juice/) or [Mailchimp CSS Inliner Tool](https://templates.mailchimp.com/resources/inline-css/).
* NPM tools like [juice](https://www.npmjs.com/package/juice) or [inline-css](https://www.npmjs.com/package/inline-css). * NPM tools like [juice](https://www.npmjs.com/package/juice) or [inline-css](https://www.npmjs.com/package/inline-css).
5. Save the output HTML file. 5. Save the output HTML file.