mirror of
https://github.com/Studio-Saelix/sencho.git
synced 2026-08-11 19:26:56 +00:00
docs(stack-activity): wrap troubleshooting entries in Accordion blocks
Match the foldable troubleshooting pattern established by docs/features/deploy-progress.mdx so the page stays compact and readers can scan to their issue. This is the canonical formatting for the /features section's troubleshooting blurbs going forward.
This commit is contained in:
@@ -63,10 +63,10 @@ Sencho attributes every recorded event to the user who was authenticated when th
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### The Activity tab shows "No activity recorded yet"
|
||||
|
||||
<Accordion title="The Activity tab shows 'No activity recorded yet'">
|
||||
The activity log is populated by operations performed through Sencho on this stack: deploys, restarts, starts, stops, and image updates. Trigger one of those actions and the entry appears within a few seconds.
|
||||
</Accordion>
|
||||
|
||||
### Operational events don't appear in the bell notification dropdown
|
||||
|
||||
<Accordion title="Operational events don't appear in the bell notification dropdown">
|
||||
The notification dropdown surfaces system alerts and error-level events. User-initiated operational events (start, stop, restart, deploy, update) appear exclusively in the per-stack Activity tab, keeping the global tray focused on conditions that need your attention.
|
||||
</Accordion>
|
||||
|
||||
Reference in New Issue
Block a user