Add new entry for CSS snippets for Plugins Publishing Guidelines

[DaddyBoard]

No description provided.

[Huderon]

Should this not be under scope rather than general?

Where do we draw the line here? If something could be accomplished with CSS but the dev adds some nonsense logic that isn't really required does that get a pass? The function of ChatButtonsBegone and CollapsibleUI can both be achieved with purely CSS, where do they stand?

[DaddyBoard]

Should this not be under scope rather than general?

woops, yes meant it to be under scope

[DaddyBoard]

Where do we draw the line here? If something could be accomplished with CSS but the dev adds some nonsense logic that isn't really required does that get a pass? The function of ChatButtonsBegone and CollapsibleUI can both be achieved with purely CSS, where do they stand?

ChatButtonsBegone(CBB) is a goliath that uses webpack queries to get the classnames, meaning its not a spam of css with wildcard queries happening on every mutation - that to me is far across the line of "functionality as a plugin" rather than just a css snippet in a plugin.

Quick glance at CollapsibleUI shows its not just css, it gives the user multiple options across various parts of the UI, a bit like CBB.

I would deem these appropriate for being a plugin, whereas something like this is what the new rule covers. Lastly, like most rules, are generally up to the discretion of the review team - if its as simple as that plugin linked above, its obviously not permitted

[Copilot]

Pull request overview

Adds a new guideline clarifying that submissions categorized as plugins must include JavaScript-driven logic/interactivity, and that CSS-only snippets (e.g., purely hiding/removing elements) are not acceptable under the plugin guidelines.

Changes:

• Added a Scope guideline disallowing CSS-only “plugin” submissions that only hide/remove elements.
• Adjusted document spacing around the Scope section.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

There’s an extra blank line before the “## Scope” header (three consecutive blank lines after the last General Guidelines item). Consider removing one to keep spacing consistent with other section breaks in this doc.

Suggested change

[Copilot]

Minor wording/grammar: “element removal/hiding” reads awkwardly; consider changing to “element removal or hiding” for clarity.