docs(features): wrap troubleshooting accordions in AccordionGroup

Wraps the loose <Accordion> blocks in editor.mdx and stack-activity.mdx
in a single <AccordionGroup> to match the troubleshooting design used
by fleet-federation.mdx. Structural only; no content changes.
This commit is contained in:
SaelixCode
2026-05-07 16:36:53 -04:00
parent bd25458a26
commit 8ad5bb2e39
2 changed files with 31 additions and 34 deletions
+8 -7
View File
@@ -63,10 +63,11 @@ Sencho attributes every recorded event to the user who was authenticated when th
## Troubleshooting
<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>
<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>
<AccordionGroup>
<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>
<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>
</AccordionGroup>