Welcome to SSW.Rules.Content (The Data in markdown). Thank you for contributing best practices into SSW Rules!
Builds are done in GitHub Actions. After a rule is edited, a Pull Request is needed to be merged into the main branch and deployed to Production.
PRs can be approved by anyone at SSW. Try these people first:
- Tiago Araujo
- Brady Stroud
- Adam Cogan
- Luke Cook
- Brook Jeynes
See the outstanding Pull Requests.
Most edits show on the site soon after merge. New redirects (from renaming a rule) only start working after the next production deploy, which runs daily at 06:00 UTC.
📘 How-to guides and GitHub Actions documentation are in the Wiki. To change a rule's URL or move it to a new folder, follow How to Rename Rules.
- Rules live in
public/uploads/rules/[uri]/rule.mdx - Categories live in the categories folder
- Each rule has a folder containing rule.mdx and its images/assets
- Rules are organised into categories
- A rule can belong to multiple categories
- Category pages link to rules via frontmatter data
This is built into a static site by the code at SSW Rules.
This repository uses GitHub Agentic Workflows to assist in the ongoing maintenance of content. Using campaigns. For more information about these campaigns, and how to create them, refer to the ContentHawk Documentation.