@grove-dev/astro 0.2.20 → 0.3.2

package/templates/default/.github/pull_request_template.md

@@ -1,27 +0,0 @@
-## What this PR does
-
-A short summary of the change. One or two sentences. If it closes an
-issue, write "Closes #123" so it auto-links.
-
-## Why
-
-The motivation. Link to any relevant issues or discussions. If this
-is a UI change, attach a before/after screenshot.
-
-## How to verify
-
-Steps for a reviewer to follow:
-
-1. `pnpm install`
-2. `pnpm exec grove validate`
-3. `pnpm grove:dev` and open `…`
-4. Confirm that `…`
-
-## Checklist
-
-- [ ] `pnpm exec grove validate` passes
-- [ ] `pnpm run build` succeeds locally
-- [ ] For record changes: the `slug` is unique and matches the
-      filename (`data/records/<slug>.yml`)
-- [ ] For new categories / stacks / platforms: the field appears
-      sensibly in `Browse by category` and `Browse by stack`

package/templates/default/.github/workflows/build.yml

@@ -1,55 +0,0 @@
-name: Build
-
-on:
-  push:
-    branches: [main]
-  workflow_dispatch:
-
-jobs:
-  build:
-    name: grove build
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    permissions:
-      contents: read
-      pages: write
-      id-token: write
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: pnpm/action-setup@v4
-        with:
-          version: 10
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      # `build` chains build:data + build:sitemap + build:llms + astro build.
-      # Site URL is overridden so sitemap/OG/canonical links resolve to
-      # the deployed URL rather than the placeholder in grove.config.ts.
-      - name: Build site
-        env:
-          SITE_URL: ${{ vars.SITE_URL || github.pages.custom_domain || format('https://{0}.github.io/{1}', github.repository_owner, github.event.repository.name) }}
-        run: pnpm run build
-
-      - name: Setup Pages
-        uses: actions/configure-pages@v5
-
-      - name: Upload artifact
-        uses: actions/upload-pages-artifact@v3
-        with:
-          path: ./dist
-
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v4
-
-      - name: Summary
-        if: success()
-        run: |
-          echo "✅ Deployed to ${{ steps.deployment.outputs.page_url }}"

package/templates/default/.github/workflows/cleanup-stale-records.yml

@@ -1,48 +0,0 @@
-name: Cleanup stale records
-
-on:
-  schedule:
-    # Monthly — first Monday 05:00 UTC. Cheap enough to run daily
-    # if you want, but most repos don't change status that often.
-    - cron: "0 5 1-7 * 1"
-  workflow_dispatch:
-
-jobs:
-  cleanup:
-    name: grove cleanup stale
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    permissions:
-      contents: read
-      issues: write
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: pnpm/action-setup@v4
-        with:
-          version: 10
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      # `grove cleanup stale` lists records whose health signals say
-      # they need human review (archived, no commits in 12+ months,
-      # unparseable repo, etc). The report is rendered as a Markdown
-      # summary in the workflow run.
-      - name: Run cleanup report
-        id: report
-        run: pnpm exec grove cleanup stale --report > cleanup-report.md
-
-      - name: Summarise
-        run: |
-          if [ -s cleanup-report.md ]; then
-            echo "## Cleanup candidates" >> $GITHUB_STEP_SUMMARY
-            cat cleanup-report.md >> $GITHUB_STEP_SUMMARY
-          else
-            echo "✅ No records need cleanup." >> $GITHUB_STEP_SUMMARY
-          fi

package/templates/default/.github/workflows/daily-refresh.yml

@@ -1,53 +0,0 @@
-name: Daily records refresh
-
-on:
-  schedule:
-    # Daily — 06:00 UTC. Refreshes stars, forks, and the most
-    # recent commit date for every record so the home page and
-    # /apps filters stay accurate.
-    - cron: "0 6 * * *"
-  workflow_dispatch:
-
-jobs:
-  refresh:
-    name: refresh activity
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    permissions:
-      contents: write
-      pull-requests: write
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: pnpm/action-setup@v4
-        with:
-          version: 10
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Refresh activity
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        # `grove sync github` walks every record, fetches the
-        # latest stars/forks/pushed_at, and writes back to the
-        # corresponding yml file. Idempotent — no change if the
-        # record is already up to date.
-        run: pnpm exec grove sync github
-
-      - name: Open PR if records changed
-        uses: peter-evans/create-pull-request@v6
-        with:
-          commit-message: "chore(data): daily records refresh"
-          title: "Daily records refresh"
-          body: |
-            Automated daily refresh of stars, forks, and last-commit
-            timestamps for every record. Generated by the
-            `daily-refresh` workflow.
-          branch: chore/daily-refresh
-          delete-branch: true

package/templates/default/.github/workflows/sync-contributors.yml

