feat: Upgrading documentation

[KanishkKhurana]

Why?

The docs structure has been confusing and distracting for a while. When someone wants to host a site on fleek or use fleek functions, we always split their attention between platform and cli instead of providing details on the value proposition and letting them take a decision thereafter.

therefore this PR has been raised to fix structural issues, developer experience issues and overall state of the docs.

some references have been drawn from this notion page made by some members of the product and devrel team -
https://www.notion.so/fleek/Docs-Revision-Proposal-128f6926f8dc804bba31fcf1da985f4b

How?

• Introduce guided selectors everywhere
• defined overview pages
• used tabs for platform and cli
• use features on the sidebar instead of platform and cli
• revamped some content on the docs

Contribution checklist?

• The commit messages are detailed
• The build command runs locally
• Assets or static content are linked and stored in the project
• Document filename is named after the slug
• You've reviewed spelling using a grammar checker
• For documentation, guides or references, you've tested the commands and steps
• You've done enough research before writing

Preview?

Screen.Recording.2024-12-12.at.5.55.04.PM.mov

[changeset-bot]

⚠️ No Changeset found

Latest commit: 96de4e4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR