https://github.com/sparkpost/template-library
A collection of example email templates for use with SparkPost
https://github.com/sparkpost/template-library
email postman-collection sparkpost templates
Last synced: 5 months ago
JSON representation
A collection of example email templates for use with SparkPost
- Host: GitHub
- URL: https://github.com/sparkpost/template-library
- Owner: SparkPost
- License: apache-2.0
- Created: 2017-02-20T16:44:18.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2018-03-27T19:57:14.000Z (about 8 years ago)
- Last Synced: 2025-05-21T08:48:49.929Z (about 1 year ago)
- Topics: email, postman-collection, sparkpost, templates
- Language: HTML
- Size: 53.7 KB
- Stars: 5
- Watchers: 14
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[Sign up](https://app.sparkpost.com/join?src=Dev-Website&sfdcid=70160000000pqBb) for a SparkPost account and visit our [Developer Hub](https://developers.sparkpost.com) for even more content.
# SparkPost Email Template Library
This repository contains a selection of prebuilt email templates designed for use with SparkPost. Some, like the [features template](templates/features/) are meant to showcase SparkPost's personalisation capabilities. Others are starting points for your own email. For example, [here's a simple responsive template](templates/responsive/).
Each template is available as HTML, text and sample substitution data. You can also import a Postman collection containing all templates as SparkPost REST API requests.
[](https://app.getpostman.com/run-collection/d2f3d0149a306779aa1e)
# Regenerating The Postman Collection
To automatically create a Postman collection from the template files:
```bash
python tools/buildPostmanCollection.py
```
# Contributing
Transparency is one of our core values, and we encourage developers to contribute and become part of the SparkPost developer community.
## Contribution Steps
1. Fork this repository
2. Create a new branch named after the issue you'll be addressing. Include the issue number as the branch name. For example: a branch named "ISSUE-8" would address issue number 8.
3. Make your changes, adding new templates or updating existing ones as necessary.
4. Remember to [regenerate the Postman collection](#regenerating-the-postman-collection) to include your changes.
5. Submit a new pull request applying your branch to the develop branch of this repository.