Values sidebar - scroll position marker #31

aaaaargZombies commented 2021年11月01日 17:27:01 +01:00

I liked having an indicator as to where you are on the values. I felt like it helped explain the function of the sidebar, letting you know how far you were through a potentially dense list of political stuff and encouraged people to click on the bit they were most concerned about. I also enjoyed adding some bells and whistles with a bit of JS.

I think this is a potential point of contention that we should explore as a team. I know Sam has previously expressed an interest in reducing as much as possible the amount of JS on websites. I'm wary of adopting an austere aproach to development and JS has really been my focus for a while so I obviously come from a different veiw point. I think Luke said they have mostlty been working in React of late and Noah listed modern JS stack as one of many areas they hoped the co-op could provide oportunity for professional development in.

I'm not sure it's the best testcase of where we stand on using JS but let's explore both how people feel about including this and the wider topic.

I liked having an indicator as to where you are on the values. I felt like it helped explain the function of the sidebar, letting you know how far you were through a potentially dense list of political stuff and encouraged people to click on the bit they were most concerned about. I also enjoyed adding some bells and whistles with a bit of JS. I think this is a potential point of contention that we should explore as a team. I know Sam has previously expressed an interest in reducing as much as possible the amount of JS on websites. I'm wary of adopting an austere aproach to development and JS has really been my focus for a while so I obviously come from a different veiw point. I think Luke said they have mostlty been working in React of late and Noah listed modern JS stack as one of many areas they hoped the co-op could provide oportunity for professional development in. I'm not sure it's the best testcase of where we stand on using JS but let's explore both how people feel about including this and the wider topic.

aaaaargZombies commented 2021年11月01日 17:32:30 +01:00

No description provided.

SamWhited commented 2021年11月02日 01:30:00 +01:00

I feel that we should not use any JavaScript on the site.

If you're building a web application it's an unfortunate reality that JavaScript will be required (though hopefully webassembly can change that in the future), however, for a small brochure site it feels like unnecessary complexity and something that is likely to cause a bad user experience when it goes wrong or when the user is on a slow connection and have to download more stuff.

A tiny bit of JavaScript to do things that gracefully fallback when JavaScript is disabled may not be the end of the world, but if the functionality isn't needed I believe it should be left out.

I feel that we should not use any JavaScript on the site. If you're building a web application it's an unfortunate reality that JavaScript will be required (though hopefully webassembly can change that in the future), however, for a small brochure site it feels like unnecessary complexity and something that is likely to cause a bad user experience when it goes wrong or when the user is on a slow connection and have to download more stuff. A tiny bit of JavaScript to do things that gracefully fallback when JavaScript is disabled may not be the end of the world, but if the functionality isn't needed I believe it should be left out.