Preparation for website mainatanance

[AceTheCreator]

It's really important to have a website that's easy to use and keeps everybody informed for the upcoming conference. That's why we need to make sure our website is dynamic and user-friendly. The website is the main place where attendees, speakers, sponsors, and media people will go to get all the information they need about the event, register, and stay updated with the latest news. Here are some things we need to do to keep the website in good shape:

• We need to add a cool and reusable theme to the website so it looks great and is easy to navigate.
• We also need to introduce a simple and user-friendly speaker registration form that's connected to Google Forms for easy data storage.
• It would be helpful to create a general FAQ page to answer any questions that attendees, speakers, and sponsors might have.
• We should improve the current lighthouse score of the website by 40%, so it loads quickly and efficiently for everyone.
• We need to make sure the Sponsorship Prospectus file button is downloadable from the website so sponsors can easily access it.
• Introduce some UI testing framework to the website
• Finally, we need to improve the current agenda and speakers components, so everybody knows what's happening and who's speaking at the conference.

[Gmin2]

Hey @AceTheCreator ig we should create child issues for this ,

[AceTheCreator]

Hey @utnim2 it's a GSoC proposed idea :)

[RamGoel]

Hey @AceTheCreator this can be added in https://github.com/postman-open-technologies/gsoc-2024?tab=readme-ov-file#project-ideas as well.

[IAmRiteshKoushik]

Hey @AceTheCreator , I would like to work on this as part of Google Summer of Code 2024. I have written down a detailed introduction over at AsyncAPI: Conference Website Maintainance. Awaiting your response and feedback regarding the same.

Ritesh Koushik

[cybraia]

Hello @AceTheCreator
I am Krishna. I came across the idea and it sounds interesting to me. I am a frontend web developer (I can make dynamic and user friendly websites) and work well with APIs as well. I will go through the codebase. Let me know who are mentors for this idea so I can keep in touch and if there's any other communication channel apart from github.

[shauryag2002]

Hi @AceTheCreator @Mayaleeeee ,
I have a question regarding integrating a simple and user-friendly speaker registration form. The form is currently hosted on the apiday website with a link like this: https://apidays.typeform.com/to/ILJeAaV8?typeform-source=www.apidays.global#event_name=xxxxx. Since it's from another website, how can we connect it to Google Forms for easy data storage?

[ashmit-coder]

Hello @AceTheCreator and @Mayaleeeee.
I am Ashmit Jagtap, I have contributed to AsyncApi this year and look forward to takle this issue in GSOC.

I would like to ask if there are any qualification tasks/pre-requesists that we need to fullfill, as this issue seems to be recently added as a part of GSOC.

[Kavisha4]

Hey @AceTheCreator and @Mayaleeeee
I am Kavisha Mathur. I have reviewed the codebase and documentation related to this issue, and would love to work on it. I am well versed with basic Front End Development, have worked with CI/CD and APIs in detail.
Please find my detailed introduction on:Link to Introduction on AsyncAPI: Conference Website Maintainance #24
Would want to know if there is a qualification test for the same.

[ashmit-coder]

Hey @AceTheCreator and @Mayaleeeee I had a doubt regarding the PR's that are coming under this project.
Aren't we supposed to start generating PR's for GSOC assigned issues after the porposal's have been submitted and candidate for the task has been selected?

That is the trend I saw in various other Repo's so wanted it to be calrified. :)

[hichemfantar]

@AceTheCreator I have experience building event websites with great UI/UX.
My latest work https://github.com/hichemfantar/TSYP-11-Official-Website
I'd be happy to work on this project as part of GSOC!

[ashmit-coder]

Hello, @AceTheCreator , @thulieblack , @Mayaleeeee. First of all thank you for selecting me for GSOC 2024 for Website Maintainance Project.

Below is the proposed schedule according to me.

Week 1 - 2:

• Solving existing issues/bugs.
• Develop a UI around a brainstormed theme and develop the wireframes for that.
• Discussions regarding the testing framework and which one to adopt.

Week 2 - 3:

• Implement the speaker registration form.
• Connect it to Google Forms API for better storage and retrieval of the data.
• Evaluate the form and designs produced till the time.

Week 3 - 4:

• Create the FAQ page.
• Research for ways to improve the lighthouse score and discuss with mentors on the possible solutions.

Week 5 - 6:

• Improve the current agenda and speakers component of the website, to make changes to them easier, as the scale of increases overtime.

Week 7 - 8:

• Improve the sponsor prospectus download button.
• Review the designs, UI and the website at the point of time, to optimise the site in coming weeks.

Week 9 - 10:

• Implement the testing framework chosen so that it is easier to maintain the repository and help with making contributions easier and safer.
• Improve the lighthouse score of the website and implement the solutions developed during the discussion period.

Week 11 - 12:

• Wrap up the project and clear any backlog issues.
• Create maintainable and descriptive in-code docs, for ease of contribution to upcoming contributors.
• Generate a final report for GSOC, get the work reviewed by the mentors and submit the report.

As of now I have my examinations in my University so I would create a new Issue with all this tasks after 12th May.
This way keeping track will be easier for me as well as for the community.

If there any feedback/ extensions I am happy to hear.

[thulieblack]

Hey @ashmit-coder thanks so much for this, I think it's best to create a separate issue/ doc for progress tracking etc