Re: Deploy new Royale static site as-is?

[Andrew Wetmore]

+1 I just have to  update the documentation and the Pelican tools will be
ready, but there is no reason not to take the updated site live right now.

a

On Mon, Jul 18, 2022 at 6:55 PM Josh Tynjala 
wrote:

> Hi all,
>
> I just created a new 11ty branch in the apache/royale-website repo, and I
> added the source files for the static site that I built with Eleventy.
>
> https://github.com/apache/royale-website/tree/11ty
>
> I made it so that Github Actions builds the site from source and deploys
> the output to the asf-staging branch. In the asf-staging branch, I added an
> .asf.yaml file, which currently deploys every new commit at the following
> staging URL:
>
> https://royale-11ty.staged.apache.org/
>
> It would be a relatively easy change to configure this repo to deploy to
> the production royale.apache.org website instead.
>
> I feel that it's better for Royale's future to have an updated website
> working sooner rather than later. I propose that we move forward with what
> we have now, instead of waiting any longer to migrate to Pelican. I have
> nothing against Pelican, and I'm totally okay with using it in the future.
> I simply think that it's better to replace the old website with
> **anything** that we can update properly, since the old website doesn't
> even mention the newest two Royale SDK releases.
>
> Does anyone object to moving forward with the Elventy-based site for now?
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>


-- 
Andrew Wetmore

Editor, Moose House Publications 
Editor-Writer, The Apache Software Foundation 

Re: Deploy new Royale static site as-is?

[Greg Dove]

Sorry Josh, Andrew,

I have not been able to give this (or many other topics) much attention
recently.

Josh: +1, definitely no objections, and thanks for your work on this.


On Tue, Jul 19, 2022 at 10:14 AM Andrew Wetmore  wrote:

> +1 I just have to  update the documentation and the Pelican tools will be
> ready, but there is no reason not to take the updated site live right now.
>
> a
>
> On Mon, Jul 18, 2022 at 6:55 PM Josh Tynjala 
> wrote:
>
> > Hi all,
> >
> > I just created a new 11ty branch in the apache/royale-website repo, and I
> > added the source files for the static site that I built with Eleventy.
> >
> > https://github.com/apache/royale-website/tree/11ty
> >
> > I made it so that Github Actions builds the site from source and deploys
> > the output to the asf-staging branch. In the asf-staging branch, I added
> an
> > .asf.yaml file, which currently deploys every new commit at the following
> > staging URL:
> >
> > https://royale-11ty.staged.apache.org/
> >
> > It would be a relatively easy change to configure this repo to deploy to
> > the production royale.apache.org website instead.
> >
> > I feel that it's better for Royale's future to have an updated website
> > working sooner rather than later. I propose that we move forward with
> what
> > we have now, instead of waiting any longer to migrate to Pelican. I have
> > nothing against Pelican, and I'm totally okay with using it in the
> future.
> > I simply think that it's better to replace the old website with
> > **anything** that we can update properly, since the old website doesn't
> > even mention the newest two Royale SDK releases.
> >
> > Does anyone object to moving forward with the Elventy-based site for now?
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
>
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications 
> Editor-Writer, The Apache Software Foundation 
>

RE: Deploy new Royale static site as-is?

[Yishay Weiss]

+1

From: Josh Tynjala
Sent: Tuesday, July 19, 2022 12:55 AM
To: Apache Royale Development
Subject: Deploy new Royale static site as-is?

Hi all,

I just created a new 11ty branch in the apache/royale-website repo, and I
added the source files for the static site that I built with Eleventy.

https://github.com/apache/royale-website/tree/11ty

I made it so that Github Actions builds the site from source and deploys
the output to the asf-staging branch. In the asf-staging branch, I added an
.asf.yaml file, which currently deploys every new commit at the following
staging URL:

https://royale-11ty.staged.apache.org/

It would be a relatively easy change to configure this repo to deploy to
the production royale.apache.org website instead.

