Skip to content

Unify and fix design across starters, tutorial, 404 page, etc #5383

Open
0 of 1 issue completed
Open

Description

@sodic

@infomiho and @cprecioso recently did a redesign of our starters, our tutorial, the 404 page and possibly something else. It's much nicer than before but still not final as in "There's nothing more to improve and fix here." I'll list some of the things.

Both tutorial and starers:

  • Mixing of styles (e.g., rounded edges and smooth fonts + neobrutalism). I don't know the correct technical terms but it seems off.
  • Unaligned text on elements (attaching an image as an example)
  • Not quite on brand - the style is similar to our landing page and docs but distinctly different, and this will change even more once the designer is done (I'm passing on this issue to him).
  • Dark theme missing - This is arguably a separate issue but since we're already doing a redesign, I think now is the time

Starters:

  • Component styles that are "too agressive" for the starter. IMO the splash screen should be fully wasp branded, the rest of the app should have a more neutral design that people can reasonably use in their apps.
  • The UI on the basic starter splash screen is too jumpy which makes it difficult to read. Something is off about the letters and the text too (I think they're too big which makes the entire thing clunky to read, not sure)
image

Activity

  1. changed the title [-]Have the designer review starters, tutorial, 404 page, etc[/-] [+]Unify design across starters, tutorial, 404 page, etc[/+] on Nov 19, 2026
  2. changed the title [-]Unify design across starters, tutorial, 404 page, etc[/-] [+]Unify and fix design across starters, tutorial, 404 page, etc[/+] on Nov 19, 2026
  3. deleted a comment from wasp-bot on Nov 20, 2026
  4. deleted a comment from wasp-bot on Nov 20, 2026
  5. Martinsos commented on Nov 20, 2026

    @Martinsos
    Member

    @wasp-bot please give this one some consideration, how would you go about it?

  6. wasp-bot commented on Nov 20, 2026

    @wasp-bot
    Collaborator

    I'd make the welcome screen unmistakably Wasp and keep the app you inherit deliberately neutral. The brandbook gives us a starting point, but I'd get a designer thumbs-up on one light/dark pair (welcome + a task form) before rolling it out everywhere.

    1. Fix the jumpiness first. Make the basic starter walkthrough a static numbered list with examples in place. No need to settle the palette to stop the page from moving while you read it.
    2. Roll out the approved look in a second pass. Keep the same type, spacing, and control sizing across starters and tutorial, with Wasp accents on the welcome screen. Follow system light/dark with a few plain CSS variables, and update the tutorial snippet, patch, examples, and screenshots together. Use the closed Unify starter and tutorial design with system dark mode #5440 as a prototype, not a patch to land wholesale: keep existing Auth UI defaults intact, and check field contrast and keyboard focus in both themes.
    3. Confirm which 404 we mean. Unify starter and tutorial design with system dark mode #5440 styled the dev server's wrong-port screen, which is a 200 at /, not a 404. I'd keep error-page styling separate from routing changes.

    agent session

  7. Martinsos commented on Nov 20, 2026

    @Martinsos
    Member

    @wasp-bot ok, give it a try with a PR!

  8. wasp-bot commented on Nov 20, 2026

    @wasp-bot
    Collaborator

    First pass is up in #5442. All five steps stay put, with examples beside them on desktop and below them on mobile. No more hopscotch. The PR closes #5441 so this issue stays open for the design pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationexampleExample app

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions