Move website to Eclipse Foundation Netlify

[JonasHelming]

As discussed in the Theia Dev meeting, it would probably make sense to move the website deployment to an official foundation netlify account so that a group of people has access. @brianking indicated that the EF could support this.
@JanKoehnlein : Would this be fine for you?
@chrisguindon : Is this possible?

[chrisguindon]

It would probably make sense to move the website deployment to an official foundation Netlify account so that a group of people has access

What kind of access problem are you trying to solve?

At the moment, we only use Netlify for our Working Group websites. Also, we only host the production instance if the website is not hosted under the eclipse.org domain.

For example, we use Netlify for jakarta.ee but not for iot.eclipse.org. iot.eclipse.org is hosted on Eclipse Infra.

We do this since we do not want sensitive information such as the Eclipse Session cookie to sent to Netlify servers if it's not needed.

Our current plan for Eclipse Projects website would be to move them to leverage Gitlab pages, however, we are still quite early on the project.

[brianking]

Given #133 (comment), is this fixed now or still needed?

[chrisguindon]

I recently created a boilerplate to help Eclipse project build a Hugo website on our infrastructure. Please check out the readme for some docs on how to use this: https://github.com/EclipseFdn/hugo-eclipsefdn-website-boilerplate

[spoenemann]

theia-ide.org is currently hosted on Netlify by TypeFox. It would be better to use something where more core committers / project leads have access to. I think it would be feasible to migrate to EF infrastructure, but I don't have the time to do such a migration at the moment.

@chrisguindon is it possible to move the Netlify site to the Eclipse org and give access to a handful of Theia committers?

[JonasHelming]

@chrisguindon : Is this possible?

[JonasHelming]

@brianking

[chrisguindon]

According to our records, we don't actually own that domain. We do own theia-ide.[com|net]. How is the site currently hosted?

My recommendation here would be to follow regular practices for a project website: which would be to use www.eclipse.org/theia and configure theia-ide.org as a redirect/alias. Also, instead of Netlify, the project would leverage their Jenkins instance to publish updates to www.eclipse.org/theia.

If we want to do something other than that, the working group needs to take the lead. We do configure WG websites with our Netlify account.

Does this help?

//cc @waynebeaton

[JonasHelming]

Yes, thank you, we will discuss this among the project leads

[spoenemann]

@JonasHelming WDYT of creating a new Netlify team for theia-ide.org and giving access to one representative from each involved organization?

Could the WG cover the monthly cost (~100$)? If that's too complicated, TypeFox or EclipseSource could take it?