search

openSUSE / mentoring

The openSUSE Developer Mentoring Program
http://101.opensuse.org
60 stars 49 forks source link

Refresh Uyuni website and improve accessibility and responsiveness #205

Open deneb-alpha opened 9 months ago

deneb-alpha commented 9 months ago

Project Title: Refresh Uyuni website and improve accessibility and responsiveness

Description: The current Uyuni website (https://www.uyuni-project.org/) is not completely responsive and it has some accessibility issues. We like to keep it simple from a coding point of view, but for making sure that no-one from our community will be excluded or will have a bad user experience, we would like to refresh the website.

One crucial aspect of this refresh is that we don't want to introduce fancy js dependencies or using any over complicated framework.

The new website should provide static pages, mainly HTML. This requirement is important/mandatory because it makes easier to adapt it when there's a new Uyuni release or when we need to add more information on the existing pages.

The source code is hosted at GitHub and we use GitHub automated deployment of new pages.

Deliverable:

Mentor:

Skills: HTML, CSS are the basic requirements

Skill Level: Easy

Prjoct Size: Small Sized Project (90 hours)

Get started:

2001Navneet commented 9 months ago

Hello @deneb-alpha , I want to work on this project as I am well aware of HTML,CSS3,Javascript, Tailwind and React js,could you assing this project to me.

2001Navneet commented 9 months ago

Please let me know that Refreshing the website means that I have to build it from scratch for desktop and mobile version? OR I have to make the website responsive from the existing desktop version?

deneb-alpha commented 9 months ago

@2001Navneet as per requirements, we don't want to redo everything.

The website already provides some static pages with the info we need for our users and community.

What we want to see improved is its accessibility and of course, we would like to also make sure that the website is responsive.

As specified, we don't want to have any fancy framework in place. The website is built with GitHub pages and we like how easy it is to update it with new content.

Considering all these information, what do you have in mind?

2001Navneet commented 9 months ago

Sure mam as per given requirements for the website I will surely give my best to improve its accessibility and make it responsive without using any CSS and Javascript based framework.

Rakielle commented 9 months ago

Hello @deneb-alpha and Raul.

I'm interested in this project. I've followed the steps mentioned above to get started. I've already forked and cloned the repository, and I've used the WAVE tool to identify potential issues. What should be the next steps?

deneb-alpha commented 9 months ago

Hello @deneb-alpha and Raul.

I'm interested in this project. I've followed the steps mentioned above to get started. I've already forked and cloned the repository, and I've used the WAVE tool to identify potential issues. What should be the next steps?

Hi @Rakielle Would you like to report the accessibility issues you found as new issues on https://github.com/uyuni-project/uyuni-project.github.io ?

And please, add also a link to this issue as a reference

Rakielle commented 9 months ago

WAVE identified several low-contrast errors. But I'm concerned about creating an issue for them because fixing it will involve creating new colour variables that'll pass WAVE. I don't want to create more issues in the process of fixing this. I'll skip the low-contrast errors and report other issues instead.

What do you think?

deneb-alpha commented 9 months ago

WAVE identified several low-contrast errors. But I'm concerned about creating an issue for them because fixing it will involve creating new color variables that'll pass WAVE. I don't want to create more issues in the process of fixing this. I'll skip the low-contrast errors and report other issues instead.

What do you think?

Feel free to report all of them. When working at the implementation we can always decide for a wontfix.

In your previous work on the UI I think you also adjusted some colours for matching accessibility requirements. We can do the same here too after evaluating what we want to do

Rakielle commented 8 months ago

Are we supposed to work on fixing the issues now or during GSoC?

DeTrOiT259 commented 8 months ago

Hello @deneb-alpha , I also want to work on this project and I've followed the steps mentioned above to get started. What should be my next step ?

0xmihirsahu commented 8 months ago

Hey @deneb-alpha , I'm excited to work on this issue. This aligns very well with my USP. I have followed the instructions mentioned above. How should I proceed?

aymansuhail commented 8 months ago

Hi @deneb-alpha ,

I've reviewed the project description and I'm excited about the opportunity to contribute to refreshing the Uyuni website. I understand the importance of ensuring responsiveness and addressing accessibility issues to enhance the user experience for the community.

I have experience with HTML and CSS, and I'm eager to work on this project following the guidelines provided. I've forked the repository and will start by using WAVE to identify and classify accessibility issues, as well as following the suggestions from W3Schools to improve responsiveness.

Looking forward to your guidance on the next steps!

Best regards, aymansuhail

Lokeshsri11 commented 8 months ago

hello @deneb-alpha , I am interested in working on this issue. Last time I had solved the accessibility related issue in openQA (openSUSE) https://github.com/os-autoinst/openQA/pull/5104

deneb-alpha commented 7 months ago

hello all,

given that some of you already reached out with PRs for fixing some of the accessibility issues, I would like to clarify better which are the expectations from this stage of the GSoC.

I'll also edit the initial description with those details

Rakielle commented 7 months ago

Hi @deneb-alpha

I noticed that the GSoC project is labeled as medium-sized, but in the description you wrote small-sized project.

Please, what's the correct size for the project?

deneb-alpha commented 7 months ago

Hi @deneb-alpha

Hi @Rakielle

I noticed that the GSoC project is labeled as medium-sized, but in the description you wrote small-sized project.

Please, what's the correct size for the project?

This project is a small size.

@ddemaio could you please adjust the label?

shivkr6 commented 7 months ago

Hi @deneb-alpha I'm an undergrad student majoring in Computer Science. I stumbled upon https://github.com/openSUSE/mentoring/issues/205 this GSoC project and found it pretty interesting. I have some knowledge of HTML and CSS.

My previous experiences have been in systems programming with Rust and C so I think I would be a good fit for this project because systems programming focuses more on simplicity and we do most of the work from scratch, which I think you want in this project.

Can I go ahead and start working on making the GSoC proposal? Also what is your preferred mode of communication?

Sincerely, Shivang K Raghuvanshi

Sachiya2000 commented 7 months ago

i am interested this project

Rakielle commented 7 months ago

@deneb-alpha Hi Marina, I hope you're doing fine.

Please can you help review and provide feedback on my proposal draft?

I sent a copy to your email. I'll be looking forward to your response.

Thank you.

adritek commented 5 months ago

I made a gist for a bug template
Revisions welcome.

adritek commented 5 months ago

Hello @deneb-alpha I've only just noticed that all the issues I've created are under: https://github.com/openSUSE/mentoring/issues and should have been filed under: https://github.com/uyuni-project/uyuni-project.github.io/issues

I'm unsure who to contact to transfer these issues to their proper repo. Apologies, and future issues will be raised in uyuni-project.github.io/issues ✅

deneb-alpha commented 4 months ago

Hello @deneb-alpha I've only just noticed that all the issues I've created are under: https://github.com/openSUSE/mentoring/issues and should have been filed under: https://github.com/uyuni-project/uyuni-project.github.io/issues

I'm unsure who to contact to transfer these issues to their proper repo. Apologies, and future issues will be raised in uyuni-project.github.io/issues ✅

Hi @adritek, I'm reopening the issues in the right organization and repo. Please, notice that this project has been already assigned. If you are still interested to contribute to Uyuni, please, stay in touch and join us on gitter. :)