Compare text

Find the difference between two text files

Real-time editor

Hide whitespace changes

Hide unchanged lines

Disable line wrap

Layout

Diff precision

Text styles

Syntax highlighting

Diffchecker Desktop The most secure way to run Diffchecker. Get the Diffchecker Desktop app: your diffs never leave your computer!Get Desktop

Untitled diff

Created 7 years agoDiff never expires

11 removals

Lines
Total
Removed

Characters
Total
Removed

To continue using this feature, upgrade to Diffchecker Pro View Pricing

45 lines

22 additions

Lines
Total
Added

Characters
Total
Added

To continue using this feature, upgrade to Diffchecker Pro View Pricing

53 lines

+ __CSS Policy__

[[size 125%]] **__Use__** [[/size]]

Just like anything else on the wiki, a CSS theme must be licensed under the same Creative Commons site license, if it is hosted on the wiki. This means that anyone is free to use, copy, and alter that copy.

What they may not do is alter it for you. It would be treated like any other article or work on the wiki (minus being subject to deletion at this time. A deletion policy is not currently defined for CSS themes, and is not being proposed at this time.)

[[size 125%]] **__What you can do:__** [[/size]]

* Change any of the style components of the wiki which do not violate the can't section.

[[size 125%]] **__What you cannot do:__** [[/size]]

* Remove, hide, alter, or "break" any navigation elements of the wiki.

* Break the 'structure' of the wiki. Don't move the top-bar to 50% to the right, don't change the sidebar to be in wingdings unless that's your specific format screw going on.

* Use the '!important' tag beyond what is required to override issues with the main CSS theme, or provide compatibility with your sub-themes or other CSS projects. Basically, don't make your theme be the only applicable theme.

* Remove the rating module

* Remove back/forward links from articles where they've been inserted.

* Encourage users to import your theme using CSS @import rules.

[[size 125%]] **__What you must do:__** [[/size]]

* Provide usage instructions.[[footnote]]Note that this only refers to telling users what to type to get the theme to show up on their article. You do not need to include examples of your theme's formatting.[[/footnote]]

* Encourage users to import your theme using Wikidot's [[include]] method (and set up your theme page accordingly - [http://scp-sandbox-3.wikidot.com/css-include-template example here]).

[[size 125%]] **__Translation Module__** [[/size]]

The translation module currently can't be altered via CSS. In the event that the Translation module clashes significantly, you are free to remove it via css, and maintain a list of translations in the comments section, or relvant hub for that article. Please try and keep it current to within a month at any given time.

The translation module can only be modified with CSS to a very limited extent. In the event that the translation module clashes significantly, you are free to remove it via css, and maintain a list of translations in the comments section, or relevant hub for that article. Please try and keep it current to within a month at any given time.

[[size 125%]] **__Accessibility__**[[/size]]

This can be evaluated on a per-theme basis.

This section is difficult to explain, but the following should be considered when composing a theme:

* Is this theme readable for color-blind people? (e.g. it employs bad color combinations like red + green which make it difficult for colorblind users to navigate the site)

* Is this theme readable for colorblind people? (e.g. it employs bad color combinations like red + green which make it difficult for colorblind users to navigate the site)

* Does this theme hamper the ability to use screen readers? (e.g. it adds 'invisible' content which gets read by screen readers but not sighted users)

* Are the fonts it uses legible for all users? (e.g. the body font size is too small, the font itself is difficult to read)

and so on. Best practices and recommendations to address all of these potential issues are easily available with a cursory Google search.

[[size 125%]] **__Hotlinking__**[[/size]]

Hotlinking is incredibly bad practice and also against site rules. There isn't a good reason to do it, given that you can host assets such as fonts on the page itself, and it also introduces problems when browsers prevent CSS themes from accessing off-site resources. As an example of how this breaks, was a version of a new rating module hosted on the sandbox. Users reported them breaking because their browser would block the page from loading it entirely.

Hotlinking is the practice of linking to files on another site, and is both incredibly bad practice and against site rules. It is incredibly bad manners to force someone's site to load images for your theme, and also introduces a degree of unreliability to your theme -- what if that site disappears?

To this end, CSS themes should not use off-site assets, instead of uploading them to the site as they would for images. I would also like to reinforce that CSS should not be linked from sandbox pages, or anywhere that isn't the main site outside of workbenches. Please use a component: page on the wiki for css themes.

To prevent hotlinking, all images, fonts and miscellaneous files used in a CSS theme must be files uploaded to the theme's page rather than linked from elsewhere on the internet.

