Update getting started (#82)

* feat: update getting started doc

* feat: update README

apps/documentation/src/components/sidebar/sidebar.tsx

@@ -4,7 +4,11 @@ import SidebarLink from './sidebar-link'
 export default function Sidebar({ close }: { close: () => void }): JSX.Element {
   return (
     <AppShell.Navbar p="md">
-      <SidebarLink href="/documentation" label="Overview" onClick={close} />
+      <SidebarLink
+        href="/documentation"
+        label="Getting started"
+        onClick={close}
+      />
       <SidebarLink
         href="/documentation/installation"
         label="Installation"

apps/documentation/src/routes/documentation/index.mdx

@@ -12,39 +12,43 @@ import Breadcrumbs from '../../components/breadcrumbs'
 
 # Tuono
 
-Tuono is a full-stack framework for building React applications using Rust as the
-backend.
+Tuono is a full-stack web framework for building React applications using Rust as the
+backend with a strong focus on usability and performance.
 
 Tuono (Italian word for "thunder", pronounced /2 Oh No/). Why Tuono? Just a badass name.
 
-## Introduction
-
-NodeJs/Deno/Bun are the only runtimes that allow a React app to be full-stack right? (no)
-
-Tuono is a full-stack React framework with the server side written in Rust.
-Because of this, Tuono is extremely fast and, the requests are handled by a multithreaded Rust server.
-React is still React - it is just superpowered.
-
-Rust is a hard language, then writing server side code is hard as well, right? (no again)
-
-Tuono provides a collection of utilities to handle the server side code seamlessly with
-the React code. Each server side route is managed in a separate file alongside the React route.
-The routing is handled by Tuono based on the files defined within the `./src/routes` directory.
+If you have experience with [Next.js](https://nextjs.org/) you will feel home here.
 
 ## Features
 
-Some of its features include:
-
-- 🟦 Full typescript support
-- 🌐 File system based routing
-- 🔥 Hot Module Reload
-- 🍭 SCSS/CSS modules
+- 🟦 Native Typescript
+- 🌐 Next.js like Routing
+- 🍭 CSS/SCSS modules
 - 🧬 Server Side Rendering
-- 🧵 Multi-threaded backend
-- ⌨️ MDX support
-- ⚙️ Build optimizations
-- Custom APIs\*
-- Image optimization\*
-- Server streamed content\*
+- 🔥 Hot Module Reload
 
-> \*development in progress
+## Introduction
+
+Tuono addresses the following two limits:
+
+- Enable React server-side rendering projects without using JS runtimes (Node, Deno)
+- Ease the web development using a typically hard language like Rust.
+
+#### NodeJs/Deno/Bun are the only runtimes that allow a React app to be server-side rendered (SSR)? (no)
+
+Tuono is the first full-stack React framework with the server side written in Rust (check the [ssr-rs](https://github.com/Valerioageno/ssr-rs) crate).
+Because of this, Tuono is extremely fast, and the requests are handled by a multithreaded Rust server.
+React is still React - it is just superpowered.
+
+#### Rust is a hard language, then writing server side code is hard as well, right? (no again)
+
+Tuono provides a collection of utilities to handle server-side code seamlessly with
+the React code. Each server side route is managed in a separate file alongside the React route.
+The routing is handled by Tuono based on the files defined within the `./src/routes` directory.
+
+#### How is Tuono different from Next.js?
+
+The Tuono API tries to stick as much as possible to the Next.js one (or at least takes a huge inspiration
+from it). The major difference is the backend system. While Next.js relies entirely on Node/Deno/Bun,
+Tuono runs the server without any intermediary runtime. This enables impressive performance improvements
+(check the benchmarks [here](https://github.com/Valerioageno/tuono/tree/main/benches)).