Contributor opportunities section

[tim-schilling]

The Django community (and Djangonaut Space stars) are in need of identifying what opportunities exist for contributing. We should add a section to the site that allows people to register community volunteering opportunities and for others to view them.

• Registering an opportunity
  • User needs a confirmed email address
  • Title
  • Short description (2 or 3 sentences)
  • Contact method
  • [optional] Categories or tags for types of opportunities (coding, meetups, conference, community, writing, speaking, etc)
  • [optional] Skills you'll develop contributing
  • These need to be approved by a staff user (just do this through the admin)
  • Need to email staff users that an opportunity was registered and needs reviewing
• Viewing opportunities
  • Maybe require confirmed email before viewing contact methods?
  • Be able to filter on tags
  • Be able to search on title and description

[FarhanAliRaza]

i would like to work on this

[tim-schilling]

@FarhanAliRaza sounds good. How do you want to approach it?

[FarhanAliRaza]

I like to create models first in my Django projects.
We create a model first and then go from there.

Should we create separate PRs for every change, like first models, then views, and ui, or one big PR? If we separate PRs, we can create separate issues for every change.

[tim-schilling]

Can I suggest doing a rough mockup first of the views? That way there should be fewer changes needed to the models as we go. And we would be in alignment on where things are going to end up.

[FarhanAliRaza]

Do you mean mockup like this in figma. https://www.figma.com/design/ShHML9qwofVk9Qxjqxj6tB/Opprtunies-page-djangonaut-space?node-id=0-1&t=1zMSYlD2vdEyboSL-1
I am not good at figma as aparent by the design 🥲
@tim-schilling

[tim-schilling]

I'm surprised you didn't try to use Claude/ChatGPT to generate mockups! 😁 This is exactly what I was hoping for, it helps us communicate around what's actually being built. Thank you!

Some adjustments:

• I think ideally the list view would be a grid. That's really only important at this stage in regards to keeping in mind that we're not going to have a ton of information present to start.
• We should have a link that takes people to the page where interested folk can learn more. This needs to exist on the form too.
• We likely want to have the skills and tags be a controlled set of options. Though I could be convinced otherwise. What do you think?

[FarhanAliRaza]

I'm surprised you didn't try to use Claude/ChatGPT to generate mockups! 😁

I was looking for an excuse to use Figma. I have wanted to use it for a long time. :) But now I think I will use ChatGPT.

I think ideally, the list view would be a grid. That's really only important at this stage in regards to keeping in mind that we're not > going to have a ton of information present to start.

ok

We should have a link that takes people to the page where interested folk can learn more. This needs to exist on the form, too.

👍

We likely want the skills and tags to be a controlled set of options, though I could be convinced otherwise. What do you think?

They are a select option in this mockup too. My design was not good enough to convey this 😂... this was a work in progress, I finalized it when I posted, and then started to make changes that were unfinished when you looked, I think.

[tim-schilling]

All good! Thanks for putting effort into this.

[FarhanAliRaza]

https://www.figma.com/design/ShHML9qwofVk9Qxjqxj6tB/Opprtunies-page-djangonaut-space?node-id=0-1&t=mClMz2hh5fvDhGQG-1

I have updated the design

On the page section might look the same, but just the grid part, this will be the detail page for opportunities.

There are some things that are not clear here.

As you have mentioned, user need to verify their email to view the contact method. When a user is not logged in, the contact method should be disabled, and on hover, it should show Verify your email to view or the button title can be that too.

When the user clicks on the the contact method button, if he is verified, we can redirect him according to the contact method. However, we have not yet defined whether the contact method is a text box or an option. If it is an option, we will have to add a textbox for details.

[tim-schilling]

As you have mentioned, user need to verify their email to view the contact method. When a user is not logged in, the contact method should be disabled, and on hover, it should show Verify your email to view or the button title can be that too.

❤️

When the user clicks on the the contact method button, if he is verified, we can redirect him according to the contact method. However, we have not yet defined whether the contact method is a text box or an option. If it is an option, we will have to add a textbox for details.

Hmm. What do you think of having it as a text input where we ask for a URL for the user? That way we can just render the <a> tag similar to how you did the video link?