Hi it would be super helpful if I could see all inputs into the calendar so I can organise a number a of days for the holiday rather than being given pre defined dates. Is this possible?

People may use the invite link to get back to the social but will be presented with the name input again when they've already chosen one.

Looks like it provides additional validation and safety

This makes no sense on the home page and takes up valuable nav real estate.

Currently using browser Sentry but perhaps there's some benefits to following the docs for setting up specifically with Sveltekit? Looks like it makes use of hooks.

And check that it unifies the development experience, i.e. whether to use SvelteKit or Netlify CLI.

In first iteration Want to be able to edit:

• Background color
• Background effect
• Image
• Name

Second iteration:

• People emojis
• Other copy

The app is meant to avoid vertical scroll whilst always filling the available vertical height unless it genuinely needs to overflow.

The issue is that current CSS doesn't account for the URL bar on mobile browsers. There's a Chrome dev article somewhere that explains how to accommodate this.

Currently seeing a bad performance score due to poor first contentful paint.

Actually the datepicker does de-select the date internally but it doesn't update the classes of the initially selected dates so they appear to still be selected.

This page could be stripped down if we make it more dynamic.

The page could have accordions for different section that progress automatically but can be manually opened / closed too.

Stage 1 accordion - invite

At first this accordion is open and the others are closed (but you can see their names).

• "Invite people"
• share link button
• NEXT

Clicking NEXT closes the 1st accordion and opens the second.

Stage 2 accordion - wait for invitees

• "Waiting for others to join"
• Show invitees
• "Enable push notification (if you want)"
• push notifications switch
• NEXT

Enabling push notifications here is much more tempting because there's nothing to do but wait and the value proposition of them becomes very clear as it solves your current problem of just waiting.

Stage 3 accordion - choose a date

Once three people join this accordion opens and the others close.

• "Once you see everyone here, choose a date"
• best dates table
• DECIDE
• "This will notify others who have subscribed to push notifications"

Alternatively we could use actual pages instead of accordions for each stage as this would allow easy analytics of the journey / funnel. Page transitions could be used to make it look like the camera is going down one page at a time.

In some situations selected dates are moving to the day before when saved. This is to do with the way we are parsing values from the date picker which is (unexpectedly) timezone aware so can shift the date to the day before.

For now the design is to ignore timezones and simply collect dates so the fix is to ensure the day selected is what is captured by the backend.

And prevent double clicks. Might want to adopt a component library for this.

Should be able to take it from the environment. Might need to check old SvelteKit docs in GitHub.

Put back button back on the decision page and use a value in session storage to check if user has already visited that page, if they have then let them return.