Skip to content

Bootstrap the MIT Astro website repository and validation contract #1

Closed

Description

@zoeyrose

Outcome

Establish atrinik/website as the sole source/deployment owner for atrinik.org while the root repository remains a thin orchestration wrapper.

Scope

  • Create Astro at repository root on main, pin Node/package manager/lockfile, and define static-first architecture with no unnecessary server runtime.
  • Add formatting, lint, type/build, link, asset-license/provenance, accessibility, performance-budget, dependency/security, and deployment dry-run checks under aggregate Website validation.
  • Document Cloudflare Pages project/domain/environment/preview/production ownership, secrets, rollback, and least-privilege deployment.
  • Use semantic releases for source changes and immutable deployment provenance where supported.
  • Expose wrapper build contract only after repository commands/artifacts stabilize.

Acceptance criteria

  • Clean clone installs reproducibly and builds a self-contained static output with no sibling source checkout.
  • No website implementation is added to atrinik/atrinik.
  • CI/deployment use exact main, protected environments, minimal permissions, and reviewable previews.
  • Release/deployment artifacts include dependency/license/provenance records.
  • Baseline page meets documented accessibility and performance budgets.

Dependencies

Independent of game runtime. Content/download pages integrate released metadata later.

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

Activity

  1. zoeyrose commented on Aug 8, 2026

    @zoeyrose
    MemberAuthor

    Implemented by #6 and validated in the published v1.0.0/v1.0.1 release line: reproducible Astro build, aggregate cross-platform validation, static output, deployment dry-run/rollback contract, SBOM and provenance artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions