See #18 (comment).

I've made some progress on generating screenshots automatically:

[see second comment]

It uses PhantomJS (which is in Debian). Call it like this:

$ phantomjs --ssl-protocol=any --web-security=false --ignore-ssl-errors=true screenshot.js \
http://www.github.com/alphapapa/solarized-everything-css \
test.png \
../css/solarized-dark/solarized-dark-github.css

Issues that remain:

1. We may need a way to specify a URL other than the domain's front page. For example, the GitHub front page probably isn't what we'd want to display.
2. Since so many sites are forcing HTTPS now, TLS/SSL errors can be a problem, depending on the system. These options seem to fix it, for GitHub at least.

Hello @alphapapa,
I find your project great and integrating it to pywal might be the ricer's bliss.

Maybe a pywal template out of one of the all-sites.css versions of solarized-everything-css is enough?

Do you have interest on coding it or can we base another repo from your code?

Cheers

Seems like a good idea to get the word out.

Wikipedia start page

Two elements on Wikipedia start page are left without solarized style. Also the popup list when one types search term is left unstyled. Probably not a big deal since the front page is not used that often, but maybe of interest anyway.

When I activated all of the solarized light themes via Stylish (I'm using Chrome) the margins/spacing/alignment on Google gets messed up, pretty much making it unusable. I found that disabling the bigblow css theme sets everything back to normal.

It's a MediaWiki, but it looks like it uses a different side-menu.

@jgkamat Now that the multi-theme branch is merged, I guess we should do something about the screenshots in the readme. Maybe display one or two in the main readme, like they are now, and then link to a page showing all of the screenshots? What do you think?

• On, Preferences - Wikipedia, under appearance we can see that there are 5 default skins:
  • Vector
  • MinervaNeue
  • Modern
  • MonoBook
  • Timeless
• Is it possible if you could provide solarized light theme for Timeless? I used the default theme that you provided and I guess that is for Vector skin (which I think is the default wikipedia skin). The provided CSS for the Timeless skin, leaves a lot of white area around (in the background) and does not solarize the background.

Sorry I am not familiar with CSS. Thanks if you could help me out. You can see that it just needs a minor tweak (notice the white background)!

Addendum: Timeless theme is the same as the Vector theme except that when zooming in the left pane (which is not that useful), gets hidden and moves to the top, while in Vector theme, the left pane also keeps zooming and occupies a lot of space!

Hello and thank you for this project,

I found many pages resistant to the styles here, including common ones served from google and reddit. A few days ago I added more aggressive selectors to the darcula stylesheet and they vastly improved the effectiveness of the styles.

For example, these styles are at the top of the darcula css file I am using (reddit pages look outstanding with these),

html {
  background-color: #262626 !important;
}
html body,
html div,
html div * {
  background-color: #262626 !important;
  color: #909396 !important;
  text-shadow:none !important;
}
html body div * {
  border-color: #909396 !important;
  text-shadow:none !important;
}
html body div a {
  text-shadow:none !important;
  color: #ce4139 !important;
}
html body div a:visited {
  color: #b68800 !important;
}
html body input,
html body textarea {
  background-color: #2e2e2e !important;
  color: #909396 !important;
}

I recommend using 'stronger' names in the stylesheets here.

/For video-cards and search button, color for light style/
g-inner-card {
background-color: #eee8d5;
}
.sbibod {
background-color: #eee8d5;
}

Just some minor stuff I noticed on GitHub:

(when hovering issues)

I tried to fix the "watching" and emoji menu one myself, without much luck so far (and running out of time, at least for today).

The base3 background colour isn't being applied to many parts of the page background. I changed the body selector to body, .container, #content, .inner-content as a bodge fix.

I'm using User JavaScript and CSS to apply the styles to *.stackexchange.com in Chrome version 67.0.3396.99 (Official Build) (64-bit).

Lots of websites now look quite ugly when using this. Wikipedia, Google, etc.

I use darkreader with grayscale set to 100, anyone interest to make it grayscale versions of files in this repo?

@The-Compiler @jgkamat @cal2195

Hey guys,

If we're adding other themes besides Solarized, this is no longer just a Solarized project. Do we need to rename and/or reorganize the project? If so, do you have any ideas? I mentioned the possible name everything-everything-css, which is...well, unique, if a bit silly sounding. everything-css would be simpler, but seems a bit vague. anything-everything-css sort-of makes sense, but only if you already know what the idea is. Anyway, ideas are welcome. :)

Would facebook support be a posibility in the near future?

Not sure if something is up with my install process or a script is buggy. This is basically what I did:

1. Open https://userstyles.org/styles/127328/solarized-everything-github
2. Select Customize Settings
3. Set Variant to Light
4. Click Install
5. Refresh Github
6. Github was DARK instead of Light

This is with Firefox and Stylus extension.

the indicators on the Arch forums that tell you there's new content (comments, threads) don't function when using this style. instead, they display a solarized box, rather than the light or dark boxes they would normally display. this happens regardless of the selected FluxBB theme the user is using.
this is the way they're supposed to look:

and this is how they look using the theme:

Can we do something with stylus to make certain rules appear in the site-specific files only?

For example, for LWN I'd like to fix those:

However, that involves rules for span and a:hover - for obvious reasons, they shouldn't land in solarized-all-sites-*.css.

(Note: I'm not going to work on this in the short term - my browser can't do per-domain stylesheets yet anyways 😉)

@jgkamat @emraher

Hi there,

It's really cool that two people have now used this repo as a base to support other color themes! :)

I was thinking, it would probably be fairly easy to add support for other color themes besides Solarized so they could all be supported from a single repo and build process. That way we could all share the work keeping the site files up-to-date.

Of course, that might mean essentially starting a new repo. Maybe it should be called everything-everything-css? Haha.

Of course, there might occasionally be some minor conflicts about which colors to use. That is, all of the sites/*.styl files would have to be the same, regardless of the color theme, but the color names would be mapped to different color values depending on which color theme file was being used (we'd probably reorganize the files into themes/{solarized,darculized,dracula} directories). Most of the time this would be fine, but occasionally there might be a page element that needed tweaking to look good with a certain theme, and that would be hard or impossible to do.

But it might be worth that small sacrifice if it reduced the maintenance burden.

What do you all think? Would you be interested in this, or would you prefer to keep your variants separate?

Thanks.

There are some problems with the documentation site readthedocs.io and dark themes:

Using qutebrowser with solarized-dark-all-sites.css, reddit looks like this:

I'm not great with web-stuff, so it's very possible this is just something I've somehow screwed up myself. Can anyone else reproduce?

I think they changed their design quite recently.

(I hope you don't mind me dumping stuff I notice here 😆 Planning to contribute a bit after my exams are done, if I'm still using this by then - really happy so far!)

hi,

This looks like a nice project.
I want to try it but I'm wondering how to load a css file with qutebrowser.

To reflect the new layout and other changes.

The new BigBlow css file seems to be conflicting with many of my sites in the all-sites css file.

For example Before:

After:

Could the bigblow target please be excluded from the all-sites css file somehow?

(this is what caused the problems for me in the PR's I made).

I can confirm your installation section is apparently not idiot proof. I'm running Firefox and have just installed the Stylish add-on. I tried Stylish once before but gave up having not found a theme I could like. Yours looks tempting but I'm lost on how to use it. I made a git clone of your repo and then took a WAG by clicking on the S > Manage styles ... > Install from URLS ... > entered full path to my clone's styl/dark.styl with a prefix of "file://". I gave it a name of "Solarized-Everything" and then exactly nothing seemed different. :-(

I removed that attempt in the Stylish manager and retried with sites/all-sites.styl and still nothing.

Where did I go wrong?