Screenshot conventions

Desk and CLI screenshots live in docs/assets/images/.

Adding images

1. Save PNG or WebP files with descriptive names, e.g.:
2. desk-btu-configuration.png
3. desk-btu-task-form.png
4. desk-btu-task-schedule-cron.png
5. desk-btu-task-log-detail.png
6. desk-btu-run-later-list.png
7. cli-btu-py-config-show.png
8. Reference in markdown:

<figure class="btu-screenshot" markdown="span">
![BTU Configuration form](../assets/images/desk-btu-configuration.png)
<figcaption>BTU Configuration — ping scheduler and email defaults</figcaption>
</figure>

1. Run mkdocs serve locally to verify layout.

Priority pages for screenshots

Page	Suggested capture
Desk overview	BTU_Core workspace
BTU Configuration	Full form + ping button
BTU Task	Task form with function path
BTU Task Schedule	Cron + timezone fields
BTU Task Log	Log with stdout/stderr
BTU Run Later	List + document detail
Install scheduler	btu-py config show terminal

Share screenshots in chat or commit directly to docs/assets/images/ — either works.

Logo

Place Datahenge or BTU logo files in docs/assets/:

• logo.svg — header (light background); used when present
• favicon.png — browser tab icon (optional)

Until a BTU-specific mark exists, the Datahenge logo is fine. Update theme.logo in mkdocs.yml after adding files.