However, you are permitted to use certain sites that explicitly encourage hotlinking for serving files to users. Notable examples include [https://fonts.google.com/ Google Fonts] and [https://picsum.photos/ Lorem Picsum]. If in doubt, play it safe and [http://05command.wikidot.com/tech-hub-chat ask the Tech Team].

Additionally, CSS should not be linked from sandbox pages or anywhere that isn't the main site (outside of workbenches). Please use a {{component:}} page on the wiki for CSS themes.

[[size 125%]] **__Remediating non-compliant themes__**[[/size]]

If your theme doesn't function in the major browsers (Internet Explorer 11, Firefox, Chrome, Opera, Safari) in a way that completely breaks navigation, function, or accessibility, it needs to be **removed** (or at bare minimum, removed from include blocks) from the site, then fixed, in that order.

Our first priority is compatibility, function, and accessibility.

Saved diffs

Original text

Open file

+ __CSS Policy__

[[size 125%]] **__Use__** [[/size]]

Just like anything else on the wiki, a CSS theme must be licensed under the same Creative Commons site license, if it is hosted on the wiki.  This means that anyone is free to use, copy, and alter that copy.

What they may not do is alter it for you.   It would be treated like any other article or work on the wiki (minus being subject to deletion at this time.  A deletion policy is not currently defined for CSS themes, and is not being proposed at this time.)

[[size 125%]] **__What you can do:__** [[/size]]
* Change any of the style components of the wiki which do not violate the can't section.

[[size 125%]] **__What you cannot do:__** [[/size]]
* Remove, hide, alter, or "break" any navigation elements of the wiki.
* Break the 'structure' of the wiki.  Don't move the top-bar to 50% to the right, don't change the sidebar to be in wingdings unless that's your specific format screw going on.
* Use the '!important' tag beyond what is required to override issues with the main CSS theme, or provide compatibility with your sub-themes or other CSS projects.  Basically, don't make your theme be the only applicable theme.
* Remove the rating module
* Remove back/forward links from articles where they've been inserted.

[[size 125%]] **__Translation Module__** [[/size]]

The translation module currently can't be altered via CSS. In the event that the Translation module clashes significantly, you are free to remove it via css, and maintain a list of translations in the comments section, or relvant hub for that article.  Please try and keep it current to within a month at any given time.

[[size 125%]] **__Accessibility__**[[/size]]

This can be evaluated on a per-theme basis.

This section is difficult to explain, but the following should be considered when composing a theme:

* Is this theme readable for color-blind people? (e.g. it employs bad color combinations like red + green which make it difficult for colorblind users to navigate the site)
* Does this theme hamper the ability to use screen readers? (e.g. it adds 'invisible' content which gets read by screen readers but not sighted users)
* Are the fonts it uses legible for all users? (e.g. the body font size is too small, the font itself is difficult to read)
and so on. Best practices and recommendations to address all of these potential issues are easily available with a cursory Google search.

[[size 125%]] **__Hotlinking__**[[/size]]

To this end, CSS themes should not use off-site assets, instead of uploading them to the site as they would for images. I would also like to reinforce that CSS should not be linked from sandbox pages, or anywhere that isn't the main site outside of workbenches.  Please use a component: page on the wiki for css themes.

[[size 125%]] **__Remediating non-compliant themes__**[[/size]]

Our first priority is compatibility, function, and accessibility.  
>

Changed text

Open file

+ __CSS Policy__

[[size 125%]] **__Use__** [[/size]]

Just like anything else on the wiki, a CSS theme must be licensed under the same Creative Commons site license, if it is hosted on the wiki.  This means that anyone is free to use, copy, and alter that copy.

What they may not do is alter it for you.   It would be treated like any other article or work on the wiki (minus being subject to deletion at this time.  A deletion policy is not currently defined for CSS themes.)

[[size 125%]] **__What you can do:__** [[/size]]
* Change any of the style components of the wiki which do not violate the can't section.

[[size 125%]] **__What you must do:__** [[/size]]
* Provide usage instructions.[[footnote]]Note that this only refers to telling users what to type to get the theme to show up on their article. You do not need to include examples of your theme's formatting.[[/footnote]]
* Encourage users to import your theme using Wikidot's [[include]] method (and set up your theme page accordingly - [http://scp-sandbox-3.wikidot.com/css-include-template example here]).

[[size 125%]] **__Translation Module__** [[/size]]

The translation module can only be modified with CSS to a very limited extent. In the event that the translation module clashes significantly, you are free to remove it via css, and maintain a list of translations in the comments section, or relevant hub for that article.  Please try and keep it current to within a month at any given time.

[[size 125%]] **__Accessibility__**[[/size]]

This can be evaluated on a per-theme basis.

This section is difficult to explain, but the following should be considered when composing a theme:

* Is this theme readable for colorblind people? (e.g. it employs bad color combinations like red + green which make it difficult for colorblind users to navigate the site)
* Does this theme hamper the ability to use screen readers? (e.g. it adds 'invisible' content which gets read by screen readers but not sighted users)
* Are the fonts it uses legible for all users? (e.g. the body font size is too small, the font itself is difficult to read)
and so on. Best practices and recommendations to address all of these potential issues are easily available with a cursory Google search.

[[size 125%]] **__Hotlinking__**[[/size]]

To prevent hotlinking, all images, fonts and miscellaneous files used in a CSS theme must be files uploaded to the theme's page rather than linked from elsewhere on the internet.

Additionally, CSS should not be linked from sandbox pages or anywhere that isn't the main site (outside of workbenches).  Please use a {{component:}} page on the wiki for CSS themes.

[[size 125%]] **__Remediating non-compliant themes__**[[/size]]

Our first priority is compatibility, function, and accessibility.