I feel that it's better for Royale's future to have an updated website
working sooner rather than later. I propose that we move forward with what
we have now, instead of waiting any longer to migrate to Pelican. I have
nothing against Pelican, and I'm totally okay with using it in the future.
I simply think that it's better to replace the old website with
**anything** that we can update properly, since the old website doesn't
even mention the newest two Royale SDK releases.

Does anyone object to moving forward with the Elventy-based site for now?

--
Josh Tynjala
Bowler Hat LLC 

Re: Deploy new Royale static site as-is?

[Harbs]

+1 from me.

Thanks for getting this working!!!

Harbs

> On Jul 19, 2022, at 12:54 AM, Josh Tynjala  wrote:
> 
> Hi all,
> 
> I just created a new 11ty branch in the apache/royale-website repo, and I
> added the source files for the static site that I built with Eleventy.
> 
> https://github.com/apache/royale-website/tree/11ty
> 
> I made it so that Github Actions builds the site from source and deploys
> the output to the asf-staging branch. In the asf-staging branch, I added an
> .asf.yaml file, which currently deploys every new commit at the following
> staging URL:
> 
> https://royale-11ty.staged.apache.org/
> 
> It would be a relatively easy change to configure this repo to deploy to
> the production royale.apache.org website instead.
> 
> I feel that it's better for Royale's future to have an updated website
> working sooner rather than later. I propose that we move forward with what
> we have now, instead of waiting any longer to migrate to Pelican. I have
> nothing against Pelican, and I'm totally okay with using it in the future.
> I simply think that it's better to replace the old website with
> **anything** that we can update properly, since the old website doesn't
> even mention the newest two Royale SDK releases.
> 
> Does anyone object to moving forward with the Elventy-based site for now?
> 
> --
> Josh Tynjala
> Bowler Hat LLC 

RE: Deploy new Royale static site as-is?

[Maria Jose Esteve]

+1

Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 18 de julio de 2022 23:55
Para: Apache Royale Development 
Asunto: Deploy new Royale static site as-is?

Hi all,

I just created a new 11ty branch in the apache/royale-website repo, and I added 
the source files for the static site that I built with Eleventy.

https://github.com/apache/royale-website/tree/11ty

I made it so that Github Actions builds the site from source and deploys the 
output to the asf-staging branch. In the asf-staging branch, I added an 
.asf.yaml file, which currently deploys every new commit at the following 
staging URL:

https://royale-11ty.staged.apache.org/

It would be a relatively easy change to configure this repo to deploy to the 
production royale.apache.org website instead.

I feel that it's better for Royale's future to have an updated website working 
sooner rather than later. I propose that we move forward with what we have now, 
instead of waiting any longer to migrate to Pelican. I have nothing against 
Pelican, and I'm totally okay with using it in the future.
I simply think that it's better to replace the old website with
**anything** that we can update properly, since the old website doesn't even 
mention the newest two Royale SDK releases.

Does anyone object to moving forward with the Elventy-based site for now?

--
Josh Tynjala
Bowler Hat LLC 

Re: Deploy new Royale static site as-is?

[Andrew Wetmore]

The help docs for working with the Pelican website template are now up to
date. The main page is here [1].

The main changes are on the getting-started page [2] and the page about
building and testing locally [3]. For the latter, there is now a
downloadable tool that simplifies the local-build process.

[1] https://infra.apache.org/asf-pelican.html
[2] https://infra.apache.org/asf-pelican-gettingstarted.html
[3] https://infra.apache.org/asf-pelican-local.html

On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve  wrote:

