gwanyan-interactive-grassland - v0.1.0
    Preparing search index...

    gwanyan-interactive-grassland - v0.1.0

    Gwanyan

    Repo Health Dependency Review CodeQL Scorecards

    If you are new to the project, read START_HERE.md first.

    The most beginner-friendly commands live in scripts/README.md.

    The shortest beginner path is:

    pwsh ./scripts/check-prerequisites.ps1
    pwsh ./scripts/install-project-dependencies.ps1
    pwsh ./scripts/run-development-application.ps1
    
    pwsh ./scripts/check-prerequisites.ps1
    pwsh ./scripts/install-project-dependencies.ps1
    pwsh ./scripts/run-development-application.ps1
    

    Open the local URL, move the mouse across the field, and watch the wind push the grass.

    pwsh ./scripts/build-all-artifacts.ps1
    pwsh ./scripts/run-all-tests.ps1
    pwsh ./scripts/verify-complete-project.ps1
    

    These scripts provide the simplest named entry points for the full workflow.

    • documentation/site/: the structured handbook and GitHub Pages site
    • documentation/site/static/api/: generated API docs from TypeDoc
    • documentation/wiki/: the separate beginner wiki served by Gollum

    If you want script names that are easy to understand, start in the scripts directory and use the matching PowerShell or Bash wrapper for the task you want.

    pwsh ./scripts/build.ps1
    pwsh ./scripts/build-all-artifacts.ps1
    pwsh ./scripts/run-all-tests.ps1
    pwsh ./scripts/verify-complete-project.ps1
    

    Detailed explanations live in scripts/README.md.

    The project explicitly documents why each major external library exists and links to the relevant official documentation in documentation/site/docs/reference/external-libraries.md.

    The repository contains workflows and policies for:

    • linting and formatting
    • unit and browser testing
    • coverage enforcement
    • TypeDoc and Docusaurus build verification
    • secret scanning
    • dependency review
    • CodeQL analysis
    • OpenSSF Scorecards
    • GitHub Pages deployment
    • pull request quality checks
    1. Clone the repository.

    2. Review CONTRIBUTING.md before making changes.

    3. Run the repository policy check:

      pwsh ./scripts/verify_repo_standards.ps1
      
    • Repo Health validates workflows, lints Markdown, checks repository policy, and scans for secrets.
    • Dependency Review flags risky dependency changes in pull requests.
    • CodeQL analyzes committed GitHub Actions and JavaScript or TypeScript code when those languages are present.
    • Scorecards monitors open source supply chain health.
    • Pull request titles are expected to use conventional prefixes such as feat: and fix:.
    • Documentation is treated as a first-class quality gate.
    • The repository is tuned for strong defaults first, then for expansion into application code as the project grows.