Merge pull request #245 from justwriteclick/ag-rm-mailer

Removes signup insertion

Author: annegentle

_layouts/learn.html

@@ -21,8 +21,6 @@ <h1>{{ page.title }}</h1>
        </div>
        {{ content }}
 
-       {% include sign-up.html %}
-
        </div>
      </div>
     {% include footer.html %}

_posts/articles/2016-09-17-github-for-docs.md

@@ -53,5 +53,3 @@ I hope I'm talking to people who care a lot about words. Let's start with some v
 These definitions can give you decision points to make about information architecture, so think about which deliverables you'll make, who should review and collaborate on those deliverables, and how you can automate publishing with the chunks of a repository or an organization as overarching collections.
 
 Take a look at [this article's source on GitHub](https://raw.githubusercontent.com/justwriteclick/docslikecode/master/_posts/articles/2016-09-17-github-for-docs.md) to get a sense of the "source" for a document. We'll look at the source aspects in a future article. To stay in touch, subscribe to get relevant emails in your inbox.
-
-{% include sign-up.html %}

_posts/articles/2016-09-18-github-collaborators.md

@@ -32,5 +32,3 @@ When you write with people beyond your immediate team, ensure that those contrib
 Harnessing these needs being met is not about gaining free labor. Contributors should be highly, highly valued, and rewarded. It's about creating opportunities to shine, and curating jobs. Because contributor graphs are available on GitHub, and because the contribution data can be mined to see that reputation being built one pull request at a time, GitHub gives rewards in a new way.
 
 If you think this all sounds nice but impractical, I encourage you to sign up for the newsletter to learn how to practice these techniques like you would a musical instrument. You need hands-on experience and time to play to get better and better.
-
-{% include sign-up.html %}

_posts/articles/2016-09-23-doc-issues-tracking.md

@@ -40,5 +40,3 @@ To take it a step further, you can also add a link to edit the source doc file i
 In traditional enterprise doc systems, writers can go weeks without getting reviews or input. Even when asking and nagging multiple times, sometimes the documentation systems are so separate from code systems that technical reviews are through email. GASP. Put those days behind you and go where the technically knowledgeable people are.
 
 Working with the same collaboration tools as technical people gives better reviews. We can merge as many as 50 patches per day, though, in reality, it's about a dozen a day. We are running up to four automated doc tests per patch and requiring two humans to check the patch and click to publish. Each reviewer who can publish must adhere to our review rules, and people follow the rules well.
-
-{% include sign-up.html %}

_posts/articles/2016-09-24-what-docs-like-code-looks-like.md

@@ -29,5 +29,3 @@ This video shows you how to clone a GitHub repo with an existing Jekyll theme an
 ### How it's made
 
 <iframe width="560" height="315" src="https://www.youtube.com/embed/{{ include.id }}" frameborder="0" allowfullscreen></iframe>
-
-{% include sign-up.html %}

_posts/articles/2016-11-26-remodel-your-docs.md

@@ -43,5 +43,3 @@ Here are some resources to get your first punch in that punch list:
 * Using Python Sphinx? The OpenStack docs theme has some Javascript you could re-use to pre-populate an Issue template so the reporter sends the page URL, the source URL, the git SHA of the commit for that version of the page, and the release version value. See this [docs.js snippet](https://github.com/openstack/openstackdocstheme/blob/master/openstackdocstheme/theme/openstackdocs/static/js/docs.js#L119).
 * Using a private repo for docs, but want to track bugs publicly? Use [Issues-only Access Permissions](https://help.github.com/articles/issues-only-access-permissions/).
 * Want to add a bit of code to pre-create Issues to use as comments on every page? Free yourself from Disqus comments. Try this [set of tips and sample code in a blog post](https://zpbappi.com/jekyll-with-tags-archive-and-comments-in-github-pages/).
-
-{% include sign-up.html %}

_posts/articles/2016-12-29-coming-soon-writing-docs-like-code.md

@@ -28,5 +28,3 @@ Here are some of the topics:
 * What about wikis?
 
 When you treat docs as code, what are your biggest barriers? Your looming concerns? Let me know so we can address these. Sign up below to learn more together.
-
-{% include sign-up.html %}

_posts/articles/2017-03-18-pantheon-case-study.md

@@ -66,5 +66,3 @@ As of March 2017, this workflow was not available to forks for security reasons.
 #### Are there any questions you wish you had asked before using GitHub for docs?
 
 How do the needs of open source software projects differ from those of a documentation project? Where does GitHub fail to fulfill the needs of documentation projects and how can those gaps be filled?
-
-{% include sign-up.html %}

_posts/articles/2017-03-25-symantec-case-study.md

@@ -127,5 +127,3 @@ The biggest thing we didn't do was integrate the Javadoc build completely into t
 On the other hand, because other doc components besides the Javadoc could only be built manually, more automation could have solved only part of the problem of keeping content up-to-date on the server. Ultimately, the decision not to automate the Javadoc made sense — there are always pain points on either side of a decision like this.
 
 We also didn't realize initially that we'd have to coordinate our doxygen build, which ran over only a small subset of the code, with multiple other doxygen builds over other parts of the code tree. I wound up working with lead devs on other coding projects to coordinate main page markup and config values so that we could all get the doc builds that we needed. This work was a bit fiddly, and produced an extra round of review with every Javadoc build to make sure that the right components were all properly included.
-
-{% include sign-up.html %}

_posts/articles/2017-04-04-balsamiq-case-study-part-1.md

@@ -94,5 +94,3 @@ Hugo looks for two pieces of front matter. The first is the presence of a parame
 If the `include` parameter isn't present, Hugo just uses the Markdown content in the file without copying content from elsewhere. This allows us to mix and match docs that are unique to one product with docs that share functionality with multiple products.
 
 It took some effort to get it set up, but now we don't even think about it. It's really easy for the content writers, and we'll be able to extend it when we add yet more versions in the future (we already are, in fact).
-
-{% include sign-up.html %}