added documentation, aligned folder structure with style guide

documentation/Architecture.md

@@ -0,0 +1,23 @@
+# Architecture
+Headscale-UI is based on the [svelte-kit](https://kit.svelte.dev/) framework and designed to compile to static HTML/JS/CSS. As such, once built (with `npm run build` or by downloading the packages), Headscale-UI can be hosted on any static file server (including headscale's static file server, once support has been added)
+
+## App Design
+Headscale-UI uses the `static` adapter built into svelte-kit, meaning that several svelte-kit functions are not feasible in a static deploymnet. Backend services (such as any route ending in `.js` or `.ts`) cannot be used, and most if not all script functions should be defined within the `onMount` function of svelte.
+
+### Client Side Design
+All Headscale-UI features and functions should be client side only. *Any* backend features should be considered to be implemented in a separate backend. This can be the [Headscale](https://github.com/juanfont/headscale) application itself (preferred), or potentially implementing a Backend-as-a-Service API such as [Supabase](https://supabase.com/).
+
+### Authentication and Authorization
+In the current alpha format, the headscale API secret is stored within the browser's `localStorage` area. This method of credential storage is not ideal as localStorage can potentially be exploited by XSS (cross-site scripting) vulnerabilities. The long term goal is to integrate Headscale-UI into Headscale's OIDC authentication capabilities, but discovery is required to implement this feature (as well as cooperation from the upstream project).
+
+For now, it is recommended that credentials only be saved on trusted computers and to use short API key expiries where possible.
+
+## Dependencies
+Dependencies are kept to a minimum and kept to large, actively maintained repositories. Great care should be taken before suggesting or adding any additional dependencies: headscale is a sensitive tool and attack surfaces must be kept minimal.
+
+### Dev Dependencies
+* [SvelteKit](https://kit.svelte.dev/) - The HTML/JS Framework and Toolkit
+* [Tailwind CSS](https://tailwindcss.com/) - The CSS Framework
+* [Post CSS](https://postcss.org/) - for compiling tailwind
+* [Typescript](https://www.typescriptlang.org/) - for static type checking
+* [Prettier](https://prettier.io/) - for Code Formatting

documentation/Style.md

@@ -0,0 +1,12 @@
+# Style
+Rough style guide for development in Headscale-UI. Documentation will be improved as style gets more defined
+
+## CSS
+CSS should be written as tailwind classes. Where (when) tailwind classes become cumbersome (10+ classes for an HTML object), classes should instead be broken into a separate `<style>` section of the svelte component with common naming conventions (such as `.btn-primary` for common buttons).
+
+`<style>` classes that span multiple components should be defined in the `/src/app.css` file.
+
+## Naming Conventions
+* Svelte pages are defined in the `/src/routes` directory and should follow a lower case, single word description, followed by extension and `.svelte`. (such as `settings.html.svelte`).
+* Svelte components ate defined in the `/src/lib` directory and should be kept in subfolders. Subfolders should be defined by the route page, followed by the component name. Svelte components are defined by single word, Capitalized descriptions (such as `UserCard`.svelte
+* Variables are defined