Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event Submission Issue #2

Open
Tanwir7 opened this issue Jun 5, 2019 · 3 comments
Open

Event Submission Issue #2

Tanwir7 opened this issue Jun 5, 2019 · 3 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Tanwir7
Copy link

Tanwir7 commented Jun 5, 2019

Creating a Form thats includes:

  1. Name of the Event
  2. Location of the Event
  3. Date
  4. Description
  5. Name of Organizer
  6. Contact Number
  7. Email
  8. Category of event
@Tanwir7 Tanwir7 closed this as completed Jun 5, 2019
@Tanwir7 Tanwir7 reopened this Jun 5, 2019
@mihok
Copy link
Member

mihok commented Jun 6, 2019

This is really great! I would love to add a couple insights if possible.

Motivation

First, the motivation here is we want to make planning ahead for organizers easier to do. Often times the challenge with running events is that you can really only operate at a month ahead of now, sometimes its even less, like a week or two ahead of now. As you might imagine operating like this over time causes friction with other forces and so by providing a way for Event Hosts to enter in their event(s) (With an emphasis on (s).) Maybe we can push back that operating behavior. Maybe this will enable them to plan 3 events ahead.

Component Breakdown

All that being said, lets start small and evolve the event submission section of speakfriend. The data intended to be collected mentioned above seems great to me! It makes me think we may need several components made. Specifically,

  • An input component that takes a validation function, or a validation regex that we can use for several items listed above

  • A date component, with the motivation blurb above as context, this might mean more than just a date drop down in the future. Lets start simple though and just layer on top of the generic input component with a placeholder. Or maybe this could be a textarea component? Up for discussion!

  • A tag component, for the category of event input, something like the image below is what I had in mind, but definitely up for discussion too

  • A base component for the form itself, that will use the above components in it, as well as handling the submission, and error feedback parts of the form

My thoughts on next steps is to create issues for each component listed above (and any others that I am forgetting) so folks can pick individual parts up themselves

@mihok mihok added good first issue Good for newcomers help wanted Extra attention is needed labels Jun 6, 2019
@PradhumnaPancholi
Copy link
Contributor

I can take this one.

@PradhumnaPancholi
Copy link
Contributor

I can start with a simple drop-down for the date as of now. But, we can try to work on functionalities like indicating booked dates and handling multiple events on the same day but different times( if we want that), or maybe providing time slots.

Let me know your thoughts about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants