website: Tabula rasa

[Eomm]

Since the new site project has been stuck for 1 year, I'm volunteering to take ownership to complete it.

I tried to do some cherry-picking to keep the good work made by @lachlancollins and @Xhale1, but it is too much effort. So I hope they will get the chance to submit a new commit 😆

What does "complete" mean? - Required features

The website MVP will be considered completed when:

• the website shows these pages:
  • the index page (project and team forward)
  • the ecosystem page
  • the benchmarks page
  • the contribute page
• the docs pages show:
  • the fastify v1 docs (only the latest version): no embellishment here
  • the fastify v2 docs (only the latest version): no embellishment here
  • the fastify v3 docs (only the latest version): no embellishment here
  • the fastify v4.x docs:
    • every semver minor version has its own docs/ page
    • upgrade the docs to be more readable
• the user can search through the docs
• SEO optimized
• Handle old website links

Nice to have

These features are not going to be done - but we will try to implement the required features keeping in mind the following list:

• internationalization
  • Korean https://github.com/fastify/docs-korean
  • Chinese https://github.com/fastify/docs-chinese
  • Portuguese https://github.com/fastify/docs-portuguese
• New Getting started introduction
• Migrate the blog from https://medium.com/@fastifyjs to this new website
• Helper: the user can search across GitHub issues

What are the new website constraints?

The constraints are:

1. we must ship fastify with the latest docs
2. we must deal with the old links (eg: redirect)
3. a fastify contributor must update the docs on the main repo fastify/fastify
4. we can't include any doc changes to fastify <=3

What do I mean by "ownership"?

I think this project has been starving because the decisions and feedback cycle were slow and we brought many more doubts than solutions.

So I'm asking to @fastify/collaborators, is to define constraints and required features
now. Then the people willing to work on this project will be able to work efficiently till things are done.

Using or not docusaurus can't be a constraint. I think I can guarantee that the new website team will not deliver some unmaintainable website and if the team has chosen docusaurus, I can say that, after using it a bit, it is very usable and well documented. (I tried ELEVENTY and I did not enjoy it). Let me be pragmatic: in any case, whatever tech would be better than the actual metalsmith aged solution.

I hope @lachlancollins and @Xhale1 are willing to work on this project revamp too.

What does this PR?

This PR is useful for me: I learnt docusaurus and I understood its mechanics.
This PR bump all the deps to the non-beta ones and set up the configuration in the most stable and complete way.

[mcollina]

lgtm

[Eomm]

Here all the info to help with the project: #32