4e02d5bc97
- Imported packages from separate repos: - github.com/Snider/config -> pkg/config - github.com/Snider/display -> pkg/display - github.com/Snider/help -> pkg/help - github.com/Snider/i18n -> pkg/i18n - github.com/Snider/updater -> pkg/updater - Moved core code from root to pkg/core - Flattened nested package structures - Updated all import paths to github.com/Snider/Core/pkg/* - Added Display interface to Core - Updated go.work for workspace modules Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
29 lines
926 B
Markdown
29 lines
926 B
Markdown
# Frontend Documentation
|
|
|
|
The frontend is an Angular application located in the `ui/` directory. It is designed to be built as a custom element or a standalone application that runs inside the Wails webview.
|
|
|
|
## Structure
|
|
|
|
- **Path:** `ui/`
|
|
- **Framework:** Angular
|
|
- **Output:** The build process generates artifacts in `ui/dist`.
|
|
|
|
## Development
|
|
|
|
The frontend can be developed using standard Angular CLI commands or via the provided demo CLI which serves the built files.
|
|
|
|
## Build Process
|
|
|
|
To build the frontend for production or integration with the Go backend:
|
|
|
|
```bash
|
|
cd ui
|
|
npm install
|
|
npm run build
|
|
```
|
|
|
|
This will compile the Angular application and place the output in the `dist/` directory, which the Go backend can then serve or embed.
|
|
|
|
## Integration
|
|
|
|
The frontend communicates with the Go backend through the Wails runtime. It can trigger actions defined in the backend (like opening windows) and receive events.
|