@@ -1,53 +0,0 @@
-name: Sync contributors
-
-on:
-  schedule:
-    # Weekly — Sunday 04:00 UTC (after the metadata sync).
-    - cron: "0 4 * * 0"
-  workflow_dispatch:
-
-jobs:
-  sync:
-    name: sync contributors
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    permissions:
-      contents: read
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: pnpm/action-setup@v4
-        with:
-          version: 10
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      # Walk the records' repoUrl fields, fetch each repo's
-      # /contributors endpoint, and write a single
-      # `data/generated/contributors.json` (consumed by the home
-      # page and /contributors page). The script lives at the root
-      # of the project — it's not a CLI command because contributor
-      # fan-in is tightly coupled to this directory's git history
-      # and doesn't generalise across forks.
-      - name: Sync contributors from GitHub
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: node scripts/sync-contributors.mjs
-
-      - name: Commit contributors.json
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
-          if git diff --quiet data/generated/contributors.json; then
-            echo "No changes to contributors.json"
-          else
-            git add data/generated/contributors.json
-            git commit -m "chore(data): refresh contributors"
-            git push
-          fi

package/templates/default/.github/workflows/sync-github-metadata.yml

@@ -1,58 +0,0 @@
-name: Sync GitHub metadata
-
-on:
-  schedule:
-    # Weekly — Sunday 03:00 UTC. Off-hours so PR validation has the
-    # freshest metadata by Monday morning.
-    - cron: "0 3 * * 0"
-  workflow_dispatch:
-  # Run on push to data/records/** so curators see fresh stars/forks
-  # without waiting for the weekly cron.
-  push:
-    branches: [main]
-    paths:
-      - "data/records/**"
-
-jobs:
-  sync:
-    name: grove sync github
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    permissions:
-      contents: write
-      pull-requests: write
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: pnpm/action-setup@v4
-        with:
-          version: 10
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Sync GitHub metadata
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        # `grove sync github` walks every record, fetches stars/forks/
-        # activity from the GitHub API, and writes a `github` block
-        # back into each record's YAML. Falls back to HTML scraping
-        # when the API rate-limits.
-        run: pnpm exec grove sync github
-
-      - name: Open PR if records changed
-        uses: peter-evans/create-pull-request@v6
-        with:
-          commit-message: "chore(data): sync GitHub metadata"
-          title: "Weekly GitHub metadata sync"
-          body: |
-            Automated weekly sync of stars, forks, activity, and topics
-            for every record. Generated by the `sync-github-metadata`
-            workflow.
-          branch: chore/sync-github-metadata
-          delete-branch: true

package/templates/default/.github/workflows/validate-data.yml

@@ -1,35 +0,0 @@
-name: Validate data
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-    branches: [main]
-
-jobs:
-  validate:
-    name: grove validate
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: pnpm/action-setup@v4
-        with:
-          version: 10
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Validate records
-        # `grove validate` checks every records/*.yml against the
-        # blueprint schema, plus decisions.yml, taxonomy, and the
-        # health block. --strict fails on warnings, used on the
-        # main branch but not on PRs (where external contributors
-        # may have minor warnings we'd rather flag than block).
-        run: pnpm exec grove validate

package/templates/default/astro.config.mjs

@@ -1,25 +0,0 @@
-// @ts-check
-// SPDX-License-Identifier: MIT
-import { defineConfig } from 'astro/config';
-import tailwindcss from '@tailwindcss/vite';
-import groveAstro from '@grove-dev/astro';
-
-// `site` is the canonical URL the build uses for absolute links
-// (sitemap, OpenGraph, canonical tags, JSON-LD). The CLI injects
-// `grove.config.ts` → `site.url` at scaffold time, but it can also
-// be overridden per-build via the `SITE_URL` env var.
-//
-// The sitemap is generated by the CLI's `grove sitemap` command
-// into `public/sitemap.xml`; the public URL is exactly `/sitemap.xml`
-// (no `-index.xml` suffix).
-export default defineConfig({
-  site: process.env.SITE_URL || 'https://example.com',
-  trailingSlash: 'ignore',
-  integrations: [groveAstro()],
-  vite: {
-    plugins: [tailwindcss()],
-  },
-  build: {
-    format: 'directory',
-  },
-});

package/templates/default/content/pages/about.md

