fix: documentation formatting

This commit is contained in:
Valerio Ageno
2024-08-15 21:08:48 +02:00
parent 92820804f8
commit a0a81b514c
7 changed files with 27 additions and 34 deletions
@@ -7,7 +7,7 @@ import { Head } from 'tuono'
import Breadcrumbs, { Element } from '../../components/breadcrumbs'
<Breadcrumbs>
<Element label="✨ Contributing"/>
<Element label="✨ Contributing" />
</Breadcrumbs>
# Contributing
@@ -25,26 +25,24 @@ The `tuono` project can mostly be split by the following sub-domains:
- The react frontend
- The documentation website (which is written with tuono 🚀)
To check what are the knowledge requirement for each domain check the
To check what are the knowledge requirement for each domain check the
[requirements](/documentation/contributing?#requirements) section below.
Currently I'm keeping a private dashboard to prioritize new features and bug fixes but if you
Currently I'm keeping a private dashboard to prioritize new features and bug fixes but if you
want to propose something please open a new issue on github or reach me using
my email address [valerioageno@yahoo.it](mailto:valerioageno@yahoo.it). I'm also available
my email address [valerioageno@yahoo.it](mailto:valerioageno@yahoo.it). I'm also available
on twitter (X) DMs `@valerioageno`, [linkedin](https://www.linkedin.com/in/valerioageno)
and discord `@__v__v__`.
## Requirements
It's not strictly required to know both React (& typescript) and Rust (even though it
would be a great nice to have).
would be a great nice to have).
Without taking into account specific cases we can mostly split the domain requirements by:
- The `CLI` needs Rust knowledge (even though a couple of scenario might need also Typescript)
- The Backend needs just `Rust`
- The Frontend needs just `React` & `Typescript`
- The documentation website needs just `React` & `Typescript` (or even less since most of the
code is markdown).
- The documentation website needs just `React` & `Typescript` (or even less since most of the
code is markdown).
@@ -7,22 +7,21 @@ import { Head } from 'tuono'
import Breadcrumbs, { Element } from '../../components/breadcrumbs'
<Breadcrumbs>
<Element label="Getting started"/>
<Element label="Getting started" />
</Breadcrumbs>
# Getting started
Tuono is the CLI that provides all the needed commands to handle the fullstack project.
Tuono is the CLI that provides all the needed commands to handle the fullstack project.
> ☝️ Check the [installation](/documentation/installation) page if you haven't installed the
`tuono` CLI yet.
> `tuono` CLI yet.
To list all the available commands run `tuono -h`.
To create a new project run `tuono new [NAME]` (optionally you can pass the --template (or -t) flag - check the examples folder).
Then to run the local development environment run inside the project folder `tuono dev`
Then to run the local development environment run inside the project folder `tuono dev`
Finally when the project will be ready to be deployed just run `tuono build` to create the final React assets and to set the server project in the production mode.
@@ -6,8 +6,7 @@ import { Head } from 'tuono'
import Breadcrumbs from '../../components/breadcrumbs'
<Breadcrumbs>
</Breadcrumbs>
<Breadcrumbs></Breadcrumbs>
# Tuono
@@ -20,18 +19,18 @@ Tuono (Italian word for "thunder", pronounced /2 Oh No/). Why Tuono? Just a bada
**NodeJs/Deno/Bun are the only runtimes that allow a React app to be fullstack right? (no)**
Tuono is a fullstack React framework with the server side written in Rust.
Because of this Tuono is extremely fast and the requests are handled by multithreaded Rust server.
Tuono is a fullstack React framework with the server side written in Rust.
Because of this Tuono is extremely fast and the requests are handled by multithreaded Rust server.
React is still React - it is just superpowered.
**Rust is an 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
Tuono provides a collection of utilities to handle the server side code seamlessly with
the React code. Each server side route is managed with a separate file alongside the React route.
The routing is handled by Tuono based on the files defined within the `./src/routes` directory.
## Features
## Features
Some of its features include:
- 🟦 Full typescript support
@@ -40,11 +39,10 @@ Some of its features include:
- 🍭 SCSS/CSS modules
- 🧬 Server Side Rendering
- 🧵 Multi thread backend
- ⌨️ MDX support
- ⚙️ Build optimizations
- Custom APIs*
- Image optimization*
- Server streamed content*
> *development in progress
- ⌨️ MDX support
- ⚙️ Build optimizations
- Custom APIs\*
- Image optimization\*
- Server streamed content\*
> \*development in progress
@@ -6,7 +6,7 @@ import Breadcrumbs, { Element } from '../../components/breadcrumbs'
</Head>
<Breadcrumbs>
<Element label="Installation"/>
<Element label="Installation" />
</Breadcrumbs>
# Installation
@@ -7,7 +7,7 @@ import { Head } from 'tuono'
import Breadcrumbs, { Element } from '../../../components/breadcrumbs'
<Breadcrumbs>
<Element label="Routing"/>
<Element label="Routing" />
</Breadcrumbs>
# Routing index
@@ -7,8 +7,8 @@ import { Head } from 'tuono'
import Breadcrumbs, { Element } from '../../../components/breadcrumbs'
<Breadcrumbs>
<Element label="Routing" href="/documentation/routing"/>
<Element label="Project structure"/>
<Element label="Routing" href="/documentation/routing" />
<Element label="Project structure" />
</Breadcrumbs>
# Project structure
@@ -7,7 +7,7 @@ import { Head } from 'tuono'
import Breadcrumbs, { Element } from '../../../components/breadcrumbs'
<Breadcrumbs>
<Element label="Tutorial"/>
<Element label="Tutorial" />
</Breadcrumbs>
# Tutorial
@@ -15,5 +15,3 @@ import Breadcrumbs, { Element } from '../../../components/breadcrumbs'
You can find the tutorial [here](https://github.com/Valerioageno/tuono/blob/main/docs/tutorial.md).
Other tasks have the priority right now. The tutorial will be ported here as soon as possible.