3 ms·

I think I would appreciate it in both places! One more piece of drive by advice: I would reduce the font-weight of the hero text on the front page ("Meetsy take

I think I would appreciate it in both places! One more piece of drive by advice: I would reduce the font-weight of the hero text on the front page ("Meetsy takes two calendars..."). Unnecessarily bold text is a common pet peeve of mine. Can I ask if you're trying to monetize this service anywhere? If not, would you mind making it a bit more clear how to run it on the Github page (e.g. with a compose.yml)?

robertwt7 4y ago
> I would reduce the font-weight of the hero text on the front page ("Meetsy takes two calendars..."). Unnecessarily bold text is a common pet peeve of mine. No worries, i'll take this into account tonight as well. I will also update with a screenshot, do you think a screenshot of the invitee's page where they can accept the invite would be good enough? I actually have a video I made (not professionally, just a screen recording) to show google for the OAuth spec but I have to make it better. > Can I ask if you're trying to monetize this service anywhere? If not, would you mind making it a bit more clear how to run it on the Github page (e.g. with a compose.yml)? At the moment I'm not trying to monetize it as it is just for fun side project, but if it gain a lot of traction probably I will just to cover the server cost. Either way it will always be open source and you can self host. compose.yml exist in the api/ folder (this is how i deploy it), front end was deployed with vercel so don't need any of that.