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?

[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?

[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 

Deploy new Royale static site as-is?

[Josh Tynjala]

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