Merge eclipse.org-research with eclipse.org

The eclipse.org-research website in hugo was done before we migrated eclipse.org to hugo.

Now that are live with eclipse.org hugo, I would like to recommend that we merge both projects for the following reason:

1. Maintenance: Easier for us to maintain 1 project versus 2
2. SEO: Since the eclipse.org hugo website is at the root of eclipse.org, that site serves a sitemap.xml that googles uses to index our website. If we migrate eclipse.org-research with eclipse.org, all the pages from our research website will be included in our sitemap: https://www.eclipse.org/sitemap.xml

Note that only the page migrated to hugo appears in that sitemap so far. This will grow overtime.

@pkriefrvi Do you have any concerns with doing this? Let me know if you have questions, I am more than happy to jump on a call with you to discuss this furter.

assigned to @cguindon

marked this issue as related to eclipsefdn/helpdesk#1978 (closed)

mentioned in issue eclipsefdn/helpdesk#1978 (closed)

This issue is motivated by the work we want to do for migrating to our new preview framework: eclipsefdn/helpdesk#1978 (closed)

For eclipse.org-research, I was thinking of solving this issue by migrating the project to our eclipse.org project.

assigned to @cguindon

added statetodo team:webdev labels

added prioritymedium severitynormal labels

added MBO label

Hey @cguindon, I love this idea! ;-) It makes perfect sense to me.

Will it impact our current webpage updating work? I guess not. Right?

Thx

No, the goal of this migration would be to move everything as-is. I will move all issues under the eclipse.org project so that we don't lose track of any work or discussion!

mentioned in merge request eclipse.org-research!75 (closed)

I am going to start working on this today.

//cc @pkriefrvi @oliviergoulet

Please let me know if you plan on proposing any big changes to the site while I work on this.

When do you think you will be done with this task, @cguindon ? I can stop working on that for a week or so. Thx

@pkriefrvi If all goes well, I should have something to review tomorrow.

@pkriefrvi I was able to spend some time tonight. If you have time, please take a look at the site migrated under the eclipse.org project: https://preview-41--www-eclipse-org.eclipsecontent.org/research/

MR: !41 (merged)

Let me know if you have any questions!

Note that you are likely to click on a link that brings you to the www.eclipse.org website.

This is a bug in a new preview service that I will need to fix with @mbarbero.

@mbarbero I will open a new issue about this but basically the issue is that for each preview, the site is build using the default baseurl which is https://www.eclipse.org/ because of: https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org/-/blob/main/config.toml#L1

With netlify, we used to work around that issue by using the -b, --baseURL string hostname (and path) to the root, e.g. http://spf13.com/ flag.

See: https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org-research/-/blob/master/netlify.toml#L21

For production, it's fine to use the default value in the config but we need to be able to set that value for all previews since the URL is unique.

Is that possible?

yes, it's possible. I'll push a fix.

Dear @cguindon I made a sniffed test and it looks good to me. Thx a lot. Do I need to switch to another repo if I want to make an update? Thx

@cguindon I've pushed a fix. Please verify https://preview-41--www-eclipse-org.eclipsecontent.org/

Note that the patch is not released, so if you rebuild the !41 (merged), it will fallback to last released version, without the fix.

Once you confirm that it fixes the issue, I'll do a release.

@pkriefrvi I can look at deploying the new version tomorrow during our webdev maintenance window if I can get this approved and merged today.

At that point, I will archive https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org-research in order for us to keep a copy for the history.

Once my work is merge, you will need to work with the eclipse.org project to propose changes to the research section: https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org

@mbarbero No it does not work. I can test by viewing this json page: https://preview-41--www-eclipse-org.eclipsecontent.org/research/projects/index.json?latest

The image property should say: "logo": "https://preview-41--www-eclipse-org.eclipsecontent.org/research/images/research/r-projects/nemo.png",

instead of: "logo": "https://www.eclipse.org/research/images/research/r-projects/nemo.png",

@mbarbero I had to rebuild the site to test this. I needed to implement the change that I mentioned here: !41 (comment 1043740)

If you can push it again, I can test it. It's probably why it's not working.

FWIW - I will likely need to merge my patch before you have time to look at this again. Might be best to test this via a new MR against the eclipse.org project?

moved from eclipse.org-research#69 (moved)

added Research label

@pkriefrvi I moved all the remaining open issues under https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org-research/-/issues to the eclipse.org project.

We should start to use the Research label to track all the "research" requests. I added that label on the 3 issues that I moved today: https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org/-/issues/?label_name%5B%5D=Research

I will now make the https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org-research read-only now that the content of the site was migrated to this repo.

I plan to deploy this new version on production tomorrow morning with @mward

added statewip label and removed statetodo label

