Proposal: Amendment to CSS Policy, Again

It's been a hot minute since the last time I tried to pass an amendment to the CSS policy. Here we are again, with some amendments that are the same, some that have changed, and some new ones.


In the following sections I will lay out 11 amendments to the CSS policy that I believe are improvements. To cut through the bulk, I have bolded the actual policy changes. The rest is context and explanation.

Amendments are as follows, with the long ones collapsed for your convenience.

1. Allow certain hotlinking

Hotlinking will be allowed from sites that encourage it, for example Google Fonts.

No changes from last time

2. Translation module inaccuracy correction

The policy will be corrected in that the translation module can be affected by some CSS.

No changes from last time (barring changes from Amendment 6, see below)

3. Provide usage instructions

CSS themes must provide usage instructions. (They don't need to include examples.)

No changes from last time

4. Use [[include]], not @import

5. The theme must be applied to the theme page

The CSS theme must be applied to its own component page, making it trivial for an author to see what that theme looks like without having to find or create a page that uses it.

6. Keep the translation module

CSS creators will no longer be allowed to remove the translation module. It remains the most important tool for cross-branch navigation.

7. A theme must be used by at least one article

8. Themes must not contain an excessive amount of bloat code

9. New themes must be approved by a member of the tech team

10. Existing themes must be changed to comply with the CSS policy within six months

11. Themes should be posted into the theme category