# Oy [](http://badge.fury.io/js/oy-vey) [](https://travis-ci.org/revivek/oy)
*Emails, oy vey!*
Render HTML emails on the server with React. Oy provides functionality to:
- Validate props against [email best-practices](https://github.com/revivek/oy/tree/master/src/rules) with `Oy` components.
- Render templates server-side with `Oy.renderTemplate`.
[Blog Post](http://oyster.engineering/post/124868558323/emails-oy-vey-render-emails-with-react) - [ReactConf 2016 talk](https://www.youtube.com/watch?v=KNGj8Y0J01Q)
NOTE: If using TypeScript, the current typings result in quickly growing compilation times. I would suggest not using TypeScript with Oy until [the bug is addressed](https://github.com/revivek/oy/issues/84). If TypeScript is a requirement, [see a workaround](https://github.com/revivek/oy/issues/84#issuecomment-374994906) that disables a subset of type-checks.
## Installation
```
npm install --save oy-vey
```
## Example usage
### Replace table markup with validating Oy components
```js
import React from 'react';
import Oy from 'oy-vey';
const {Table, TBody, TR, TD} = Oy;
export default (props) => {
return (
);
};
```
### Compose higher level components like usual
```js
import React from 'react';
import MyLayout from './layout/MyLayout.jsx';
import BodyText from './modules/BodyText.jsx';
export default (props) => {
return (
Welcome to Oy!
);
};
```
### Inject rendered code into HTML skeleton with Oy.renderTemplate
For example, if using Express.js:
```js
import express from 'express';
import React from 'react';
import Oy from 'oy-vey';
import GettingStartedEmail from './templates/GettingStartedEmail.jsx';
const server = express();
server.set('port', (process.env.PORT || 8887));
server.get('/email/oy', (req, res) => {
const template = Oy.renderTemplate(, {
title: 'Getting Started with Foo',
headCSS: '@media ...',
previewText: 'Here is your guide...'
});
res.send(template);
});
server.listen(server.get('port'), () => {
console.log('Node server is running on port', server.get('port'));
});
```
## Default components
The `Oy` namespace exposes the following components validated against email best practices:
```
Table TBody TR TD Img A
```
## HTML attributes
As of React 16, React will not strip non-standard HTML attributes. That means you can use all the attributes typically required for email templates:
```
align background bgcolor border valign
```
For those migrating from previous Oy versions, note that `bgColor` is now `bgcolor` and `vAlign` is `valign`.
## Oy.renderTemplate API
`Oy.renderTemplate(, templateOptions[, generateCustomTemplate])`
The `templateOptions` parameter is an object with the following fields:
```
title (string, required) - Used by clients if email is opened in a web page.
previewText (string, required) - Short description that appears in email clients
headCSS (string, optional) - CSS that belongs in ``. Note, email clients may strip this out.
bgColor (string, optional) - The background color for the email. '#FFFFFF' is the default
lang (string, optional) - ISO language code
dir (string, optional) - Either 'ltr' or 'rtl'. 'ltr' is the default
```
### Using a Custom Template
If Oy's [default template](https://github.com/revivek/oy/blob/master/src/utils/HTML4.js) doesn't work for you, you can make your own. `generateCustomTemplate` takes in `templateOptions` with an additional property `bodyContent`, which is the rendered body HTML to be inserted into your template. It then returns a string that should be the final email HTML sent to users.
```js
const generateCustomTemplate = (templateOptions) => {
return `
${templateOptions.title}
${templateOptions.bodyContent}
`
};
const template = Oy.renderTemplate(, {
title: 'Getting Started with Foo'
}, (templateOptions) => generateCustomTemplate(templateOptions));
```
## Contributing
```
# Test
npm test
# Compile from ES6 in src/ to ES5 in lib/
npm run compile
```
We welcome contributions. If there's some information missing or ideas for how to make Oy better, please
send a pull request, file an issue, or email [1.vivekpatel@gmail.com](mailto:1.vivekpatel@gmail.com).
The best place to start would be in contributing new rules. [A running wishlist of email validation rules are in the Issues section](https://github.com/oysterbooks/oy/issues?q=is%3Aopen+is%3Aissue+label%3A%22rule+wishlist%22).