[Erector-devel] Github Pages
brian.takita at gmail.com
Tue May 5 13:26:13 EDT 2009
On Sun, May 3, 2009 at 2:07 PM, Alex Chaffee <alex at pivotallabs.com> wrote:
> OK, I've reread http://pages.github.com and I'm sold. Free web page
> hosting; deploy via "git push". What's not to like?
> The only possible problem is where to keep the .rb files? In the main
> project (so they stay in sync with updates in the API) or in the site
> project (so they stay in sync with the generated pages)? Probably the
> latter, which might entail putting a copy of erector inside the site
> repo... possibly using braid.
Cool. Sorry, I havn't been reading my emails. (I'm a little better
than Sobo though).
I can take a look at making this happen. I'll make a branch. Should I
sign up Erector as a github user?
> Alex Chaffee - alex at stinky.com
> Stalk me: http://friendfeed.com/alexch | http://twitter.com/alexch |
> On Sun, Apr 19, 2009 at 1:41 PM, Brian Takita <brian.takita at gmail.com> wrote:
>> On Sat, Apr 18, 2009 at 3:00 PM, Alex Chaffee <alex at pivotallabs.com> wrote:
>>> Can we keep using the existing documentation page objects (which are
>>> written in Erector and output HTML)? There's some logic in there for
>>> generating the navigation and faq index and stuff.
>> I don't see why not. It would require that the generated files go into
>> the erector.github.com project.
>> Perhaps we can use submodules or a clone that we manage (like rails)
>> in the erector project?
>>> I see something about Jekyll at http://pages.github.com/ but I don't
>>> really understand it yet.
>> I think Jekyll is a template system that enables the generation of
>> html files (like what you already did for Erector).
>>> Alex Chaffee - alex at stinky.com
>>> Stalk me: http://friendfeed.com/alexch | http://twitter.com/alexch |
>>> On Sat, Apr 18, 2009 at 2:37 PM, Brian Takita <brian.takita at gmail.com> wrote:
>>>> I propose that we create an Erector github project and use Github
>>>> Pages (http://erector.github.com) instead of using Rubyforge.
>>>> Their usage of Git to update the site is pretty slick. It would also
>>>> be much easier to administer than Rubyforge.
>>>> Erector-devel mailing list
>>>> Erector-devel at rubyforge.org
More information about the Erector-devel