From be87d73d5dd93277491af8f495c1e9c159a41716 Mon Sep 17 00:00:00 2001 From: Simon Hyll Date: Tue, 22 Aug 2023 00:52:54 +0200 Subject: [PATCH] working on it --- src/content/docs/2/guide/develop.mdx | 65 +++++-------------- .../2/guide/framework/frontend-agnostic.mdx | 21 ++++++ .../framework/{svelte.mdx => sveltekit.mdx} | 2 +- 3 files changed, 37 insertions(+), 51 deletions(-) create mode 100644 src/content/docs/2/guide/framework/frontend-agnostic.mdx rename src/content/docs/2/guide/framework/{svelte.mdx => sveltekit.mdx} (98%) diff --git a/src/content/docs/2/guide/develop.mdx b/src/content/docs/2/guide/develop.mdx index d889329ba5..cbae8ad91d 100644 --- a/src/content/docs/2/guide/develop.mdx +++ b/src/content/docs/2/guide/develop.mdx @@ -10,62 +10,27 @@ Tauri is frontend agnostic, but sometimes frameworks need a bit of extra attenti nicely with Tauri. The frameworks listed below are by no means a list of officially supported frameworks, if your framework isn't listed it can most likely be made to work with Tauri as well. + + ### Javascript - - - - - - + + + + + + ### Rust - - - - + + + + diff --git a/src/content/docs/2/guide/framework/frontend-agnostic.mdx b/src/content/docs/2/guide/framework/frontend-agnostic.mdx new file mode 100644 index 0000000000..b054573f45 --- /dev/null +++ b/src/content/docs/2/guide/framework/frontend-agnostic.mdx @@ -0,0 +1,21 @@ +--- +title: Frontend agnostic +--- + +import { Tabs, TabItem } from '@astrojs/starlight/components'; + +Tauri has no opinion on what frontend framework you pick or what languages you use. However, that doesn't mean that +Tauri doesn't have any demands on it. + +Within web development the concept of frontend agnosticism is more commonly referred to as static web hosting. That is, +you compile your website once and can then put it into any http framework capable of serving a folder. Examples of this +is for example Apache and Nginx. + +For all intents and purposes you can think of Tauri as a static web host, and you have to provide Tauri with a folder +containing some mix of HTML, CSS, Javascript and possibly WASM that can be served to the webview Tauri provides. + +## Checklist + +- Use static site generation (SSG). Tauri doesn't officially support any server based alternatives (SSR). +- For mobile development a development server of some kind is necessary that can host the frontend on your internal IP. +- Use a proper client-server relationship between your app and your API's. So no hybrid solutions with SSR. diff --git a/src/content/docs/2/guide/framework/svelte.mdx b/src/content/docs/2/guide/framework/sveltekit.mdx similarity index 98% rename from src/content/docs/2/guide/framework/svelte.mdx rename to src/content/docs/2/guide/framework/sveltekit.mdx index bd8e327968..c6468b23da 100644 --- a/src/content/docs/2/guide/framework/svelte.mdx +++ b/src/content/docs/2/guide/framework/sveltekit.mdx @@ -1,5 +1,5 @@ --- -title: Svelte +title: SvelteKit --- import { Tabs, TabItem } from '@astrojs/starlight/components';