API Demo Probe parent 163849
Next Topic(s):
Created:
23rd of February 2026
04:38:49 PM
Modified:
23rd of February 2026
06:28:03 PM
API Demo Revision v5: Rich Note Boxes
This draft expands callout patterns, code utilities, and diagram support for review.
This line was directly added by admin and the draft was saved. Check if this can be identified - Not only published page, but also the saved draft of a page must be checked.
1.1 Expanded Note Boxes
Definition: Structured callouts separate concept definition, operational caution, and implementation guidance.
Good Practice: Use one concrete message per callout and keep labels consistent across chapters.
Common Pitfall: If every paragraph becomes a callout, important warnings lose visibility.
Did You Know: API sync can create multiple pending revisions while an earlier approved version stays active.
AECO Insight: Site teams scan callout boxes first during quick review before progress meetings.
Performance Tip: Keep code examples short in review pages to reduce visual clutter and copy mistakes.
Security Note: Do not expose client secret or bearer tokens inside instructional page content.
Indian Regulatory Note: Approval history and archived revisions support audit traceability for project records.
1.2 Mermaid Check
flowchart TB
A[Version 3 Approved] --> B[Version 4 Pending]
B --> C[Version 5 Pending]
C --> D[Review Decision]
1.3 Copy and Line Number Check
-- Fetch versions for demo page
GET /index.php/ccm/api/1.0/page_versions/469
-- Publish specific version (when required)
PUT /index.php/ccm/api/1.0/page_versions/469/5
{
"is_approved": true
}
1.4 Review Checklist
- All note boxes render with icon and label.
- Mermaid diagram renders after library load.
- Copy button returns plain code text.
- This draft remains pending until explicit approval.