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 wrote:
> We (developers) always discuss tools for m
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
It's overstating it to say it's almost all automated. But there are some small
and important steps towards this. We are, I believe, at the point that the
WebApp I've been building is more functional than the script Rich originally
wrote. But there is still work to do before it's all automated. F
On Mon, Aug 3, 2015 at 11:51 AM, Owen O'Malley wrote:
> On Mon, Aug 3, 2015 at 8:22 AM, Stian Soiland-Reyes
> 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
>> autobu
On Mon, Aug 3, 2015 at 8:22 AM, Stian Soiland-Reyes
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. Howeve
Git can be used instead of SVN. CMS is not required.
Drill has comprehensive docs on how to push their web-site:
https://github.com/apache/drill/tree/gh-pages-master
On Mon, Aug 3, 2015 at 8:38 AM, Jay Vyas
wrote:
> Yeah, same question... Svn pushing or CMS still required? According to
> th
Yeah, same question... Svn pushing or CMS still required? According to the
snippet below the svn part is no longer needed? But maybe I'm
misinterpreting ...?
> On Aug 3, 2015, at 11:22 AM, Stian Soiland-Reyes wrote:
>
> This looks good.
>
> So do I understand any of the commiters editing
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?
Is Jekyll still requiring various Ruby libraries to be installed in a
carefully selected version (with fun time on Windows for na
On Wed, Mar 4, 2015 at 11:56 PM, Ted Dunning wrote:
> Several projects are using Jekyll to emulate the github style site
> processing. As an example: http://drill.apache.org/
>
> THis is still a bit inconvenient in that the gh-pages branch has to be
> built using jekyll and then checked into SVN
Anything rendering markdown is GH compatible imo. Sorry to bump this
zombie thread but just curious if anyone has thought more about this, its
really easy to edit markdown and push it - it would improve the docs of ALL
apache projects if we were able to just maintain docs without having to
push co
The following are the meetups I'm aware of in the coming week where
Apache enthusiasts are likely to be present. If you know
of others, please let me know, and/or add them to
http://apache.org/events
If there's a meetup in your area, please consider attending. If you
attend, please consider takin
On 07/23/2015 12:25 PM, missywarnkin wrote:
Rich, teach me how to do this, and I can start doing it if you'd like.
~M
Ross has been working on this tool to make it more user friendly, and I
believe he's got it at a place where we can hand it off to someone. I
haven't yet had a chance to l
12 matches
Mail list logo
