You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.MD
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ These guidelines are here so we can all be on the same page. They also help ensu
6
6
7
7
## What types of contributions help?
8
8
9
-
MailMason is an open source project, and we love to receive contributions from our community — you! There are many ways to contribute, from writing tutorials or blog posts, improving [the documentation](https://github.com/wildbit/mailmason/wiki), submitting [bug reports and feature requests](https://github.com/wildbit/mailmason/issues), or writing code which can be incorporated into MailMason itself.
9
+
MailMason is an open source project, and we love to receive contributions from our community — you! There are many ways to contribute, from writing tutorials or blog posts, improving [the documentation](https://github.com/activecampaign/mailmason/wiki), submitting [bug reports and feature requests](https://github.com/activecampaign/mailmason/issues), or writing code which can be incorporated into MailMason itself.
10
10
11
11
## Sources for Support
12
12
@@ -26,8 +26,8 @@ Building and testing highly compatible HTML emails is difficult no matter how yo
26
26
### Technical and procedural considerations
27
27
28
28
* Ensure compatibility across email clients for every change that's accepted. We recommend [Litmus](https://litmus.com)
29
-
* Ensure that code that goes into core meets all requirements in this checklist:
30
-
* Create [issues](https://github.com/wildbit/mailmason/issues) for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
29
+
* Ensure that code that goes into core meets all requirements in this checklist:
30
+
* Create [issues](https://github.com/activecampaign/mailmason/issues) for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
31
31
* Before adding new templates, start out with a feature request issue. We may already have some underway.
32
32
* Keep pull requests as atomic as possible, preferably one new feature per pull request.
33
33
* Be welcoming to newcomers and encourage diverse new contributors from all backgrounds. See the [Code of Conduct](http://wildbit.com/open-source-code-of-conduct).
@@ -36,8 +36,8 @@ Building and testing highly compatible HTML emails is difficult no matter how yo
36
36
37
37
Unsure where to begin contributing to MailMason? You can start by looking through these beginner and help-wanted issues:
38
38
39
-
*[Beginner issues](https://github.com/wildbit/mailmason/labels/beginner) - issues which should only require a few lines of code, and a little testing.
40
-
*[Help wanted issues](https://github.com/wildbit/mailmason/labels/help%20wanted) - issues which should be a bit more involved than beginner issues.
39
+
*[Beginner issues](https://github.com/activecampaign/mailmason/labels/beginner) - issues which should only require a few lines of code, and a little testing.
40
+
*[Help wanted issues](https://github.com/activecampaign/mailmason/labels/help%20wanted) - issues which should be a bit more involved than beginner issues.
41
41
42
42
Both issue lists are sorted by total number of comments. While not perfect, number of comments is a reasonable proxy for impact a given change will have.
43
43
@@ -48,7 +48,7 @@ At this point, you're ready to make your changes! Feel free to ask for help; eve
48
48
## Getting started
49
49
50
50
1. Create your own fork of the code
51
-
2. Setup your local environment by following [the instructions in the Wiki](https://github.com/wildbit/mailmason/wiki/Getting-Started).
51
+
2. Setup your local environment by following [the instructions in the Wiki](https://github.com/activecampaign/mailmason/wiki/Getting-Started).
52
52
3. Make some great changes in your fork
53
53
4. Submit a pull request with a detailed explanation of the change and reasoning.
54
54
@@ -83,7 +83,7 @@ While we don't have an active roadmap, we do have plans to add new templates. Wh
Copy file name to clipboardExpand all lines: README.md
+27-27Lines changed: 27 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@
10
10
11
11
With MailMason, you can use Grunt tasks, Handlebars, and SASS to streamline building a consistent set of transactional email templates using layouts and partials to reduce redundancy and create both the HTML and plain text versions of your transactional emails in one fell swoop.
12
12
13
-
By default, the generated templates use [Mustachio](https://github.com/wildbit/mustachio) for the variable placeholders so that you can easily use them as [Postmark](https://postmarkapp.com) templates. However, the Mustachio pieces are only placeholders, and the generated templates could easily be adapted to work with any email provider.
13
+
By default, the generated templates use [Mustachio](https://github.com/activecampaign/mustachio) for the variable placeholders so that you can easily use them as [Postmark](https://postmarkapp.com) templates. However, the Mustachio pieces are only placeholders, and the generated templates could easily be adapted to work with any email provider.
14
14
15
15
## What does it do for you?
16
16
@@ -27,35 +27,35 @@ By default, the generated templates use [Mustachio](https://github.com/wildbit/m
27
27
28
28
## Interested in contributing?
29
29
30
-
Read through our [guidelines for contributing](https://github.com/wildbit/mailmason/blob/template_updates/CONTRIBUTING.MD) to help make contributions quick and easy.
30
+
Read through our [guidelines for contributing](https://github.com/activecampaign/mailmason/blob/template_updates/CONTRIBUTING.MD) to help make contributions quick and easy.
31
31
32
32
## Visit the wiki for documentation and usage
33
33
34
-
If you need help getting started or using MailMason, make sure to check out the [MailMason wiki](https://github.com/wildbit/mailmason/wiki).
MailMason is licensed under the **MIT** license. Please refer to the [LICENSE](https://github.com/wildbit/mailmason/blob/master/LICENSE) for more information.
61
+
MailMason is licensed under the **MIT** license. Please refer to the [LICENSE](https://github.com/activecampaign/mailmason/blob/master/LICENSE) for more information.
Copy file name to clipboardExpand all lines: src/templates/example/content.hbs
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ preheader: "This is example text for the preheader set via the YAML front-matter
5
5
<hr>
6
6
<h1>Escaped Handlebars Brackets</h1>
7
7
8
-
<p>Working with templates, you'll occasionally need to put some <ahref="https://github.com/wildbit/mustachio">Mustachio</a> code in your Handlebars templates. To prevent the Handlebars processing from attempting to process your Mustachio code, you'll need to escape the curly braces by adding a backslash just before the opening curly braces.</p>
8
+
<p>Working with templates, you'll occasionally need to put some <ahref="https://github.com/activecampaign/mustachio">Mustachio</a> code in your Handlebars templates. To prevent the Handlebars processing from attempting to process your Mustachio code, you'll need to escape the curly braces by adding a backslash just before the opening curly braces.</p>
9
9
10
10
\{{ something }} will turn into \{{something}}<br><br>
0 commit comments