> +1
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala 
> Enviado el: lunes, 18 de julio de 2022 23:55
> Para: Apache Royale Development 
> Asunto: Deploy new Royale static site as-is?
>
> Hi all,
>
> I just created a new 11ty branch in the apache/royale-website repo, and I
> added the source files for the static site that I built with Eleventy.
>
> https://github.com/apache/royale-website/tree/11ty
>
> I made it so that Github Actions builds the site from source and deploys
> the output to the asf-staging branch. In the asf-staging branch, I added an
> .asf.yaml file, which currently deploys every new commit at the following
> staging URL:
>
> https://royale-11ty.staged.apache.org/
>
> It would be a relatively easy change to configure this repo to deploy to
> the production royale.apache.org website instead.
>
> I feel that it's better for Royale's future to have an updated website
> working sooner rather than later. I propose that we move forward with what
> we have now, instead of waiting any longer to migrate to Pelican. I have
> nothing against Pelican, and I'm totally okay with using it in the future.
> I simply think that it's better to replace the old website with
> **anything** that we can update properly, since the old website doesn't
> even mention the newest two Royale SDK releases.
>
> Does anyone object to moving forward with the Elventy-based site for now?
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>


-- 
Andrew Wetmore

Editor, Moose House Publications 
Editor-Writer, The Apache Software Foundation 

Re: Deploy new Royale static site as-is?

[Andrew Wetmore]

If we now have a working process to maintain our website, can someone help
me update our documentation about it? This page [1] still gives guidance
for the WordPress site.

a

1. https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)

On Mon, Aug 1, 2022 at 1:35 PM Andrew Wetmore  wrote:

> The help docs for working with the Pelican website template are now up to
> date. The main page is here [1].
>
> The main changes are on the getting-started page [2] and the page about
> building and testing locally [3]. For the latter, there is now a
> downloadable tool that simplifies the local-build process.
>
> [1] https://infra.apache.org/asf-pelican.html
> [2] https://infra.apache.org/asf-pelican-gettingstarted.html
> [3] https://infra.apache.org/asf-pelican-local.html
>
> On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve 
> wrote:
>
>> +1
>>
>> Hiedra
>>
>> -Mensaje original-
>> De: Josh Tynjala 
>> Enviado el: lunes, 18 de julio de 2022 23:55
>> Para: Apache Royale Development 
>> Asunto: Deploy new Royale static site as-is?
>>
>> Hi all,
>>
>> I just created a new 11ty branch in the apache/royale-website repo, and I
>> added the source files for the static site that I built with Eleventy.
>>
>> https://github.com/apache/royale-website/tree/11ty
>>
>> I made it so that Github Actions builds the site from source and deploys
>> the output to the asf-staging branch. In the asf-staging branch, I added an
>> .asf.yaml file, which currently deploys every new commit at the following
>> staging URL:
>>
>> https://royale-11ty.staged.apache.org/
>>
>> It would be a relatively easy change to configure this repo to deploy to
>> the production royale.apache.org website instead.
>>
>> I feel that it's better for Royale's future to have an updated website
>> working sooner rather than later. I propose that we move forward with what
>> we have now, instead of waiting any longer to migrate to Pelican. I have
>> nothing against Pelican, and I'm totally okay with using it in the future.
>> I simply think that it's better to replace the old website with
>> **anything** that we can update properly, since the old website doesn't
>> even mention the newest two Royale SDK releases.
>>
>> Does anyone object to moving forward with the Elventy-based site for now?
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>>
>
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications 
> Editor-Writer, The Apache Software Foundation 
>
>
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications 
Editor-Writer, The Apache Software Foundation 

Re: Deploy new Royale static site as-is?

[Josh Tynjala]

The website is in this repo:

https://github.com/apache/royale-website

The readme gives the relevant npm commands to install required dependencies
and test locally (requires Node.js).

Just commit changes and push to the master branch, and it will deploy
automatically.

--
Josh Tynjala
Bowler Hat LLC 


On Tue, Aug 30, 2022 at 3:24 PM Andrew Wetmore  wrote:

