This page tracks the screenshots currently used by the J2 Tags documentation.
| Folder | Use |
|---|
src/assets/j2-tags-plugin/editor-tools/ | Shared editor UI such as Assignments, Quick Tags, Inspector, Tag Picker, context menus, Overlay, and Outliner. |
src/assets/j2-tags-plugin/pro/ | Pro workflows such as Tag Manager, Diagnostics, TagSets, Usage Database, imports, redirects, and unresolved tags. |
src/assets/j2-tags-plugin/behavior/ | Behavior System screenshots. |
src/assets/j2-tags-plugin/reference/ | Reference-only screenshots such as plugin settings. |
| Page | Screenshot |
|---|
| Assignments Panel | editor-tools/J2TagAssignmentsLite.png, editor-tools/J2TagAssignmentsPro.png |
| Assignments Panel Context Menus | editor-tools/AssignmentsTagContextMenu.png, editor-tools/AssignmentsObjectContextMenu.png |
| Tag Inspector | editor-tools/J2TagInspectorPinnedLite.png |
| Tag Picker | editor-tools/TagPicker.png |
| Viewport Overlay | editor-tools/J2TagOverlayPro.png |
| World Outliner | editor-tools/J2TagsOutlinerColumn.png |
| Quick Tag Settings | editor-tools/J2QuickTagSettings.png |
| Plugin Settings | reference/J2TagSettingsPro.png |
| Tag Manager | pro/J2TagManagerPro.png |
| Diagnostics | pro/J2TagDiagnosticsPro.png |
| Behavior Overview | behavior/J2TagBehaviorLibraryPro.png |
| TagSets | pro/J2TagSetAssetPro.png |
| Usage Tracking | pro/J2TagUsageDataBasePro.png |
| Import and Export | pro/ImportTags.png, pro/ReviewImport.png |
| Redirects | pro/ResolveRedirects.png |
| Undefined Tags | pro/ResolveTagsQuickTag.png, pro/ResolveTagsTagSet.png |
| Context Menus / Asset Tags | editor-tools/ContextMenu-J2Tags.png |
- Use Unreal Editor screenshots from the current plugin UI.
- Prefer the Lite screenshot for Lite pages and the Pro screenshot for Pro pages.
- Keep images readable at documentation width; add a second detail screenshot instead of over-cropping.
- Add
{ thumbnail="true" } to screenshot references so users can open larger images when needed.
- Do not rely on screenshots to explain core behavior; page text must stand on its own.
- Use ASCII filenames for new documentation references.
- Use
:::tip[Quick summary] when the customer needs a quick orientation before reading details.
- Use regular Markdown numbered lists for task flows unless a page is converted to MDX and imports Starlight’s
Steps component.
- Use Starlight’s
Tabs and TabItem components in .mdx files when the same concept has clear variants, such as Lite vs Pro or Simple vs Full mode.
- Use
:::note for prerequisites or restrictions, :::tip for optional guidance, :::caution for cleanup or overwrite risks, and :::danger only for high-impact destructive behavior.
- Use inline code for menu paths and bold text for buttons, menu items, and named UI controls.
