You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@datasketches.apache.org by leerho <le...@gmail.com> on 2019/12/03 18:20:01 UTC

Website content moved.

Folks,

The generated html content of datasketches.github.io has been pushed to
incubator-datasketches-website
<http://github.com/apache/incubator-datasketches-website/tree/asf-site> and
is now visible to the public from datasketches.apache.org.

We still have the task of transferring the markdown and figuring out how to
automatically do the rendering.

Thanks to Joonsuk for this!

Lee.

Re: Website content moved.

Posted by leerho <le...@gmail.com>.
Yes, that is our plan.

Thank you!

Lee.

On Mon, Dec 9, 2019 at 2:17 AM Christopher <ct...@apache.org> wrote:

> I would think the first step is to move the existing jekyll/markdown
> over to ASF, and then worry about switching to another site generator
> as subsequent work.
>
> On Wed, Dec 4, 2019 at 2:08 PM Kenneth Knowles <ke...@apache.org> wrote:
> >
> > Beam uses Jekyll but actually I understand from tech writers that Hugo
> is much better for i18n in addition to being easier to use generally. We
> have lost quite a few potential contributions due to the pain of the Ruby +
> Jekyll ecosystem. Also dramatically faster to the extent that matters.
> >
> > Kenn
> >
> > On Wed, Dec 4, 2019 at 2:50 AM Christopher <ct...@apache.org> wrote:
> >>
> >> Apache Accumulo does something very similar. We build our `asf-site`
> >> branch from Jekyll-based site contents (mostly markdown) in our
> >> `master` branch in the repo. Although we've drifted away from
> >> GitHub-only features, we still use Jekyll to build our site. We have a
> >> script (
> https://github.com/apache/accumulo-website/blob/c29c50cdd/_devtools/git-hooks/post-commit
> )
> >> that does most of the work for us, but we tend to run that script
> >> manually (and locally) whenever we merge a PR to the master branch, or
> >> make any other commits to the master branch. (The script basically
> >> does `bundle exec jekyll build` with some additional `git` magic to
> >> create a commit on the `asf-site` branch containing the generated
> >> site, ready to `git push`.)
> >>
> >> If DataSketches does something like this, then all you really need to
> >> do is transfer the master branch from the old datasketches.github.io
> >> repo to the new incubator-datasketches-website repo (history and all,
> >> is okay), and then use a script similar to Accumulo's to generate and
> >> update the `asf-site` branch, based on the master branch, on-demand.
> >> Jenkins might be able to be configured to do it, or you might be able
> >> to work with INFRA to set up a post-receive hook on the server-side so
> >> it automatically gets regenerated when you push to the master branch
> >> where your markdown is, although they should probably disable Jekyll
> >> plugins with `--safe` if they run it on the server side (which is
> >> basically what GitHub does).
> >>
> >> On Tue, Dec 3, 2019 at 1:20 PM leerho <le...@gmail.com> wrote:
> >> >
> >> > Folks,
> >> >
> >> > The generated html content of datasketches.github.io has been pushed
> to incubator-datasketches-website and is now visible to the public from
> datasketches.apache.org.
> >> >
> >> > We still have the task of transferring the markdown and figuring out
> how to automatically do the rendering.
> >> >
> >> > Thanks to Joonsuk for this!
> >> >
> >> > Lee.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
> >> For additional commands, e-mail: dev-help@datasketches.apache.org
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
> For additional commands, e-mail: dev-help@datasketches.apache.org
>
>

Re: Website content moved.

Posted by Christopher <ct...@apache.org>.
I would think the first step is to move the existing jekyll/markdown
over to ASF, and then worry about switching to another site generator
as subsequent work.

