Remove the website in favor of the new org-level site

[captainbrosset]

• We have a new logo, see WebDX Community Group logo #3820.
• We decided that the site should be hosted at the org level, so I moved the source code to the https://github.com/web-platform-dx/web-platform-dx.github.io/ repo, which is now published at https://web-platform-dx.github.io/
• I also made some modifications to the site:
  • Add the new logo in header + favicon.
  • Made the WebDX CG page be the landing page.
  • Added a dark theme.
  • Made some minor CSS improvements.
  • Made some minor content improvements.

Currently, the /web-features/ path still goes to the current repo.
Once we merge this PR, the current repo will stop hosting the site, and the /web-features/ path will start being served by the org-level gh-pages site.
At the org-level site, the /web-features/ path is redirected to /baseline/. This is so that existing links aren't broken, and improve the site. The /web-features/ path was a technical one only, due to the our repo's name. In reality, web-features and baseline are 2 different things, and the new /baseline/ makes a lot more sense here.

[captainbrosset]

@sebazelonka thank you very much for your logo proposal! I took the liberty to modify it a tiny bit, as you can see above.

I'd love for our group to adopt this logo. Are you good with this?

[captainbrosset]

Note for myself: revert the change where I made the CG page be the homepage instead of the Baseline page. We don't want to do this in this PR, to avoid breaking existing links.
Future plan: move the CG homepage to the github org level, and keep this repo for the baseline page.

[sebazelonka]

@captainbrosset I love the gradient and how the proportions are adjusted. TBH, I don't like too much where the WebDX is, I like it more just beside the Icon, but if the idea is to have something bigger in the same width, I think is the right alternative.

[NiklasMerz]

The new logo and website is looking sharp

[tidoust]

At the org-level site, the /web-features/ path is redirected to /baseline/

Not sure how Eleventy manages redirect-like pages, but it seems to me that the code in the org-level site will only redirect /web-features/, and not subpages such as /web-features/supported-browsers/. I do not know whether there are sources that currently target these subpages but they may be worth redirecting too?

The approach looks good to me, and the structure makes more sense. I propose to re-add the Baseline wordmark in the /baseline/ page, see web-platform-dx/web-platform-dx.github.io#1

[captainbrosset]

Not sure how Eleventy manages redirect-like pages, but it seems to me that the code in the org-level site will only redirect /web-features/, and not subpages such as /web-features/supported-browsers/. I do not know whether there are sources that currently target these subpages but they may be worth redirecting too?

Correct, only the /web-features/ path is redirected, as this is the most important one. I'm much less worried about the other ones, but sure, we can add redirect pages to handle them too.

The approach looks good to me, and the structure makes more sense. I propose to re-add the Baseline wordmark in the /baseline/ page, see web-platform-dx/web-platform-dx.github.io#1

Done! Thanks for the PR.

[captainbrosset]

Not sure how Eleventy manages redirect-like pages, but it seems to me that the code in the org-level site will only redirect /web-features/, and not subpages such as /web-features/supported-browsers/. I do not know whether there are sources that currently target these subpages but they may be worth redirecting too?

Correct, only the /web-features/ path is redirected, as this is the most important one. I'm much less worried about the other ones, but sure, we can add redirect pages to handle them too.

Done, see the *-redirect.html files in https://github.com/web-platform-dx/web-platform-dx.github.io/tree/main/src