Improve settings hints and workspace log clarity
This commit is contained in:
@@ -9,4 +9,4 @@ This directory contains technical documentation for DMS.
|
||||
- `api-contract.md` - API endpoint contract grouped by route module, including settings and processing-log trim defaults
|
||||
- `data-model-reference.md` - database entity definitions and lifecycle states
|
||||
- `operations-and-configuration.md` - runtime operations, ports, volumes, and persisted settings configuration
|
||||
- `frontend-design-foundation.md` - frontend visual system, tokens, and UI implementation rules
|
||||
- `frontend-design-foundation.md` - frontend visual system, tokens, UI implementation rules, and settings helper-copy guidance
|
||||
|
||||
@@ -50,3 +50,10 @@ When adding or redesigning a UI area:
|
||||
3. Implement component styles in `frontend/src/styles.css` using existing layout and variant conventions.
|
||||
4. Validate responsive behavior at `1240px`, `1040px`, `760px`, and `560px` breakpoints.
|
||||
5. Verify keyboard focus visibility and text contrast before merging.
|
||||
|
||||
## Settings UX Copy
|
||||
|
||||
- Keep helper copy in settings short and plain language, especially on advanced model and threshold controls.
|
||||
- Prefer one concise hint per advanced control that explains practical impact rather than internals.
|
||||
- In the Workspace settings block, keep processing-log controls visually separated from default path and tag behavior.
|
||||
- Processing-log hints must explicitly state they affect logs and retention behavior, not document metadata values.
|
||||
|
||||
Reference in New Issue
Block a user