Skip to content

Centralize community rules #944

@shtlrs

Description

@shtlrs

Currently, the same rules are persisted in 2 different places
pydis_site/apps/api/views.py and pydis_site/apps/content/resources/rules.md

Over the past month or so, we've had two rule updates in one of the files only, leaving the other forgotten.
It would be nice to put the rules in one place only in order to avoid missing out on one over the other.

Note
I'm not even sure this is something we'd want to do, so just putting it out there (@jchristgit you're the site master, so you might have better scope knowledge here)

An idea off the top of my head is:
Since one is put in an .md file, we can't really achieve intepolation of the content of that file.
So maybe the view can parse the file & extract the rules based on their numbers and maps them to a tuple along with the keywords.

Metadata

Metadata

Assignees

Labels

area: APIRelated to or causes API changesarea: frontendRelated to site content and user interactionpriority: 3 - lowLow Prioritytype: enhancementChanges or improvements to existing features

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions