Naser Mansour
0f9d12c3cf
Adds docs/tasks/ (16 epics + 102 stories converted to task/subtask files with statuses.md as the new status source of truth) and docs/ux-design.md (retrospective design-system reference), and points CLAUDE.md at them. docs/prd.md and docs/architecture.md are kept as BMAD wrote them; the legacy docs/stories/, docs/epics/, docs/qa/gates/ and .bmad-core/ stay in place as historical/traceability records, superseded but not deleted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
27 lines
1014 B
Markdown
27 lines
1014 B
Markdown
---
|
|
id: 5-3
|
|
title: 5-3 Post Deletion
|
|
status: QA Review
|
|
date: 2026-09-27
|
|
parent: 5
|
|
---
|
|
|
|
## Description
|
|
|
|
As an admin, I want to permanently delete posts, So that I can remove outdated or incorrect content from the website. Context: Integrates with: posts table; Technology: Livewire Volt; Follows pattern: Permanent delete pattern. Add delete button to the post edit form (from Story 5.1) when editing an existing post:. Full implementation history: docs/stories/story-5.3-post-deletion.md
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] Delete button on post list (primary location)
|
|
- [ ] Delete button on post edit page (secondary location)
|
|
- [ ] Confirmation modal dialog before deletion
|
|
- [ ] Permanent deletion (no soft delete per PRD)
|
|
- [ ] Success message after deletion
|
|
- [ ] Redirect to post list after deletion from edit page
|
|
- [ ] Admin-only access (middleware protection)
|
|
- [ ] Audit log entry preserved
|
|
- [ ] Old values stored in log
|
|
- [ ] Clear warning in confirmation
|
|
- [ ] Bilingual messages
|
|
- [ ] Tests for deletion
|