Skip to content

Commit

Permalink
working on it
Browse files Browse the repository at this point in the history
  • Loading branch information
simonhyll committed Aug 24, 2023
1 parent b5271a6 commit be87d73
Show file tree
Hide file tree
Showing 3 changed files with 37 additions and 51 deletions.
65 changes: 15 additions & 50 deletions src/content/docs/2/guide/develop.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<LinkCard
title="Frontend agnostic"
href="/2/guide/framework/frontend-agnostic"
/>

### Javascript

<CardGrid>
<LinkCard
title="Next.js"
href="/2/guide/framework/nextjs"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard
title="Nuxt"
href="/2/guide/framework/nuxt"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard
title="Qwik"
href="/2/guide/framework/qwik"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard
title="Svelte"
href="/2/guide/framework/svelte"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard
title="Vite"
href="/2/guide/framework/vite"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard
title="Webpack"
href="/2/guide/framework/webpack"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard title="Next.js" href="/2/guide/framework/nextjs" />
<LinkCard title="Nuxt" href="/2/guide/framework/nuxt" />
<LinkCard title="Qwik" href="/2/guide/framework/qwik" />
<LinkCard title="SvelteKit" href="/2/guide/framework/sveltekit" />
<LinkCard title="Vite" href="/2/guide/framework/vite" />
<LinkCard title="Webpack" href="/2/guide/framework/webpack" />
</CardGrid>

### Rust

<CardGrid>
<LinkCard
title="Trunk"
href="/2/guide/framework/trunk"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard
title="Yew"
href="/2/guide/framework/yew"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard
title="Sycamore"
href="/2/guide/framework/sycamore"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard
title="Leptos"
href="/2/guide/framework/leptos"
description="Some frameworks require special attention to work well with mobile development"
/>
<LinkCard title="Trunk" href="/2/guide/framework/trunk" />
<LinkCard title="Yew" href="/2/guide/framework/yew" />
<LinkCard title="Sycamore" href="/2/guide/framework/sycamore" />
<LinkCard title="Leptos" href="/2/guide/framework/leptos" />
</CardGrid>
21 changes: 21 additions & 0 deletions src/content/docs/2/guide/framework/frontend-agnostic.mdx
Original file line number Diff line number Diff line change
@@ -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.
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Svelte
title: SvelteKit
---

import { Tabs, TabItem } from '@astrojs/starlight/components';
Expand Down

0 comments on commit be87d73

Please sign in to comment.