Skip to content

Harden website accessibility, performance, security, deployment, and rollback #3

Description

@zoeyrose

Outcome

Make atrinik.org a production-quality launch/discovery/download surface for the replacement cutover.

Scope

  • Meet WCAG-oriented semantic HTML, keyboard/focus, contrast, reduced motion, responsive layout, alt text, headings, forms, and error-state requirements.
  • Set measurable page-weight, image, font, script, LCP/CLS/INP or static-proxy budgets and validate representative mobile/desktop pages.
  • Apply CSP/security headers, dependency/action pinning, secret isolation, branch/environment controls, custom-domain/TLS/DNS ownership, and preview protections.
  • Define deployment health checks, cache invalidation, immutable assets, previous-deployment rollback, domain/DNS rollback, and outage page.
  • Test broken/missing GitHub/metaserver data at build/runtime without publishing misleading downloads/status.

Acceptance criteria

  • Automated accessibility/link/build/security/performance checks plus manual keyboard/screen-reader/reduced-motion review pass.
  • Production deployment and rollback rehearsal capture exact commit/artifact/domain state.
  • No secret appears in static output/logs; deployment permissions are least privilege.
  • Classic/replacement download and compatibility messaging remains accurate through cutover.
  • Operational ownership and recovery instructions live in this repository.

Dependencies

Can establish budgets early; final gate depends on replacement release candidates and cutover plan.

All website code is MIT. Media/downloaded artifacts retain their exact licenses and provenance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Effort

    None yet

    Projects

    Status
    Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions