community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <ctubb...@apache.org>
Subject Re: GitHub Pages
Date Tue, 04 Aug 2015 17:29:21 GMT
+1

On Mon, Aug 3, 2015 at 10:12 PM, jay vyas <jayunit100.apache@gmail.com> wrote:
> agreed niclas that tools are secondary;   but deploying websites is just a
> hassle that steals cycles from that heroic group of folks who would rather
> be spending their time writing awesome docs  :)
>
> On Mon, Aug 3, 2015 at 9:30 PM, Niclas Hedhman <niclas@hedhman.org> wrote:
>
>> We (developers) always discuss tools for making documentation easier. But
>> we (developers) will always cite another hurdle (with tools) for not
>> contributing more to documentation. In a lot of cases, it doesn't matter
>> how easy the tools become, it is still the same heroic lot of people whoc
>> write the docs. Doesn't matter if that is HTML, xdoc. Anakia, docbook,
>> Maven text, Asciidoc, CMSes, Wiki, Jekyll or gh-pages. The unwilling will
>> always be able to raise a reason why he can't contribute...
>>
>> And as a rather active doc writer, I am happy when receiving contributions
>> in any form, such as email on mailing list, big or small, and I'll gladly
>> put that in myself. I'd probably be happy with an audio contribution as
>> well. It isn't the typing that is the hard part, it is coming up with the
>> accurate Content.
>>
>> My 2 cents to this never ending debate... ;-)
>>
>> Cheers
>> Niclas
>>
>> On Tue, Aug 4, 2015 at 12:23 AM, Christopher <ctubbsii@apache.org> wrote:
>>
>> > On Mon, Aug 3, 2015 at 11:51 AM, Owen O'Malley <omalley@apache.org>
>> wrote:
>> > > On Mon, Aug 3, 2015 at 8:22 AM, Stian Soiland-Reyes <stain@apache.org>
>> > > wrote:
>> > >
>> > >> This looks good.
>> > >>
>> > >> So do I understand any of the commiters editing the site would still
>> > >> need to run Jekyll manually and push (how?), or is there a GitHub like
>> > >> autobuild?
>> > >>
>> > >
>> > > It is manual, so it isn't as easy as github pages. However, I find that
>> > > generally I want to run jekyll locally first anyways to debug my
>> changes.
>> > >
>> >
>> > FWIW, GitHub pages is pretty easy to debug (non-local): push to
>> > gh-pages in a fork, before doing a PR against the gh-pages branch. If
>> > ASF ever did provide automated rendering, this is one reason I'd want
>> > it to be gh-pages compatible (because users who don't/can't have the
>> > build tools locally, can still make helpful contributions).
>> >
>>
>>
>>
>> --
>> Niclas Hedhman, Software Developer
>> http://zest.apache.org - New Energy for Java
>>
>
>
>
> --
> jay vyas

Mime
View raw message