Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Concrete.css

concrete.style

Post reply on HN
Print view View original

61–70 of 117 posts

Re: Concrete.css

#61

Post by kthartic »

louismerlin wrote: post #20
kmoser wrote: post #4

Not sure I would make the "disabled" buttons stand out more brightly than a regular button. In fact I would swap the colors of those buttons, or maybe make the disabled button greyed out.

I limited myself to black and white when creating the style-sheet, but maybe I should indeed add some kind of indicator for the "disabled" button, such as hatchings. edit: hatchings make the inner text unreadable, I'll play around with opacity and dotted lines, thank you to the users who proposed them. edit 2: went with dashed lines and published a new version. It even shaves off a couple of bytes off the minimized v…

Hmm I think the dashed lines still don't say to me "disabled" unless you told me. It looks more like a secondary button (eg "Go back" or "Cancel"). I really do think the use of reduced opacity would make sense here :)

Re: Concrete.css

#63

Post by xigoi »

Semaphor wrote: post #12
robador wrote: post #10

This doesn't look right with the dark reader extension in firefox. I would expect a website that's compatible with dark mode to work with dark reader (I.e. I would expect dark reader to not influence the CSS in that case)

That is sadly not the case. I disable dark reader for all sites supporting darkmode because it always changes them.

Are you using the dark mode detection feature?

Re: Concrete.css

#64

Post by nc0 »

As it is often said in various designer forums, please avoid pure white (#FFFFFF) on black (here #111111), as it makes the text glow for the human eyes (therefore making it unreadable for long text). Instead, try to lower a bit the contrast on the text color.

Also, the dispositions for the buttons at the beginning (GitHub, NPM, ...) are not adjusted correctly for keyboard navigation (each button requires two tabs).

Appart from that, I do like a minimalist stylesheet, so I will also recommend Tufte CSS [0] for readers.

[0]: https://github.com/edwardtufte/tufte-css

Re: Concrete.css

#65

Post by chiefalchemist »

jug wrote: post #50

Refreshingly simple, almost to the point of an aversion to other minimalist competitors like Milligram. I like it. As someone else said here, it brings my mind to an alternative web with browsers that had a better default and standardized stylesheet. Oh how I wish for this. Can't just Chrome, Firefox, Edge, Safari all just adopt this one? Setting up no-CSS sites would be a more sensible thing and we would have less n…

re: Project Gemini - Gemini in 100 words

Reading that reminds us how far we have *not* come. We were promised jetpacks, and instead we got the internet. A pro-distraction, privacy violating, social fabric tearing, power tool.

More Big Brother, less prophet / savior.

Re: Concrete.css

#66

Post by dvdkon »

nc0 wrote: post #64

As it is often said in various designer forums, please avoid pure white (#FFFFFF) on black (here #111111), as it makes the text glow for the human eyes (therefore making it unreadable for long text). Instead, try to lower a bit the contrast on the text color. Also, the dispositions for the buttons at the beginning (GitHub, NPM, ...) are not adjusted correctly for keyboard navigation (each button requires two tabs). A…

This really depends on the user's display and the viewing conditions. Someone with a TN LCD or even an OLED in bright light would likely prefer the "high contrast" #FFF on #000.

Re: Concrete.css

#67

Post by icar »

dvdkon wrote: post #66
nc0 wrote: post #64

As it is often said in various designer forums, please avoid pure white (#FFFFFF) on black (here #111111), as it makes the text glow for the human eyes (therefore making it unreadable for long text). Instead, try to lower a bit the contrast on the text color. Also, the dispositions for the buttons at the beginning (GitHub, NPM, ...) are not adjusted correctly for keyboard navigation (each button requires two tabs). A…

This really depends on the user's display and the viewing conditions. Someone with a TN LCD or even an OLED in bright light would likely prefer the "high contrast" #FFF on #000.

[dead]

Re: Concrete.css

#68

Post by AeroNotix »

chiefalchemist wrote: post #65
jug wrote: post #50

Refreshingly simple, almost to the point of an aversion to other minimalist competitors like Milligram. I like it. As someone else said here, it brings my mind to an alternative web with browsers that had a better default and standardized stylesheet. Oh how I wish for this. Can't just Chrome, Firefox, Edge, Safari all just adopt this one? Setting up no-CSS sites would be a more sensible thing and we would have less n…

re: Project Gemini - Gemini in 100 words Reading that reminds us how far we have *not* come. We were promised jetpacks, and instead we got the internet. A pro-distraction, privacy violating, social fabric tearing, power tool. More Big Brother, less prophet / savior.

My honest hot take is that we made computers too easy to use.

I appreciate how liberating computers and the internet can be for a lot of people but it has been far too easy to implement dark control through them.

Re: Concrete.css

#70

Post by yreg »

krsdcbl wrote: post #45
louismerlin wrote: post #20

Earlier quoted context omitted.

I limited myself to black and white when creating the style-sheet, but maybe I should indeed add some kind of indicator for the "disabled" button, such as hatchings. edit: hatchings make the inner text unreadable, I'll play around with opacity and dotted lines, thank you to the users who proposed them. edit 2: went with dashed lines and published a new version. It even shaves off a couple of bytes off the minimized v…

this could be a rare but very practical usecase for strike-through text

Wow, I love that!
Post reply on HN