needs utility for doing Range[] - Range[] to calculate the available ranges.

each event type has a url like https://meet-me.deno.dev/my-name/event-name

With check of conflict

tasks:

• #39
• #38
• #37

Note: booking page has 2 types:

Type 1: URL https://meet-me.deno.dev/user-slug/

• It shows all available type
• The user first select the event type
• Then the user select a vacant slot from the calendar

Type 2: URL https://meet-me.deno.dev/user-slug/event-slug

• It shows the only one event type, which is already selected when the user visited the page
• The user select a vacant slot from the calendar

• Note1: if the user doesn't set the user slug, the booking page is not available.
• Note2: if the user doesn't set the event slug, then the booking page for the single event is still available via the url https://meet-me.deno.dev/user-slug/event-uuid

Path

• /mypage/onboarding

The user set up the url slug, availabilities, event types.

After setting up those parameters, they are navigated to my page (/mypage)

Tasks

• Set slug (user's url)
• Set availability
• Set timezone
  • Move Dropdown component from Deploy
• Set event type
  • Create a new Event Type Modal
    • Move Dialog component from Deploy
  • Delete event type
  • Edit Event Type modal

PATCH /api/user updates partial user data.

maybe overflow-y-scroll or overflow-y-auto instead of overflow-scroll ?

https://github.com/denoland/showcase_cal/blob/main/components/shared/TimeZoneSelect.tsx#L18

• Figma design https://www.figma.com/file/P0XsTDIeiwNhm8jFS03gwz/Deno-Cal?node-id=0%3A1
• Prototyped sign in flow #7
• Temporary Domain models #6

This time input is now text input. Want it to be selector (like calendly)

remove github action for deploy

For some reason, the google always ask authorization of API usages whenever the user tries to sign in.

Currently the oauth app is working in testing mode. It needs to be verified by Google to make it public (because this app uses sensitive permission scopes (like calendar.events calendar.read-only

• Describe how to use permission scopes
• Created demo youtube video
• Create Terms of service https://meet-me.deno.dev/terms
• Create Privacy policy https://meet-me.deno.dev/privacy

Now in rewiew

• Get review feedback

• Share progress on onboarding flow
• Discuss Inbox feature: Maybe drop it for first pass? (@ry says he doesn't need it for his use case)
• Plan this week's work

• How many pages do we need? (my proposal 4 pages: https://gist.github.com/kt3k/7ed815fc9210916d49e6ef5dea06bf87 )
• Do we need DB? (probably yes?) Which DB do we use?
• Which web framework do we use?

Feel free to add items.

• #40
• #41

design & implement session token expiration

which has:

• User slug settings
• Availability settings
• Time Zone settings

Copy to clipboard button

User Journeys

1. Acquisition Journey

   As a potential user of cal, I want to be able to view information about the solution to determine if I want to sign up for the product.

2. Signup Journey

   As an intended user of cal, I want to be able to signup for cal, using my Google Account for identification and authentication and linking my cal account to my Google Calendar. I also want to select some default configuration details about how I want cal to operate.

3. Cal Configuration Journey

   As an authenticated user, I want in interface to be able to configure my meeting slots as well as well as configure other options associated with my account.

4. Cal Visitor Journey

   As an unauthenticated user/visitor to a specific users page, I want to be presented with the available meetings slots for the user so I can book a meeting with them.

5. Cancellation Journey

   As an authenticated user, I want to be able to un-enroll in cal.

Infrastructure

• CI/CD (GitHub Actions)
• Frontend Tooling (Aleph.js)
• Business Logic/Middleware/Client API (Deploy Services)
• Persistance (Supabase)

Initial Work Break Down

• Infrastructure

  • Scaffold out CI/CD
  • Setup architectural decision records

• Frontend

  • Mocks/Designs for Landing, Sign-up, Configuration, Visitor/Booking pages
  • Scaffold out Aleph.js for "pages" (Landing, Sign-up, Configuration, Visitor/Booking)

• Middleware

  • Design domain model (event storm?)
  • Design process flow for sign-up
  • Design process flow for configuration
  • Design process flow for booking creation and change
  • Design and build mock APIs based on domain model and flows

• Integrations

  • Investigate and Detail OAuth integration with Google
  • Investigate and Detail Google Calendar Permissions and APIs
  • Investigate and Detail notifications via e-mail

• Backend

  • Investigate and Detail supabase integration
  • Design data model based on domain model
  • Implement data store design

Detect users' timezone somehow and set it to user object when first creating the user. (Currently in routes/api/authorize.ts)

• #40
• #41

like they do it in https://showcase-chat.deno.dev/