feat: integrate SvelteKit for seamless navigation and improved data loading

frontend/README.md

@@ -1,43 +1,39 @@
-# Svelte + Vite
+# Superset Tools Frontend (SvelteKit)
 
-This template should help get you started developing with Svelte in Vite.
+This is the frontend for the Superset Tools application, built with SvelteKit in SPA mode.
 
-## Recommended IDE Setup
+## Development
 
-[VS Code](https://code.visualstudio.com/) + [Svelte](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode).
+1.  **Install dependencies**:
+    ```bash
+    npm install
+    ```
 
-## Need an official Svelte framework?
+2.  **Run development server**:
+    ```bash
+    npm run dev
+    ```
+    The frontend will be available at `http://localhost:5173`. It is configured to proxy API requests to `http://localhost:8000`.
 
-Check out [SvelteKit](https://github.com/sveltejs/kit#readme), which is also powered by Vite. Deploy anywhere with its serverless-first approach and adapt to various platforms, with out of the box support for TypeScript, SCSS, and Less, and easily-added support for mdsvex, GraphQL, PostCSS, Tailwind CSS, and more.
+## Production Build
 
-## Technical considerations
+1.  **Build the static SPA**:
+    ```bash
+    npm run build
+    ```
+    This generates a static SPA in the `build/` directory.
 
-**Why use this over SvelteKit?**
+2.  **Serve with Backend**:
+    The Python backend is configured to serve the files from `frontend/build/`. Ensure the backend is running:
+    ```bash
+    cd ../backend
+    python src/app.py
+    ```
 
-- It brings its own routing solution which might not be preferable for some users.
-- It is first and foremost a framework that just happens to use Vite under the hood, not a Vite app.
+## Architecture
 
-This template contains as little as possible to get started with Vite + Svelte, while taking into account the developer experience with regards to HMR and intellisense. It demonstrates capabilities on par with the other `create-vite` templates and is a good starting point for beginners dipping their toes into a Vite + Svelte project.
-
-Should you later need the extended capabilities and extensibility provided by SvelteKit, the template has been structured similarly to SvelteKit so that it is easy to migrate.
-
-**Why include `.vscode/extensions.json`?**
-
-Other templates indirectly recommend extensions via the README, but this file allows VS Code to prompt the user to install the recommended extension upon opening the project.
-
-**Why enable `checkJs` in the JS template?**
-
-It is likely that most cases of changing variable types in runtime are likely to be accidental, rather than deliberate. This provides advanced typechecking out of the box. Should you like to take advantage of the dynamically-typed nature of JavaScript, it is trivial to change the configuration.
-
-**Why is HMR not preserving my local component state?**
-
-HMR state preservation comes with a number of gotchas! It has been disabled by default in both `svelte-hmr` and `@sveltejs/vite-plugin-svelte` due to its often surprising behavior. You can read the details [here](https://github.com/sveltejs/svelte-hmr/tree/master/packages/svelte-hmr#preservation-of-local-state).
-
-If you have state that's important to retain within a component, consider creating an external store which would not be replaced by HMR.
-
-```js
-// store.js
-// An extremely simple external store
-import { writable } from 'svelte/store'
-export default writable(0)
-```
+- **Routing**: File-based routing in `src/routes/`.
+- **Layouts**: Shared UI in `src/routes/+layout.svelte`.
+- **Data Loading**: `load` functions in `+page.ts` for efficient data fetching.
+- **API Client**: Centralized API logic in `src/lib/api.js`.
+- **Styling**: Tailwind CSS.