~thomasorus

France

https://thomasorus.com

Recent activity

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Thomasorus to ~sircmpwn/sr.ht-discuss

Hey folks,

When I created this mailing list, I was hoping that Sourcehut would be a place 
where I can contribute with my knowledge and experience about accessibility
and inclusive design, and have a positive impact for its users. 

I knew it would take time and patience, because devs communities are not used
to these topics, but I was ready for it. And since Drew committed to accessibility 
in a previous blog post, I was confident we would be able to work together, in 
incremental steps, to make Sourcehut better.

So Drew, you can imagine that seeing you cherry pick and bend to your 
own tastes or "good sense" accessibility standards and inclusive design rules ;
while boasting about your professional experience in order to get away with

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Thomasorus to ~sircmpwn/sr.ht-discuss

> I hope this dark theme is not ended up being used.  
> Its contrast is way too poor (2~2.5) to be considered accessible.

This is a technical test, not a design proposal. It won't
be used in production.

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Thomasorus to ~sircmpwn/sr.ht-discuss

Hey folks,

> It’s quite a good recreation of the original design. I’m not a fan of
> the large variation, it’s less efficient and readable than the original
> spacing.

I actually find the larger version way more readable, but way less
balanced from a design standpoint. It doesn't feel like good design but
things are less cluttered, which allows for an easier scan (see below).

> While we are discussing the matter: what about font preferences? I think
> that setting the font-family to sans-serif and monospace would lead to a
> random direction but may allow better accessibility for dyslexic persons
> for example. Or even allow people to set the programming font they are

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Thomasorus to ~sircmpwn/sr.ht-discuss

Hello everyone, thanks for your patience. 

I've spent a few evenings recreating sourcehut 
git repository page using the CUBE CSS
methodology. This is a technical demo and not
a design proposal. To get a better understanding, 
please read the CUBE website before
reading the SCSS files (starting with index).

You can see the code here:
https://git.sr.ht/~thomasorus/sourcehut-cubed

In the README, you will find links to different versions
I created. What I am particularly happy about is how

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Thomasorus to ~sircmpwn/sr.ht-discuss

> Can you start by preparing a patch for antiweb
> (or maybe even in a separate tree) which 
> demonstrates some of the basics of your preferred 
> approach? Then we can start from more robust
> foundations.

No problem, I'll try preparing something during the
holiday season. Might reproduce a page from
sourcehut to show how the code is organized so
everyone can get a better idea.

I'll give you an update in this mailing list once it's
done.

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Thomasorus to ~sircmpwn/sr.ht-discuss

> How so?
> I am open to suggestions, yes.

Just by looking quickly I think there are some ways in 
how you approached it that can be detrimental to the 
project long term:

- Heavy use of sass variables to the point where it's 
sometimes hard to read when you're new. Sass is still 
important and useful but I've seen a lof of sass codebases 
that could only be understood by their creators because
 of vars, extends, custom functions, etc. I recommend a 
more lean approach so newcomers can join in.

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Thomasorus to ~sircmpwn/sr.ht-discuss

Hey folks, sorry for the duplicate thread, I'm still learning.
Reposting my answers from the other thread + new ones.

> I have no idea if that bootstrap can shine without JavaScript,
> but I hope that sourcehut remains JavaScript free.

Bootstrap is normally used with jquery/JavaScript but it seems it
was removed by Drew when making Sourcehut. My proposal 
isn't to change how sourcehut works, but to give it a coat of 
paint.

> More polish on rough edges could be nice, but in general I 
> think it's in a good place.

Re: Improving Sourcehut design, accessibility and frontend code 9 months ago

From Thomasorus to ~sircmpwn/sr.ht-discuss

> I have no idea if that bootstrap can shine without JavaScript,
but I hope that sourcehut remains JavaScript free.

Bootstrap is normally used with jquery/JavaScript but it seems it
was removed by Drew when making Sourcehut. My proposal 
isn't to change how sourcehut works, but to give it a coat of 
paint.

> More polish on rough edges could be nice, but in general I 
think it's in a good place.

I feel the same. It's more about polishing and giving alternatives.
Also it could be a way to organize and really defined the visual
language of sourcehut for people who want to use it or