feat: expand documents to include manuals
This commit is contained in:
@@ -22,25 +22,18 @@ You are a senior software engineer specializsing in NodeJS, Typescript, front en
|
||||
- Make no assumptions.
|
||||
- Ask clarifying questions.
|
||||
- Ultrathink
|
||||
- You will be implementing a backup and restore functionality directly in this application.
|
||||
- You will be extending the "Documents" feature to include manuals.
|
||||
|
||||
*** CONTEXT ***
|
||||
- This is a modern web app for managing a vehicle fleet. It has both a desktop and mobile versions of the site that both need to maintain feature parity. It's currently deployed via docker compose but in the future will be deployed via k8s.
|
||||
- Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change.
|
||||
- There is no backup and restore functionality in this system.
|
||||
- There needs to be a new section added in the admin settings. Here are the files and line numbers of existing admin settings to base this change off of and mirror those.
|
||||
frontend/src/pages/admin/AdminEmailTemplatesPage.tsx
|
||||
192: Manage notification email templates
|
||||
|
||||
frontend/src/pages/SettingsPage.tsx
|
||||
436: secondary="Manage notification email templates"
|
||||
|
||||
frontend/src/features/settings/mobile/MobileSettingsScreen.tsx
|
||||
430: <div className="text-sm text-blue-600 mt-1">Manage notification email templates</div>
|
||||
- There currently is a folder data/backups/ that is empty. Evaluate if this should be used or if another one makes more sense.
|
||||
- The admin page should show all the local backups. But also allow for uploading a backup.
|
||||
- The admin page should have a option to create a manual backup and download it.
|
||||
- The admin page should have the ability to schedule backups as hourly, daily, weekly, monthly. And also allow multiple schedules and retention policies.
|
||||
- You need to extend the Documents feature to include a third "Document Type"
|
||||
- Right now the document has two types. Insurance and Registration
|
||||
- The third type will be called "Manual"
|
||||
- This document will just have the uploaded file and a notes field and Title field
|
||||
- When implementing this we need to play for the future feature of scanning the document for maintenance schedules
|
||||
- Add a toggle for this scanning. Label it "Scan for Maintenance Schedule"
|
||||
- Do not implement this feature at this time but put the toggle in the interface and the backend changes to facility this workflow.
|
||||
|
||||
*** CHANGES TO IMPLEMENT ***
|
||||
- Research this code base and ask iterative questions to compile a complete plan.
|
||||
|
||||
Reference in New Issue
Block a user