@pkriefrvi I forgot to mention but I am changing the URL from https://www.eclipse.org/org/research/ to https://www.eclipse.org/research/.

I believe this is what you prefer.

I will have redirects in place to ensure that any existing links still work.

At this point, pretty much everything is done. We still need to remove the old site from OKD but I will do that in a couple of days incase we discover an issue with my migration and decide to revert back to the old website.

Hi @cguindon I forked the eclipse.org repo. When It try to build the site locally, I get an error:

Last login: Fri Nov 25 12:51:54 on console You have mail. philippe@PKs-MacBook-2 ~ % cd git philippe@PKs-MacBook-2 git % cd eclipse.org philippe@PKs-MacBook-2 eclipse.org % yarn yarn install v1.22.17 warning ../../package.json: No license field info No lockfile found. [1/4] Resolving packages... warning eclipsefdn-hugo-solstice-theme > eclipsefdn-solstice-assets > hogan.js > mkdirp@0.3.0: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) warning eclipsefdn-hugo-solstice-theme > eclipsefdn-solstice-assets > laravel-mix > node-libs-browser > url > querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. warning eclipsefdn-hugo-solstice-theme > eclipsefdn-solstice-assets > laravel-mix > cssnano > cssnano-preset-default > postcss-svgo > svgo > stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility [2/4] Fetching packages... [3/4] Linking dependencies... [4/4] Building fresh packages... [2/2] ⠂ eclipsefdn-hugo-solstice-theme error /Users/philippe/git/eclipse.org/node_modules/eclipsefdn-hugo-solstice-theme: Command failed. Exit code: 2 Command: npm run fetch_project && npm run production Arguments: Directory: /Users/philippe/git/eclipse.org/node_modules/eclipsefdn-hugo-solstice-theme Output:

eclipsefdn-hugo-solstice-theme@0.0.173 fetch_project node bin/projects/index.js -l exampleSite/data

Loading data using 'https://projects.eclipse.org/api/projects' as initial URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=2' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=3' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=4' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=5' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=6' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=7' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=8' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=9' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=10' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=11' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=12' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=13' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=14' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=15' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=16' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=17' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=18' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=19' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=20' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=21' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=22' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=23' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=24' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=25' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=26' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=27' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=28' as next URL Loading additional data using 'https://projects.eclipse.org/api/projects?pagesize=20&page=29' as next URL

eclipsefdn-hugo-solstice-theme@0.0.173 production NODE_ENV=production webpack --progress --config=node_modules/laravel-mix/setup/webpack.config.js

[webpack-cli] Failed to load '/Users/philippe/git/eclipse.org/node_modules/eclipsefdn-hugo-solstice-theme/node_modules/laravel-mix/setup/webpack.config.js' config [webpack-cli] Error: Cannot find module '/Users/philippe/git/eclipse.org/node_modules/eclipsefdn-hugo-solstice-theme/node_modules/laravel-mix/setup/webpack.config.js' Require stack:

• /Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/webpack-cli.js
• /Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/bootstrap.js
• /Users/philippe/git/eclipse.org/node_modules/webpack-cli/bin/cli.js
• /Users/philippe/git/eclipse.org/node_modules/webpack/bin/webpack.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:927:15) at Function.Module._load (node:internal/modules/cjs/loader:772:27) at Module.require (node:internal/modules/cjs/loader:999:19) at require (node:internal/modules/cjs/helpers:93:18) at WebpackCLI.tryRequireThenImport (/Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/webpack-cli.js:204:22) at loadConfigByPath (/Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/webpack-cli.js:1404:38) at /Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/webpack-cli.js:1454:88 at Array.map () at WebpackCLI.loadConfig (/Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/webpack-cli.js:1454:68) at WebpackCLI.createCompiler (/Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/webpack-cli.js:1785:33) { code: 'MODULE_NOT_FOUND', requireStack: [ '/Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/webpack-cli.js', '/Users/philippe/git/eclipse.org/node_modules/webpack-cli/lib/bootstrap.js', '/Users/philippe/git/eclipse.org/node_modules/webpack-cli/bin/cli.js', '/Users/philippe/git/eclipse.org/node_modules/webpack/bin/webpack.js' ] } info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this philippe@PKs-MacBook-2 eclipse.org %

How can I fix it? Thx a lot

I looked into it. I would also get an error at the same step. It seems like updating the Hugo theme with yarn add eclipsefdn-hugo-solstice-theme@0.0.174 --exact will fix it.

Thx @oliviergoulet. Indeed, it fixes the issue!

Indeed, there was an issue with some changes I did recently to migrate our documentation to our new infra.

eclipsefdn/it/webdev/hugo-solstice-theme!286 (diffs) is fixing that error.

I will update this website today.

I made an update to the site: 1935ec7a

Closing this issue but please re-open if you still have problems!

closed

added statedone label and removed statewip label