> If we now have a working process to maintain our website, can someone help
> me update our documentation about it? This page [1] still gives guidance
> for the WordPress site.
>
> a
>
> 1. https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)
>
> On Mon, Aug 1, 2022 at 1:35 PM Andrew Wetmore  wrote:
>
> > The help docs for working with the Pelican website template are now up to
> > date. The main page is here [1].
> >
> > The main changes are on the getting-started page [2] and the page about
> > building and testing locally [3]. For the latter, there is now a
> > downloadable tool that simplifies the local-build process.
> >
> > [1] https://infra.apache.org/asf-pelican.html
> > [2] https://infra.apache.org/asf-pelican-gettingstarted.html
> > [3] https://infra.apache.org/asf-pelican-local.html
> >
> > On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve 
> > wrote:
> >
> >> +1
> >>
> >> Hiedra
> >>
> >> -Mensaje original-
> >> De: Josh Tynjala 
> >> Enviado el: lunes, 18 de julio de 2022 23:55
> >> Para: Apache Royale Development 
> >> Asunto: Deploy new Royale static site as-is?
> >>
> >> Hi all,
> >>
> >> I just created a new 11ty branch in the apache/royale-website repo, and
> I
> >> added the source files for the static site that I built with Eleventy.
> >>
> >> https://github.com/apache/royale-website/tree/11ty
> >>
> >> I made it so that Github Actions builds the site from source and deploys
> >> the output to the asf-staging branch. In the asf-staging branch, I
> added an
> >> .asf.yaml file, which currently deploys every new commit at the
> following
> >> staging URL:
> >>
> >> https://royale-11ty.staged.apache.org/
> >>
> >> It would be a relatively easy change to configure this repo to deploy to
> >> the production royale.apache.org website instead.
> >>
> >> I feel that it's better for Royale's future to have an updated website
> >> working sooner rather than later. I propose that we move forward with
> what
> >> we have now, instead of waiting any longer to migrate to Pelican. I have
> >> nothing against Pelican, and I'm totally okay with using it in the
> future.
> >> I simply think that it's better to replace the old website with
> >> **anything** that we can update properly, since the old website doesn't
> >> even mention the newest two Royale SDK releases.
> >>
> >> Does anyone object to moving forward with the Elventy-based site for
> now?
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC 
> >>
> >
> >
> > --
> > Andrew Wetmore
> >
> > Editor, Moose House Publications 
> > Editor-Writer, The Apache Software Foundation 
> >
> >
> >
> >
> >
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications 
> Editor-Writer, The Apache Software Foundation 
>

Re: Deploy new Royale static site as-is?

[Josh Tynjala]

FYI — I wrote the new documentation for updating the Royale website.
--
Josh Tynjala
Bowler Hat LLC 


On Tue, Aug 30, 2022 at 3:24 PM Andrew Wetmore  wrote:

> If we now have a working process to maintain our website, can someone help
> me update our documentation about it? This page [1] still gives guidance
> for the WordPress site.
>
> a
>
> 1. https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)
>
> On Mon, Aug 1, 2022 at 1:35 PM Andrew Wetmore  wrote:
>
> > The help docs for working with the Pelican website template are now up to
> > date. The main page is here [1].
> >
> > The main changes are on the getting-started page [2] and the page about
> > building and testing locally [3]. For the latter, there is now a
> > downloadable tool that simplifies the local-build process.
> >
> > [1] https://infra.apache.org/asf-pelican.html
> > [2] https://infra.apache.org/asf-pelican-gettingstarted.html
> > [3] https://infra.apache.org/asf-pelican-local.html
> >
> > On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve 
> > wrote:
> >
> >> +1
> >>
> >> Hiedra
> >>
> >> -Mensaje original-
> >> De: Josh Tynjala 
> >> Enviado el: lunes, 18 de julio de 2022 23:55
> >> Para: Apache Royale Development 
> >> Asunto: Deploy new Royale static site as-is?
> >>
> >> Hi all,
> >>
> >> I just created a new 11ty branch in the apache/royale-website repo, and
> I
> >> added the source files for the static site that I built with Eleventy.
> >>
> >> https://github.com/apache/royale-website/tree/11ty
> >>
> >> I made it so that Github Actions builds the site from source and deploys
> >> the output to the asf-staging branch. In the asf-staging branch, I
> added an
> >> .asf.yaml file, which currently deploys every new commit at the
> following
> >> staging URL:
> >>
> >> https://royale-11ty.staged.apache.org/
> >>
> >> It would be a relatively easy change to configure this repo to deploy to
> >> the production royale.apache.org website instead.
> >>
> >> I feel that it's better for Royale's future to have an updated website
> >> working sooner rather than later. I propose that we move forward with
> what
> >> we have now, instead of waiting any longer to migrate to Pelican. I have
> >> nothing against Pelican, and I'm totally okay with using it in the
> future.
> >> I simply think that it's better to replace the old website with
> >> **anything** that we can update properly, since the old website doesn't
> >> even mention the newest two Royale SDK releases.
> >>
> >> Does anyone object to moving forward with the Elventy-based site for
> now?
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC 
> >>
> >
> >
> > --
> > Andrew Wetmore
> >
> > Editor, Moose House Publications 
> > Editor-Writer, The Apache Software Foundation 
> >
> >
> >
> >
> >
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications 
> Editor-Writer, The Apache Software Foundation 
>

