Skip to content
Browse files

Update publishing guide

  • Loading branch information...
1 parent 8360769 commit cd2cdbe23f3eaa6f4afa5db2a348667a51a90b02 @rwdaigle rwdaigle committed May 27, 2011
Showing with 38 additions and 3 deletions.
  1. +1 −1 site/atom.xml
  2. +1 −1 site/publish.html
  3. +36 −1 source/publish.haml
View
2 site/atom.xml
@@ -3,7 +3,7 @@
<title>Edge Rails.info</title>
<link href="http://edgerails.info/atom.xml" rel="self" />
<link href="http://edgerails.info" />
- <updated>2011-05-27T19:48:36-04:00</updated>
+ <updated>2011-05-27T20:24:53-04:00</updated>
<id>http://edgerails.info</id>
<entry>
<title>Reversible Migrations</title>
View
2 site/publish.html
@@ -94,7 +94,7 @@
<div class='page_width'>
<div id='main'>
<div class='contents'>
- <!-- use the :mardown filter if you want to write pages with Markdown -->&#x000A;<h3>Publishing Guide</h3>&#x000A;&#x000A;<p>We&#8217;re still refining our process&#8230; stay tuned for details!</p>
+ <!-- use the :mardown filter if you want to write pages with Markdown -->&#x000A;<h3>Publishing Guide</h3>&#x000A;&#x000A;<p>EdgeRails.info runs on Jekyll, the static site generator, to facilitate the easy forking, sharing and updating of articles&#x000A;via GitHub, every programmer&#8217;s favorite collaboration tool. We welcome your article contributions and have collected&#x000A;the following set of resources to help you get started.</p>&#x000A;&#x000A;<h4>Contribution Howto</h4>&#x000A;&#x000A;<p>If you have an idea for an article about a new feature in Rails (or have chosen one suggested by us/others)&#x000A;then here&#8217;s what I&#8217;d like to suggest:</p>&#x000A;&#x000A;<ul>&#x000A;<li>Contact me at ryan [dot] daigle [at] gmail [dot] com letting me know what topic you plan to write about (to&#x000A;ensure somebody else hasn&#8217;t already started on that topic).</li>&#x000A;<li>Once it&#8217;s clear you&#8217;re not duplicating somebody else&#8217;s efforts, follow the <a href="https://github.com/rwdaigle/edgerails/blob/master/README.textile">README</a>&#x000A;to checkout the site source and write the article.</li>&#x000A;<li>Once you&#8217;ve written the article and have regenerated the site, checkin your work and send me a <a href="http://help.github.com/pull-requests/">pull request on GitHub</a>.&#x000A;I&#8217;ll take a quick read and, if all looks good, will merge your work into the official branch and push the changes up to the site. And that&#8217;s it!</li>&#x000A;</ul>&#x000A;&#x000A;&#x000A;<p>This is meant to be a very easy and lightweight process. If it&#8217;s not, I need to hear from you!</p>&#x000A;&#x000A;<h4>Wanted Topics</h4>&#x000A;&#x000A;<p>Sometimes the hardest part in contributing is coming up with the topic. See below for a list known topics (and tasks) we&#8217;d love to&#x000A;have covered on the site (but please check w/ me before starting so we don&#8217;t have two people working on the same thing&#x000A;at once - see bullet #1 above):</p>&#x000A;&#x000A;<ul>&#x000A;<li>Mountable engines in Rails 3</li>&#x000A;<li>Rails 3.1 asset pipeline</li>&#x000A;<li>Bulk alter table</li>&#x000A;<li>Subdomain and tld routing support</li>&#x000A;<li>has_secure_password</li>&#x000A;<li>Making the site regeneration more efficient (it currently takes so long as Jekyll regenerates all files)</li>&#x000A;</ul>&#x000A;&#x000A;&#x000A;<p>As even this page is part of the site source, feel free to add your own suggestions to this list as well. Contributions are&#x000A;welcome to all aspects of the site.</p>&#x000A;&#x000A;<ul>&#x000A;<li>Ryan Daigle</li>&#x000A;</ul>
</div>
</div>
<div id='sidebar'>
View
37 source/publish.haml
@@ -7,4 +7,39 @@ nav: publish
:markdown
### Publishing Guide
- We're still refining our process... stay tuned for details!
+ EdgeRails.info runs on Jekyll, the static site generator, to facilitate the easy forking, sharing and updating of articles
+ via GitHub, every programmer's favorite collaboration tool. We welcome your article contributions and have collected
+ the following set of resources to help you get started.
+
+ #### Contribution Howto
+
+ If you have an idea for an article about a new feature in Rails (or have chosen one suggested by us/others)
+ then here's what I'd like to suggest:
+
+ - Contact me at ryan [dot] daigle [at] gmail [dot] com letting me know what topic you plan to write about (to
+ ensure somebody else hasn't already started on that topic).
+ - Once it's clear you're not duplicating somebody else's efforts, follow the [README](https://github.com/rwdaigle/edgerails/blob/master/README.textile)
+ to checkout the site source and write the article.
+ - Once you've written the article and have regenerated the site, checkin your work and send me a [pull request on GitHub](http://help.github.com/pull-requests/).
+ I'll take a quick read and, if all looks good, will merge your work into the official branch and push the changes up to the site. And that's it!
+
+ This is meant to be a very easy and lightweight process. If it's not, I need to hear from you!
+
+
+ #### Wanted Topics
+
+ Sometimes the hardest part in contributing is coming up with the topic. See below for a list known topics (and tasks) we'd love to
+ have covered on the site (but please check w/ me before starting so we don't have two people working on the same thing
+ at once - see bullet #1 above):
+
+ * Mountable engines in Rails 3
+ * Rails 3.1 asset pipeline
+ * Bulk alter table
+ * Subdomain and tld routing support
+ * has_secure_password
+ * Making the site regeneration more efficient (it currently takes so long as Jekyll regenerates all files)
+
+ As even this page is part of the site source, feel free to add your own suggestions to this list as well. Contributions are
+ welcome to all aspects of the site.
+
+ - Ryan Daigle

0 comments on commit cd2cdbe

Please sign in to comment.
Something went wrong with that request. Please try again.