sugarlabs / www

The Sugar Labs web site
https://www.sugarlabs.org
GNU General Public License v3.0
71 stars 213 forks source link

Issue in the Mobile / small devices view. #399

Closed hs-07 closed 1 year ago

hs-07 commented 1 year ago

Problem:

Unavailability of Hamburger Icon in Navbar.

Issue:

When we open the website, we cannot navigate through any Navbar Hyperlinks as they cant be assessed due to unavailability of Hamburger Icon in the Navbar. (as displayed below in picture)

Screenshot_20230301_202223

Solution:

Enabling Hamburger Icon in Navbar and displaying all Hyperlinks appropriately.

My efforts:

~ Had setup the site in local environment. ~ Started working over the this issue.

I would request the mentors or the developers to assign the issue to me for more clarity that no one else is not working on the same. Thankyou.

chimosky commented 1 year ago

Thanks for pointing this out.

I would request the mentors or the developers to assign the issue to me for more clarity that no one else is not working on the same.

We don't assign issues in our community but feel free to open a PR when you can, anyone is welcome to work on any issue and we can test each and pick the better solution or combine commits.

quozl commented 1 year ago

I've tested and reproduce the behaviour of no menu provided on small displays. I've seen this before and didn't think it was a problem, because all the relevant links are at the bottom of the page, which is where a mobile user reaches once they have scrolled their small window over the content without tapping on anything.

A low priority issue.

I agree using a hamburger is an appropriate thing to do. However, the way it should be done is to make sure the content uses the existing feature, rather than adding any new coding. This is because our aim should be to provide content for the web site rather than spend any significant time working on the style and layout. Jekyll themes were chosen for this, and if they have been broken through ill-advised changes to the themes we should put them back the way they were, update them from upstream, or use a new theme. Long term this strategy of content first shall reduce wasted effort.

Would you like to get involved in the software that Sugar Labs actually produces, rather than looking at our web site? Look at Sugarizer, Sugar activities, Music Blocks, or Turtle Blocks.

Also,

I would request the mentors or the developers to assign the issue to me for more clarity that no one else is not working on the same.

This idea is a radical departure from our community norms. If more than one person working on a problem is not acceptable to you, then this is not the sort of community you should be contributing to. Please look at the various ways in which humans organise themselves to achieve their goals, and then evaluate our community again. Thanks!

hs-07 commented 1 year ago

@chimosky @quozl Thank you for your valuable advices. @quozl Sir, surely I would like to get involved with the software Sugar Labs produces, infact I am looking into them too, but thought to get familiar with base code of Sugar Labs website and understand the workflow.

quozl commented 1 year ago

Okay, thanks. That's an easy mistake to make. The workflow in this repository is quite different to the workflow of our software. Almost nothing is common between our web site and our software, except colours, and we've plans to change even that.