Open ryyppy opened 4 years ago
Quick prototype based on: https://github.com/OneGraph/onegraph-meetup-plugin
Live preview: https://cem2ran.github.io/reasonml-events
Are there any design guidelines/system I should follow to tweak the styling or is it good enough as is?
I'm using the following logic to filter some of the events because the result from Meetup.com appears to also include events that don't have any ReasonML 🤷♂️ https://github.com/cem2ran/reasonml-events/blob/af3b6ea31ef204db0b8a2185adbc3361c02bffae/demo/src/index.js#L10-L15
Are there any design guidelines/system I should follow to tweak the styling or is it good enough as is?
For now it's enough to keep it simple with the styling and we will let @bettistein have a look at it for a proper design mockup.
The rest sounds fine, how would one manage the API keys though?
Right now it is setup as a persisted query so you call an endpoint that can only do one thing (query ReasonML meetups). TTL is set to 1 hour, which means that meetup.com is only hit at most 24 times a day, otherwise served from cache. Currently it's authenticated with my own personal meetup & onegraph account, but we can create one for ReasonAssoc, if needed. I'll try to get some feedback from Sean (onegraph) on this, but I believe this is the recommended approach.
This could be a standalone component mounted in the
pages/community/events.mdx
page.\cc @cem2ran