Prueba Email Responsivo

Objetivo

Crear una pieza de correo responsiva:

Utiliza el framework: Foundation for Emails también conocido como ZURB
Puedes encontrar la documentación en: https://foundation.zurb.com/emails/docs/

Instrucciones:

Inicia con este repositorio, no olvides dar: npm install.
En la carpeta prueba encontrarás un ejemplo de como debe verse en móvil y en escritorio. Además encontrarás un archivo contenidos.txt con los textos de la pieza.
Las imágenes ya están cargadas en la carpeta /src/assets del proyecto.
Genera tu html en el archivo /src/pages/index.html
Para los estilos propios que necesites generarar utiliza el archivo /assets/scss/template/_template.scss
Deberás construirlo con la sintaxis de acuerdo a la documentación, utiliza los tags: row, columns, etc, además de las de html.

¿Qué valoramos?

Tu habilidad para entender la documentación y aprovecharla. Recuerda recurrir al apoyo de tus mentores y/o tutoriales en google.
La limpieza de tu código e identación debe ser lo más claro posible (SASS y HTML).
Que des preferencia al uso de las sintaxis de ZURB.
El crear tus estilos propios y aprovecha las clases propias de ZURB, recuerda basarte en la documentación https://foundation.zurb.com/emails/docs/alignment.html.
Que integres mediaqueries.
La atención que pongas en los detalles: pesos de texto, colores, superíndices y que observes como varía la alineación en responsivo, etc.

Para terminar

Genera tu carpeta /dist con la cual valoraremos el resultado final.
Es importante revisar tus archivos /src/pages/index.html y /assets/scss/template/_template.scss no olvide subirlo a un git propio y proporcionarnos la liga.

A continuación encontrarás el Readme Original del proyecto de ZURB como referencia, al usar este git como inicio puedes saltarte la parte de instalación del CLI, gracias por tu aportación.

Foundation for Emails Template

Please open all issues with this template on the main Foundation for Emails repo.

This is the official starter project for Foundation for Emails, a framework for creating responsive HTML devices that work in any email client. It has a Gulp-powered build system with these features:

Handlebars HTML templates with Panini
Simplified HTML email syntax with Inky
Sass compilation
Image compression
Built-in BrowserSync server
Full email inlining process

Installation

To use this template, your computer needs Node.js 0.12 or greater. The template can be installed with the Foundation CLI, or downloaded and set up manually.

Using the CLI

Install the Foundation CLI with this command:

npm install foundation-cli --global

Use this command to set up a blank Foundation for Emails project:

foundation new --framework emails

The CLI will prompt you to give your project a name. The template will be downloaded into a folder with this name.

Manual Setup

To manually set up the template, first download it with Git:

git clone https://github.com/zurb/foundation-emails-template projectname

Then open the folder in your command line, and install the needed dependencies:

cd projectname
npm install

Build Commands

Run npm start to kick off the build process. A new browser tab will open with a server pointing to your project files.

Run npm run build to inline your CSS into your HTML along with the rest of the build process.

Run npm run litmus to build as above, then submit to litmus for testing. AWS S3 Account details required (config.json)

Run npm run mail to build as above, then send to specified email address for testing. SMTP server details required (config.json)

Run npm run zip to build as above, then zip HTML and images for easy deployment to email marketing services.

Speeding Up Your Build

If you create a lot of emails, your build can start to slow down, as each build rebuilds all of the emails in the repository. A simple way to keep it fast is to archive emails you no longer need by moving the pages into src/pages/archive. You can also move images that are no longer needed into src/assets/img/archive. The build will ignore pages and images that are inside the archive folder.

Litmus Tests (config.json)

Testing in Litmus requires the images to be hosted publicly. The provided gulp task handles this by automating hosting to an AWS S3 account. Provide your Litmus and AWS S3 account details in the example.config.json and then rename to config.json. Litmus config, and aws.url are required, however if you follow the aws-sdk suggestions you don't need to supply the AWS credentials into this JSON.

{
  "aws": {
    "region": "us-east-1",
    "accessKeyId": "YOUR_ACCOUNT_KEY",
    "secretAccessKey": "YOUR_ACCOUNT_SECRET",
    "params": {
        "Bucket": "elasticbeanstalk-us-east-1-THIS_IS_JUST_AN_EXAMPLE"
    },
    "url": "https://s3.amazonaws.com/elasticbeanstalk-us-east-1-THIS_IS_JUST_AN_EXAMPLE"
  },
  "litmus": {
    "username": "YOUR_LITMUS@EMAIL.com",
    "password": "YOUR_ACCOUNT_PASSWORD",
    "url": "https://YOUR_ACCOUNT.litmus.com",
    "applications": ["ol2003","ol2007","ol2010","ol2011","ol2013","chromegmailnew","chromeyahoo","appmail9","iphone5s","ipad","android4","androidgmailapp"]
  }
}

Manual email tests (config.json)

Similar to the Litmus tests, you can have the emails sent to a specified email address. Just like with the Litmus tests, you will need to provide AWS S3 account details in config.json. You will also need to specify to details of an SMTP server. The email address to send to emails to can either by configured in the package.json file or added as a parameter like so: npm run mail -- --to="example.com"

{
  "aws": {
    "region": "us-east-1",
    "accessKeyId": "YOUR_ACCOUNT_KEY",
    "secretAccessKey": "YOUR_ACCOUNT_SECRET",
    "params": {
        "Bucket": "elasticbeanstalk-us-east-1-THIS_IS_JUST_AN_EXAMPLE"
    },
    "url": "https://s3.amazonaws.com/elasticbeanstalk-us-east-1-THIS_IS_JUST_AN_EXAMPLE"
  },
  "mail": {
    "to": [
      "example@domain.com"
    ],
    "from": "Company name <info@company.com",
    "smtp": {
      "auth": {
        "user": "example@domain.com",
        "pass": "12345678"
      },
      "host": "smtp.domain.com",
      "secureConnection": true,
      "port": 465
    }
  }
}

For a full list of Litmus' supported test clients(applications) see their client list.

Caution: AWS Service Fees will result, however, are usually very low do to minimal traffic. Use at your own discretion.

davidlechuga / proyecto-final