Website Update Procedure Ryxen The Rainmaker
This document defines the standard operating procedure for updating content, code, and structure on the Ryxen.ca and therainmakerops.com websites. It ensures consistency, security, and compliance with brand guidelines.
All website updates — whether textual, structural, or functional — must follow this procedure to maintain version control, minimize downtime, and ensure all changes are reviewed by a qualified team lead. This policy applies to both public sites and internal dashboards managed under the Ryxen brand.
Updates are categorized as: minor (typos, media replacement), standard (new pages, styling changes), and critical (security patches, platform migrations). Each category triggers a specific approval and testing workflow.
This procedure covers all website properties owned or operated by Ryxen and The Rainmaker Ops, including but not limited to ryxen.ca, therainmakerops.com, and any subdomains or staging environments.
It applies to all employees, contractors, and partners with write access to site repositories or CMS panels. Individual blog posts and landing pages for marketing campaigns are also included, unless explicitly exempted in writing by the Director of Operations.
- All code changes must be pushed to the `staging` branch first, then merged to `main` only after successful review and automated test pass.
- Content must adhere to the current Ryxen brand guidelines: approved typefaces, colour palette (including
#596673as accent), and tone. - Every update must be logged in the change register with timestamp, author, description, and category. A monthly audit is performed by the ops lead.
- A rollback plan must be documented before any critical or standard update. If a staging environment exists, test there first.
- Website Editor / Content Author – Creates and submits content changes; responsible for grammar, spelling, and link integrity.
- Reviewer (Team Lead or Senior) – Approves content accuracy, brand compliance, and functional impact; merges approved changes.
- Operations Director – Owns the policy, grants exemptions, chairs the monthly audit, and ensures the rollback plan is up to date.
- DevOps / Technical Lead – Manages CI/CD pipelines, security patches, and server-side deployments; holds merge rights for critical updates.