Skip to content

Commit

Permalink
Propose guidelines change (#28)
Browse files Browse the repository at this point in the history
* Propose guidelines change

* Update guidelines.md

Improve theme guidelines wording
  • Loading branch information
zerebos authored Dec 23, 2024
1 parent ac604fb commit 96472ca
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 3 deletions.
3 changes: 2 additions & 1 deletion docs/plugins/introduction/guidelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ These are guidelines that all plugins are expected to abide by. Any plugin that
1. Addons must not discriminate whom can use it.
1. Addons must not collect user data without opt-in consent.
1. Addons must not include explicit sexual material or other adult content.
1. Addons must have English language support.


## Scope
Expand Down Expand Up @@ -51,4 +52,4 @@ These are guidelines that all plugins are expected to abide by. Any plugin that
- Necessary dependencies should be either bundled or a separate plugin.
1. Plugins must not use closed source nor self-hosted binaries or libaries.
1. Plugins must not be obfuscated, minified, include sourcemaps, or be otherwise deceitful.
<!-- 1. Plugins must not bypass the addon approval system by implementing their own update system. -->
1. Plugins must not bypass the addon approval system by implementing their own update system.
7 changes: 5 additions & 2 deletions docs/themes/introduction/guidelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ These are guidelines that all themes are expected to abide by. Any themes that v
1. Addons must not discriminate whom can use it.
1. Addons must not collect user data without opt-in consent.
1. Addons must not include explicit sexual material or other adult content.
1. Addons must have English language support.


## Usability
Expand All @@ -35,5 +36,7 @@ These are guidelines that all themes are expected to abide by. Any themes that v
- If used, provide sensible fallbacks for other languages.

## Design
1. Themes should not be a basic recolor or background change. Themes should significantly alter the look and feel of Discord.
1. Themes should have full coverage of most common pages, popouts, modals and controls. Keep in mind that changing Discord's variables does not provide full coverage of the app.
1. Themes should provide a cohesive design that notably alters the look and feel of Discord.
- A simple recoloring via CSS variables or adding a background image is not considered notable.
1. Themes should be designed to seamlessly integrate with any unthemed sections, ensuring a smooth and consistent experience across the entire interface
- Try to leave as few unthemed sections as possible in order to improve the user experience.

0 comments on commit 96472ca

Please sign in to comment.