Design brand-native loading, empty, success and error states #209

Goal

Make system states feel like part of Sea Saba rather than generic application UI.

Audit

Identify the major states visitors can encounter, including:

• availability loading
• no availability
• booking/request failures
• contact form success/error
• image/content loading
• 404/not-found
• empty search/filter results
• temporary service errors

Direction

Use Sea Saba's existing visual language and the bubble-loader work where appropriate, without overusing branded animation.

Acceptance criteria

• Major async states are inventoried
• Loading states avoid layout jumps
• Empty states explain the next useful action
• Errors are clear, actionable and nontechnical
• Success states provide unmistakable confirmation
• 404 page feels intentional and useful
• Reduced-motion is supported where animation is used