@@ -1,66 +0,0 @@
----
-title: "About"
-description: "What this directory is, who it's for, and how it works."
----
-
-# About this directory
-
-This site is a small, hand-curated index of useful open-source work
-relevant to a specific community. The framing is deliberately
-narrow: we list *one* project per record, with a hand-written
-"why listed" note for each, and we surface the things that matter
-in practice (recent activity, install friction, license, etc.)
-rather than the things that look impressive on a GitHub profile.
-
-## How it works
-
-Records live as YAML files in `data/records/`. Each record carries:
-
-- A `kind` (`project`, `resource`, or `entity` — picked by the
-  blueprint in `grove.config.ts`).
-- A `slug` (URL-safe identifier; becomes the path on
-  `/<kind>/<slug>`).
-- A `name` and a one-line `description`.
-- Cross-links (`links.github`, `links.website`, etc.) and free-form
-  tags.
-- An optional `curation` block with `labels`, `reviewedAt`,
-  `bestFor`, `whyListed`, `caveats`, and `scores`.
-- An optional `github` block with the live repository signals
-  (stars, forks, latest release, languages, pushed-at).
-
-At build time:
-
-1. `grove validate` checks every record against the JSON schema.
-2. `grove generate` writes `data/generated/records.{full,index}.json`
-   and `data/generated/site-config.json`.
-3. `grove sitemap` writes `public/sitemap.xml`.
-4. `grove llms` writes `public/llms.txt` and `llms-full.txt`.
-5. `astro build` produces the static output.
-
-The whole pipeline is reproducible. The records are the source of
-truth; everything else is derived.
-
-## Why a static site
-
-The directory is a *reference*, not an *app*. Static HTML is the
-right tool:
-
-- Every page is a single round-trip. No client-side data layer.
-- The output is auditable: open the deployed HTML and you can see
-  the full markup, no hidden hydration.
-- Hosting is cheap (or free, on GitHub Pages / Cloudflare Pages).
-- AI crawlers can read the full content. The `llms.txt` /
-  `llms-full.txt` files give them a single fetch to land on.
-
-## Contributing
-
-To add a record, open a submission issue. The maintainer will
-review and, if accepted, open a PR that adds the new YAML file.
-See `/submit` for the issue form and a minimal record template.
-
-## License
-
-The site's source code is MIT. The records are released under CC-BY
-4.0 unless a record's `license` field says otherwise. A record's
-`license` field is the license of the *project it describes*, not
-the license of the directory entry.

package/templates/default/content/pages/methodology.md

