HaiLin/ai-ticket-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: sync stage 2 knowledge progress

Browse Source
This commit is contained in:
hailin
2026-07-03 17:59:36 +08:00
parent 94f0488341
commit 6625278c6d
3 changed files with 48 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/frontend/design-system.md
View File

@@ -71,6 +71,8 @@ Business pages should use:
- Ticket status transitions use `TicketTransitionDialog`. Resolution and closure actions can carry a solution summary; non-resolution workflow actions still require a handling note.
- Ticket workflows are category-driven: business and operation issues support short closure paths, data issues use a medium path, and technical issues keep the standard support workflow.
- Linked solutions support search, recommendation-only linking, adoption with automatic ticket closure, and prefilled resolution text during later resolve/close actions.
- Knowledge pages use the same `AppPage`, `AppSection`, `AppDataTable`, `AppField`, and shadcn form primitives as ticket and system pages.
- Knowledge search results must show source type, title, score, and citable content snippets.
- System governance quick-create forms use `AppSection`, `FieldGroup`, and `AppField`.
Preview page: