Skip to content

Migrate EF websites to our new preview framework

Most of our websites are currently using Netlify to enable developers to review a preview of their changes each time they submit an MR. However, over the years, the cost of using Netlify has increased significantly.

In an effort to reduce our costs, @mbarbero and his team created a new preview framework that we can use that run on the Eclipse Infrastructure.

We've been using this new service on a few sites, such as eclipse.org, in order to test the service and I am happy to report that it meets all our requirements and it's pretty stable.

Here's an example of a PR using our new framework (eclipse.org): eclipsefdn/it/websites/eclipse.org!25

Here's an example of a PR with Netlify: eclipsefdn/it/websites/sparkplug.eclipse.org!126

With that said, we are now ready to migrate more sites to this new service.

Please note that I will focus on sites that I easily swap to our new framework without too much work. This means that larger sites such as all the Adoptium, Jakarta and AsciiDoc sites won't be migrated with this issue. These sites will require a separate conversation with each of these WG to see if they are interested in switching.

My goal is to transition to our new framework without any impact on our contributors for these sites. I will publish a full list shortly.

There will be 2 phases for this project.

Phase 1: We will migrate all the websites hosted as an eclipse.org subdomain:

Phase 2: These are custom webdev projects with custom requirements. We will deal with these separately.

Phase 3: We will finalize the transition with sites with domains currently managed by Netlify. We need to move them to Rodgers via #1979 (closed) before we take this on.

Note: I will not create separate issues for sites under Phase 1 since I expect the migration to be fairly straightforward.

I will need to create issues on some sites under phases 2-3 to discuss certain details. For example, I would like to consider merging eclipse.org/research with eclipse.org but I need to discuss this change with them first.

//cc @droy

Edited by Christopher Guindon