Re: Deploy new Royale static site as-is?

[Andrew Wetmore]

Ah, thank you. Is it in the page that had the information for the WordPress
site?

a

On Tue, Sep 27, 2022 at 7:02 PM Josh Tynjala 
wrote:

> FYI — I wrote the new documentation for updating the Royale website.
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Tue, Aug 30, 2022 at 3:24 PM Andrew Wetmore 
> wrote:
>
> > If we now have a working process to maintain our website, can someone
> help
> > me update our documentation about it? This page [1] still gives guidance
> > for the WordPress site.
> >
> > a
> >
> > 1. https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)
> >
> > On Mon, Aug 1, 2022 at 1:35 PM Andrew Wetmore 
> wrote:
> >
> > > The help docs for working with the Pelican website template are now up
> to
> > > date. The main page is here [1].
> > >
> > > The main changes are on the getting-started page [2] and the page about
> > > building and testing locally [3]. For the latter, there is now a
> > > downloadable tool that simplifies the local-build process.
> > >
> > > [1] https://infra.apache.org/asf-pelican.html
> > > [2] https://infra.apache.org/asf-pelican-gettingstarted.html
> > > [3] https://infra.apache.org/asf-pelican-local.html
> > >
> > > On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve 
> > > wrote:
> > >
> > >> +1
> > >>
> > >> Hiedra
> > >>
> > >> -Mensaje original-
> > >> De: Josh Tynjala 
> > >> Enviado el: lunes, 18 de julio de 2022 23:55
> > >> Para: Apache Royale Development 
> > >> Asunto: Deploy new Royale static site as-is?
> > >>
> > >> Hi all,
> > >>
> > >> I just created a new 11ty branch in the apache/royale-website repo,
> and
> > I
> > >> added the source files for the static site that I built with Eleventy.
> > >>
> > >> https://github.com/apache/royale-website/tree/11ty
> > >>
> > >> I made it so that Github Actions builds the site from source and
> deploys
> > >> the output to the asf-staging branch. In the asf-staging branch, I
> > added an
> > >> .asf.yaml file, which currently deploys every new commit at the
> > following
> > >> staging URL:
> > >>
> > >> https://royale-11ty.staged.apache.org/
> > >>
> > >> It would be a relatively easy change to configure this repo to deploy
> to
> > >> the production royale.apache.org website instead.
> > >>
> > >> I feel that it's better for Royale's future to have an updated website
> > >> working sooner rather than later. I propose that we move forward with
> > what
> > >> we have now, instead of waiting any longer to migrate to Pelican. I
> have
> > >> nothing against Pelican, and I'm totally okay with using it in the
> > future.
> > >> I simply think that it's better to replace the old website with
> > >> **anything** that we can update properly, since the old website
> doesn't
> > >> even mention the newest two Royale SDK releases.
> > >>
> > >> Does anyone object to moving forward with the Elventy-based site for
> > now?
> > >>
> > >> --
> > >> Josh Tynjala
> > >> Bowler Hat LLC 
> > >>
> > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > Editor, Moose House Publications 
> > > Editor-Writer, The Apache Software Foundation 
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Andrew Wetmore
> >
> > Editor, Moose House Publications 
> > Editor-Writer, The Apache Software Foundation 
> >
>


