Step 1
Landing page sets up the free check, first fix, and monitoring path.
Step 2
Website setup is centered with one filled field and one follow-up field.
Step 3
Alerts and audit are single-focus screens with no outer wrapper card.
Scope
The artifact covers homepage, signup, message, onboarding, and mobile.
Full Journey Context
Latest Changes
- Homepage now explains the journey before signup: run a free check, see a first fix, then keep it watched.
- Onboarding hides the app sidebar and mobile app nav so the user stays focused on setup.
- Step one removes the inner heading and uses expectation copy in the main subtitle.
- Step two changes the headline to Where do you talk? and removes optional/box copy.
- Step three removes the inner title and adds the shared SiteFavicon component to each site row.
- The alert-routing selector still appears only when both Slack and Telegram are connected.
Step 1
The old setup had multiple explanatory layers and app navigation competing for attention. The current screen keeps one headline, one expectation-setting sentence, the entered site, and one progressive blank field.
Old
Revised
Step 2
The revised alert step removes the duplicated heading, explanatory paragraph, and outer wrapper. The two connection choices are the visual focus, with Skip and Continue directly underneath.
Old
Revised
Step 3
The final step no longer repeats that the site is ready. The site row carries identity, starts with the shared favicon treatment, and leaves Run audit as the primary action.
Old
Revised
Mobile Check
Capture Limits
- Login, site creation, chat status, schedule save, and audit trigger calls use a disposable local mock.
- No production data, live Slack/Telegram OAuth, billing, or database operations were used.
- The favicon uses the app's shared favicon component and its normal fallback behavior.