AI Implementation feature(914): Admin Area Blog and Blog Page 1.00 (#59)
This commit was merged in pull request #59.
This commit is contained in:
+9
-1
@@ -3,7 +3,7 @@ type: guide
|
||||
title: Blog Publishing and Reading
|
||||
description: How administrators create, edit, publish, and delete Markdown posts and how users read published posts.
|
||||
tags: [guide, blog, admin, markdown, tester]
|
||||
timestamp: 2026-07-23T10:12:24Z
|
||||
timestamp: 2026-07-23T10:36:45Z
|
||||
---
|
||||
|
||||
# User views
|
||||
@@ -34,6 +34,14 @@ Both views use `BlogPresenterComponent` to show the post title, publication date
|
||||
* Click the trash action to open **Delete post**. The confirmation includes the title and warns that deletion cannot be undone.
|
||||
* Click **Delete** to remove the post. The table refreshes and displays `Post deleted.`. Click **Cancel** or the modal backdrop to leave the post unchanged.
|
||||
|
||||
# Closing modals with Escape
|
||||
|
||||
Both the **New post / Edit post** modal and the **Delete post** confirmation honor the platform-wide Escape-to-close convention:
|
||||
|
||||
* Pressing **Escape** while the modal is open closes it without saving or deleting.
|
||||
* Escape is suppressed while a save/publish request is in flight (the modal stays open until the current operation completes), so an in-flight create or update cannot be silently cancelled by an accidental keypress.
|
||||
* Escape, the **Cancel** / **Delete** buttons, and clicking the modal backdrop all close the modal via the same `onCancel()` → `cancel` output flow; no partial post is ever created or modified when Escape is pressed.
|
||||
|
||||
# Validation and expected errors
|
||||
|
||||
| Input or operation | Expected behavior |
|
||||
|
||||
Reference in New Issue
Block a user