On Wed, Dec 4, 2019 at 2:08 PM Kenneth Knowles <ke...@apache.org> wrote:
>
> Beam uses Jekyll but actually I understand from tech writers that Hugo is much better for i18n in addition to being easier to use generally. We have lost quite a few potential contributions due to the pain of the Ruby + Jekyll ecosystem. Also dramatically faster to the extent that matters.
>
> Kenn
>
> On Wed, Dec 4, 2019 at 2:50 AM Christopher <ct...@apache.org> wrote:
>>
>> Apache Accumulo does something very similar. We build our `asf-site`
>> branch from Jekyll-based site contents (mostly markdown) in our
>> `master` branch in the repo. Although we've drifted away from
>> GitHub-only features, we still use Jekyll to build our site. We have a
>> script (https://github.com/apache/accumulo-website/blob/c29c50cdd/_devtools/git-hooks/post-commit)
>> that does most of the work for us, but we tend to run that script
>> manually (and locally) whenever we merge a PR to the master branch, or
>> make any other commits to the master branch. (The script basically
>> does `bundle exec jekyll build` with some additional `git` magic to
>> create a commit on the `asf-site` branch containing the generated
>> site, ready to `git push`.)
>>
>> If DataSketches does something like this, then all you really need to
>> do is transfer the master branch from the old datasketches.github.io
>> repo to the new incubator-datasketches-website repo (history and all,
>> is okay), and then use a script similar to Accumulo's to generate and
>> update the `asf-site` branch, based on the master branch, on-demand.
>> Jenkins might be able to be configured to do it, or you might be able
>> to work with INFRA to set up a post-receive hook on the server-side so
>> it automatically gets regenerated when you push to the master branch
>> where your markdown is, although they should probably disable Jekyll
>> plugins with `--safe` if they run it on the server side (which is
>> basically what GitHub does).
>>
>> On Tue, Dec 3, 2019 at 1:20 PM leerho <le...@gmail.com> wrote:
>> >
>> > Folks,
>> >
>> > The generated html content of datasketches.github.io has been pushed to incubator-datasketches-website and is now visible to the public from datasketches.apache.org.
>> >
>> > We still have the task of transferring the markdown and figuring out how to automatically do the rendering.
>> >
>> > Thanks to Joonsuk for this!
>> >
>> > Lee.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
>> For additional commands, e-mail: dev-help@datasketches.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
For additional commands, e-mail: dev-help@datasketches.apache.org


Re: Website content moved.

Posted by Kenneth Knowles <ke...@apache.org>.
Beam uses Jekyll but actually I understand from tech writers that Hugo is
much better for i18n in addition to being easier to use generally. We have
lost quite a few potential contributions due to the pain of the Ruby +
Jekyll ecosystem. Also dramatically faster to the extent that matters.

Kenn

On Wed, Dec 4, 2019 at 2:50 AM Christopher <ct...@apache.org> wrote:

> Apache Accumulo does something very similar. We build our `asf-site`
> branch from Jekyll-based site contents (mostly markdown) in our
> `master` branch in the repo. Although we've drifted away from
> GitHub-only features, we still use Jekyll to build our site. We have a
> script (
> https://github.com/apache/accumulo-website/blob/c29c50cdd/_devtools/git-hooks/post-commit
> )
> that does most of the work for us, but we tend to run that script
> manually (and locally) whenever we merge a PR to the master branch, or
> make any other commits to the master branch. (The script basically
> does `bundle exec jekyll build` with some additional `git` magic to
> create a commit on the `asf-site` branch containing the generated
> site, ready to `git push`.)
>
> If DataSketches does something like this, then all you really need to
> do is transfer the master branch from the old datasketches.github.io
> repo to the new incubator-datasketches-website repo (history and all,
> is okay), and then use a script similar to Accumulo's to generate and
> update the `asf-site` branch, based on the master branch, on-demand.
> Jenkins might be able to be configured to do it, or you might be able
> to work with INFRA to set up a post-receive hook on the server-side so
> it automatically gets regenerated when you push to the master branch
> where your markdown is, although they should probably disable Jekyll
> plugins with `--safe` if they run it on the server side (which is
> basically what GitHub does).
>
> On Tue, Dec 3, 2019 at 1:20 PM leerho <le...@gmail.com> wrote:
> >
> > Folks,
> >
> > The generated html content of datasketches.github.io has been pushed to
> incubator-datasketches-website and is now visible to the public from
> datasketches.apache.org.
> >
> > We still have the task of transferring the markdown and figuring out how
> to automatically do the rendering.
> >
> > Thanks to Joonsuk for this!
> >
> > Lee.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
> For additional commands, e-mail: dev-help@datasketches.apache.org
>
>

Re: Website content moved.

Posted by Christopher <ct...@apache.org>.
Apache Accumulo does something very similar. We build our `asf-site`
branch from Jekyll-based site contents (mostly markdown) in our
`master` branch in the repo. Although we've drifted away from
GitHub-only features, we still use Jekyll to build our site. We have a
script (https://github.com/apache/accumulo-website/blob/c29c50cdd/_devtools/git-hooks/post-commit)
that does most of the work for us, but we tend to run that script
manually (and locally) whenever we merge a PR to the master branch, or
make any other commits to the master branch. (The script basically
does `bundle exec jekyll build` with some additional `git` magic to
create a commit on the `asf-site` branch containing the generated
site, ready to `git push`.)

If DataSketches does something like this, then all you really need to
do is transfer the master branch from the old datasketches.github.io
repo to the new incubator-datasketches-website repo (history and all,
is okay), and then use a script similar to Accumulo's to generate and
update the `asf-site` branch, based on the master branch, on-demand.
Jenkins might be able to be configured to do it, or you might be able
to work with INFRA to set up a post-receive hook on the server-side so
it automatically gets regenerated when you push to the master branch
where your markdown is, although they should probably disable Jekyll
plugins with `--safe` if they run it on the server side (which is
basically what GitHub does).

On Tue, Dec 3, 2019 at 1:20 PM leerho <le...@gmail.com> wrote:
>
> Folks,
>
> The generated html content of datasketches.github.io has been pushed to incubator-datasketches-website and is now visible to the public from datasketches.apache.org.
>
> We still have the task of transferring the markdown and figuring out how to automatically do the rendering.
>
> Thanks to Joonsuk for this!
>
> Lee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@datasketches.apache.org
For additional commands, e-mail: dev-help@datasketches.apache.org