Collection of UserStyles (US), web styling CSS for use with Stylus or similar browser plugin. (except Stylish)
This GIT repo is only used for description and feedback/issue tracker for now, not actual ...user.css files.
UserStyle files are in USw repository: https://userstyles.world/user/papo
That is because of the incompatible workflow.
Dark Styles I create are made for the purpose of comfortable reading.
There is a notable difference with dark Styles for color-haters.
Color is not removed, or set to the same one, for distinguishable elements. On the contrary, additional special color is used for links, visited links, links to a page section vs. links to another article, separate colors for caption/sub-caption...
But, using the UserStyle Options, all important colors can be changed even to the same one, thus giving the color-haters false feeling of cleanliness ;).
[m] in description of a style from this set means it's also tested for mobile version.
There are three types of Background Color used in these US, with defaults for two of them being a pattern.
The practice of using a pattern for page background and text background, instead of a solid color has an important purpose of not hypnotizing the reader. They do help to stay on the line and in focus. The negative effect of solid background and sharp contrast of a text on people reading it is a proofed concept.
These background colors can also be changed in Options. A very nice alternative would be to changing colors of background to presets Dark charcoal and Rich black colors in US Options. But the advantage of non-hypnotizing background would be lost.
Background: color or pattern for page background. Used for empty parts of a web page.
Text background: color or pattern for background of main text on a web page.
Third color is a section background. It's fixed to 30% transparent.
The main problem with styles is, they tend to stop working over time. This is because the site they are made for does change and the maintainer does not have time to keep updating the style.
In this set of styles I try to keep a style as simple as possible, not changing every small detail, but only those that matter the most.
This way I can keep up with fixes to all my styles.
I use these styles myself since 2017, so there is some warranty of continuity.
I have tens of styles and plan to share majority of them.
A preview image of these Styles do not show ADs. But they are not removed by these UserStyles.
I don't want to support general AD removing. Also, to follow a practice of not combining multiple features into one,
"Dark" styles do change color style, "DeAnnoy" styles do remove or change behavior of certain page elements and, if desired, find and install a style for removing ADs.
I do not provide them. Multiple styles for one web site can work together without any measurable overhead.
The exception are some annoying ADs, masking themselves as main page content, leading to other useless pages, or are otherwise intrusive.
These ADs are 1, background-colored/bordered by "Dark" styles. 2, can be disabled in "DeAnoy" styles.
These includes 3rd party enhancers with "(i)Relevant" articles, like Outbrain, Dianomi.
Moreover, they are mostly embedded in a shadow DOM or an iframe. And that makes them impossible or difficult to style.
Dark Styles I use for news media and similar sites have these common features:
No bright colors. Easy on eyes. No white background, bars or blocks in and around main article.
High contrast. No dark text on dark background as many styles do, but bright white on nearly black.
A special color for visited links. Like good old web does by default, so you know what you've already read when another article is referenced in an article.
Main colors can be changed on all styles in Configure of the style.
Sometimes the header is restyled. Specially if the original is using bright colors.
How Styles perform in lower resolutions is not tested for now.
But there is a plan to support lower widths. Specially if Stylus will be made available in Firefox mobile, or Chrome will allow plugins in mobile browser.
For now, if it's obvious from original site's CSS that a rule which is being overrid applies only to certain resolution, I try to keep the overridden the same way.
The style might not always look very fancy.
If you go deeper in a site, the styling might not work. e.g. menus, sharing features, featured articles.
If you find a text which is not readable, e.g. white on white background, or dark on black, report it and I'll fix it,
but I'll not be adding a complete site style overdo.
I don't use ADs. They are not styled, as I don't see them. I will not be adding add blocker to any of my styles. But if there is an AD banner too bright,
you can ask me to style it to a darker version.
I use a common Configure header and scheme.
You can use the Configure in the menu of Stylus to change main colors. That setting will survive most updates.
Not always are all options in Configure working, because I just copy one over, to ease the maintenance of so many styles,
but not always add rules to support all options from the Configure. Though the plan is to implement all options in time.
The background pattern and part of the header code was taken from: https://github.com/StylishThemes
Advanced users could also override variables in :root section of my styles, to customize the style even more. To do that, create your own style, use the same @-moz-document and define just the :root section only with rules you want to override. Then use Actions > Style Injection Order in Stylus plugin Options, to place your style above mine. When site changes and I'll update my style, your override rules will still work and you don't have to do anything to keep the site as you like it.
There might be unstyled elements, as I have various site customizing gadgets. Not just AD blocker.
I try to disable them sporadically to check how the site would look for others. But not always and not thoroughly.
If you see an element which is particularly intrusive by its brightness, please file an Issue, make a screenshot and add a description.
If you want, you can make a fix yourself and push a merge. I'll accept, but later will probably edit your edit anyway. So expect that in advance and don't be upset.
I plan to change this common part, from USO pre-processor to default or stylus, to intentionally break compatibility with Stylish plugin.
Stylish is evil. Spying on users, sending all history, even confidential data to analytics site.
Breaking rules of content writers and Extension Stores. It should be banned. I will not support it further with my styles.
If you use Stylish, change to Stylus, you can keep all styles you have and use more sources for even more styles.
Also, the licence of my Styles is not compatible with Stylus plugin. You can't use it legaly in Stylish plugin (while OK in other, like Stylus).
It is because I use non-commercial licence, CC BY-NC-SA 4.0, and Stylish is making money on exploiting its users and misusing user created content commercially.
All styles using this look-alike theme are located
Styles using Around 40 indistyles are not here in git now.
They are for now only in USw repository: https://userstyles.world/user/papo
Use Issues here in Github to report a problem.
If you really really want to fix a style, you can commit the whole css file here and I'll manually link it or copy it to USw Store.
The rules are: Maintain principles mentioned above. Use existing code style. Overload original site css where possible, do not use !important,
do not style insignificant details or not easy reachable page, use variable where appropriate.
To save your time, discuss in Issues section before, to be sure the commit won't be discarded.
I am still trying to find / waiting for a good work-flow solution.
Maintaining a style could be time demanding as the styled site can change often.
What I do is, when I see a problem, I'll fix it in Stylus web editor.
It then offers a way to upload to userstyles.world by a press of a button. But I can't get them here to git auto-magically.
We can link styles in userstyles.world to git, and they're updated when a style in git updates, but not the other way around.