@@ -1,103 +0,0 @@
----
-title: "Methodology"
-description: "How records are picked, scored, and surfaced in this directory."
----
-
-# Methodology
-
-This page describes how entries in the directory are chosen, how the
-curation signals are computed, and what we do (and don't) promise about
-the data. The intent is to make the directory's logic auditable — every
-number on a detail page is reproducible from the record's YAML.
-
-## Selection
-
-A record is included if it is:
-
-1. **Open source.** Source is public under an OSI-approved license
-   (or public-domain dedication).
-2. **Actively maintained.** A pushed commit within the last 18 months
-   OR a declared maintenance status of `maintained` / `passive`.
-3. **Useful to a curious developer.** A working build, a real user
-   base (or a credible path to one), and a clear description of what
-   the project does.
-
-We exclude: abandoned experiments, vapourware, projects whose entire
-purpose is to sell a hosted plan, and any record that has not been
-hand-checked by a maintainer.
-
-## Curation labels
-
-The `curation.labels` field is a small, hand-set list. The supported
-labels are:
-
-- `hot` — high recent activity or attention (≥ 1 000 stars or a
-  commit within the last 30 days).
-- `new` — added to the directory in the last 7 days.
-- `mature` — long-running curated project, pushed > 365 days ago,
-  but still maintained.
-- `featured` — editor's pick for the front page.
-- `needs-review` — open submission awaiting a second maintainer
-  look.
-
-These labels are mutually additive, not exclusive. A `new` record
-can also be `hot`; a `mature` record can also be `featured`.
-
-## Scoring
-
-The detail page surfaces a five-dimension score block. The five
-dimensions are:
-
-- **Documentation** — is the README / docs site enough to onboard
-  without reading the source?
-- **Onboarding** — install in < 5 min, first useful result in < 1 h.
-- **Maintenance** — recent commits, issue close rate, release cadence.
-- **Community** — issues answered, discussions active, contributors
-  per release.
-- **Production-readiness** — CI, tests, security policy, releases
-  with semver.
-
-Each dimension is scored 0-5. The overall score on the detail page
-is the mean. Scores are stored on the record, not computed at build
-time, so we can deliberately disagree with the raw signals (a 1-line
-toy that happens to be wildly popular can still score low on
-documentation).
-
-## Health signals
-
-The `health` block on each record tracks four state machines:
-
-- `status` — `healthy` / `slowing` / `stale` / `archived`.
-- `tier` — `curated` / `community` / `experimental`.
-- `issue_close_rate` — moving 90-day average.
-- `last_release` — most recent semver tag.
-
-A record's `status` transitions are time-boxed: a project with no
-commits in 365 days flips from `slowing` to `stale`; 730 days flips
-to `archived`. The transition is mechanical; the recovery is
-manual (a maintainer sets `tier` back to `community` after review).
-
-## Lenses
-
-The directory's home page surfaces three curated lenses:
-
-- **Hot** — `curation.labels` includes `hot`, OR `github.stars` ≥
-  1 000, OR `pushedAt` within 30 days.
-- **New** — `pushedAt` within 7 days, OR `curation.labels` includes
-  `new`.
-- **Mature** — `health.tier === "curated"` AND `pushedAt` > 365 days
-  ago.
-
-Each lens caps at 6 items on the home page; the full filtered list
-is reachable via the lens tab on `/projects`.
-
-## What we don't promise
-
-- **Real-time data.** The site is rebuilt on a schedule, not on
-  every push. Counts and dates can lag by up to one build cycle.
-- **Verdict-free scores.** A high overall score means "useful to a
-  curious developer", not "best in class" — judgement calls are
-  documented per record, not baked into the score.
-- **Causal claims.** The "best for" / "why listed" / "caveats"
-  blocks are editorial notes, not derived signals. They reflect
-  what a maintainer thought at review time.

package/templates/default/data/records/coolify.yml

@@ -1,46 +0,0 @@
-kind: project
-name: Coolify
-slug: coolify
-description: Open-source, self-hostable Heroku / Netlify / Vercel alternative — deploy apps and databases from a single dashboard.
-category: DevOps
-tags:
-  - self-host
-  - paas
-  - deployment
-  - svelte
-stack: SvelteKit
-stacks:
-  - SvelteKit
-  - Node.js
-  - Docker
-platforms:
-  - linux
-  - self-host
-projectType: real-app
-difficulty: intermediate
-codebaseSize: large
-repoUrl: https://github.com/coollabsio/coolify
-links:
-  github: https://github.com/coollabsio/coolify
-  website: https://coolify.io
-bestFor:
-  - Self-hosted PaaS
-  - VPS deployments
-  - Docker-based stacks
-whyListed:
-  - One-click app + DB deploys
-  - Active dev
-  - Clear upgrade path from manual Docker
-caveats: []
-distribution:
-  channels: []
-source:
-  type: manual
-curation:
-  reviewed: true
-  reviewedBy: grove-bot
-  reviewedAt: "2026-06-13"
-  labels:
-    - hot
-  lenses: []
-visibility: keep

package/templates/default/data/records/gitea.yml

@@ -1,46 +0,0 @@
-kind: project
-name: Gitea
-slug: gitea
-description: Lightweight, self-hosted Git service — painless, single-binary, low-resource alternative to GitHub.
-category: DevOps
-tags:
-  - git
-  - forge
-  - self-host
-  - go
-stack: Go
-stacks:
-  - Go
-  - Vue
-platforms:
-  - linux
-  - self-host
-  - docker
-projectType: real-app
-difficulty: intermediate
-codebaseSize: large
-repoUrl: https://github.com/go-gitea/gitea
-links:
-  github: https://github.com/go-gitea/gitea
-  website: https://about.gitea.com
-bestFor:
-  - Self-hosted Git hosting
-  - Lightweight CI/CD integration
-  - Internal team forges
-whyListed:
-  - Single binary, easy install
-  - Mature, stable releases
-  - Active community
-caveats: []
-distribution:
-  channels: []
-source:
-  type: manual
-curation:
-  reviewed: true
-  reviewedBy: grove-bot
-  reviewedAt: "2026-06-13"
-  labels:
-    - mature
-  lenses: []
-visibility: keep

package/templates/default/data/records/hoppscotch.yml

@@ -1,47 +0,0 @@
-kind: project
-name: Hoppscotch
-slug: hoppscotch
-description: Open-source API development ecosystem — design, test, and debug APIs faster from a single interface.
-category: Web
-tags:
-  - api
-  - testing
-  - developer-tools
-  - vue
-stack: Vue
-stacks:
-  - Vue
-  - TypeScript
-  - GraphQL
-platforms:
-  - web
-  - desktop
-  - self-host
-projectType: real-app
-difficulty: beginner
-codebaseSize: large
-repoUrl: https://github.com/hoppscotch/hoppscotch
-links:
-  github: https://github.com/hoppscotch/hoppscotch
-  website: https://hoppscotch.io
-bestFor:
-  - API exploration
-  - REST/GraphQL/WebSocket testing
-  - Self-hosted team workflows
-whyListed:
-  - Lightweight, fast UI
-  - PWA + desktop builds
-  - Open-source Postman/Insomnia alternative
-caveats: []
-distribution:
-  channels: []
-source:
-  type: manual
-curation:
-  reviewed: true
-  reviewedBy: grove-bot
-  reviewedAt: "2026-06-13"
-  labels:
-    - hot
-  lenses: []
-visibility: keep