-- 
Andrew Wetmore

Editor, Moose House Publications 
Editor-Writer, The Apache Software Foundation 

Re: Deploy new Royale static site as-is?

[Josh Tynjala]

Yeah, same URL as before. Just new instructions to replace the old
WordPress stuff.

https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)

--
Josh Tynjala
Bowler Hat LLC 


On Tue, Sep 27, 2022 at 3:06 PM Andrew Wetmore  wrote:

> Ah, thank you. Is it in the page that had the information for the WordPress
> site?
>
> a
>
> On Tue, Sep 27, 2022 at 7:02 PM Josh Tynjala 
> wrote:
>
> > FYI — I wrote the new documentation for updating the Royale website.
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Tue, Aug 30, 2022 at 3:24 PM Andrew Wetmore 
> > wrote:
> >
> > > If we now have a working process to maintain our website, can someone
> > help
> > > me update our documentation about it? This page [1] still gives
> guidance
> > > for the WordPress site.
> > >
> > > a
> > >
> > > 1.
> https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)
> > >
> > > On Mon, Aug 1, 2022 at 1:35 PM Andrew Wetmore 
> > wrote:
> > >
> > > > The help docs for working with the Pelican website template are now
> up
> > to
> > > > date. The main page is here [1].
> > > >
> > > > The main changes are on the getting-started page [2] and the page
> about
> > > > building and testing locally [3]. For the latter, there is now a
> > > > downloadable tool that simplifies the local-build process.
> > > >
> > > > [1] https://infra.apache.org/asf-pelican.html
> > > > [2] https://infra.apache.org/asf-pelican-gettingstarted.html
> > > > [3] https://infra.apache.org/asf-pelican-local.html
> > > >
> > > > On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve  >
> > > > wrote:
> > > >
> > > >> +1
> > > >>
> > > >> Hiedra
> > > >>
> > > >> -Mensaje original-
> > > >> De: Josh Tynjala 
> > > >> Enviado el: lunes, 18 de julio de 2022 23:55
> > > >> Para: Apache Royale Development 
> > > >> Asunto: Deploy new Royale static site as-is?
> > > >>
> > > >> Hi all,
> > > >>
> > > >> I just created a new 11ty branch in the apache/royale-website repo,
> > and
> > > I
> > > >> added the source files for the static site that I built with
> Eleventy.
> > > >>
> > > >> https://github.com/apache/royale-website/tree/11ty
> > > >>
> > > >> I made it so that Github Actions builds the site from source and
> > deploys
> > > >> the output to the asf-staging branch. In the asf-staging branch, I
> > > added an
> > > >> .asf.yaml file, which currently deploys every new commit at the
> > > following
> > > >> staging URL:
> > > >>
> > > >> https://royale-11ty.staged.apache.org/
> > > >>
> > > >> It would be a relatively easy change to configure this repo to
> deploy
> > to
> > > >> the production royale.apache.org website instead.
> > > >>
> > > >> I feel that it's better for Royale's future to have an updated
> website
> > > >> working sooner rather than later. I propose that we move forward
> with
> > > what
> > > >> we have now, instead of waiting any longer to migrate to Pelican. I
> > have
> > > >> nothing against Pelican, and I'm totally okay with using it in the
> > > future.
> > > >> I simply think that it's better to replace the old website with
> > > >> **anything** that we can update properly, since the old website
> > doesn't
> > > >> even mention the newest two Royale SDK releases.
> > > >>
> > > >> Does anyone object to moving forward with the Elventy-based site for
> > > now?
> > > >>
> > > >> --
> > > >> Josh Tynjala
> > > >> Bowler Hat LLC 
> > > >>
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > >
> > > > Editor, Moose House Publications 
> > > > Editor-Writer, The Apache Software Foundation 
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > Editor, Moose House Publications 
> > > Editor-Writer, The Apache Software Foundation 
> > >
> >
>
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications 
> Editor-Writer, The Apache Software Foundation 
>