-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Sponsor and member contact link improvement #1561
Comments
Hi can I be assigned to this issue? |
@pandenaman007 consider yourself assigned - thank you. |
According to me we should place the "want to join" button at the starting of the webpage rather than at the end as the user would have to scroll all the way down in the same way as the Eclipse foundation page is designed. We can have two button placed side-by-side one of "want to join" and the other should be about the contact for the membership. These should be at the top of the page just like that of the page of The Eclipse Foundation. For the "want to sponsor" we can place that one at the end of the webpage. This can be the improvements over the current format. |
@pandenaman007 do you need any further feedback? |
No ma'am I think this is good according to me and also I checked the resources You mentioned in #1253 such as that of the Jakarta Package EE . I think this good approach for the contact linking UX design so that it gets the attention of more people. Thanks for your kind support. |
hi @pandenaman007 - I think this issue is not a "good first issue" because there are aspects of it that are still not defined, so requires more discussion. If you are okay with it, I would like your help on a better defined issue, (and I would tag you shortly on a different issue to assist with). Reading the request, I think there are some problems with the suggested workflow which I will outline after I first interpret what I think is being requested. This is a large feature request (that is not suitable as a good first issue), it can be broken down into several smaller pieces (each of which perhaps are good first issues). The current request is this:
Problems to consider: We have many web pages being discussed as part of this workflow:
Adding a flow diagram for a potential flow from the members page to other pages (and what those pages link off to): flowchart LR
A[Members page]
A --> C{Decision}
C -->|Learn More| D[How to Support Us page]-->|Contact us| B[Contact form page]
C -->|Contact Us| F[Contact form page]
C -->|Ready to Join| E[Membership Application page]
D -->|About Working Groups| G[About working groups page]
D -->|Sponsor Us| H[Sponsor Application form]
D -->|Join EF| I[Membership Application page]
D -->|Join Adoptium WG|J[Membership Application page]
|
Yes Ma'am I think this will require more level of understanding and experience for me to solve. Please assign me some other issue and I would be very happy to solve that issue. Again thanks a lot for your kind support. |
@pandenaman007 - if you can shift over to work on adoptium/aqa-tests#4199 that would be wonderful! |
@smlambert can take up this? |
Is your feature request related to a problem? Please describe.
We are trying to improve new members' and sponsors' experience and contact flow.
Having the same user experience as they can get from other Eclipse Foundation working group pages will be helpful.
Describe the solution you'd like
Instead of having https://adoptium.net/members/ a "want to join?" button has the same flow as this page https://www.eclipse.org/org/workinggroups/explore.php having 2: contact us about membership that will go to the same link https://adoptium.net/join/ and My organization is ready to join now https://membership.eclipse.org/application#sign-in .
And for Sponsor's page: https://adoptium.net/sponsors/ , want to sponsor? Change from the form link to the same links mentioned above.
Describe alternatives you've considered
a first step for sure is changing the "want to sponsor" to the same link as "want to join?" from the member page.
Then we could add the rest of the buttons and related links.
As part of the website improvements ideas: #1253
The text was updated successfully, but these errors were encountered: