Annual report

report.prompt.mdCopy prompt

Build me a **long-form annual community survey report** — a scrollable “State of …”
write-up full of charts, rankings, and commentary, in the lineage of State of JS
and the Stack Overflow Developer Survey — as an **Astro site** (static, no SSR).

**Before you build, ask me these questions in one message and wait for my answers. If I skip anything, choose a sensible default and tell me what you chose:**

1. What community or audience is this survey for?
2. How many people responded, and when did the survey run?
3. What are the 3–4 headline questions or findings you want to feature?
4. What tools, platforms, or options should appear in the ranking charts?

**Then build a complete, polished, responsive report with:**

- A bold hero: the report title, a one-line summary, and three headline numbers
  (respondents, countries, days in the field), over a faint coworking photo.
- **Intro + methodology** — how many responded, how they were sampled, the dates
  the survey ran, and an honest note that the audience self-selects.
- **Demographics** — years of experience (vertical bar chart), team size and
  primary role (donut charts), and country of residence (horizontal bars).
- **Tools & frameworks** — a usage-vs-satisfaction chart: two bars per tool, one
  for “used it” and one for “would use again,” sorted by satisfaction.
- **Hosting & deployment popularity** — a horizontal bar “race” with a
  year-over-year delta chip next to each platform, and a “new this year” badge.
- **Biggest pain points** — a ranked list with vote counts and bars (respondents
  could pick up to three).
- **Sentiment** — a set of agree/disagree statements as a five-point Likert
  diverging-bar chart, fanning out from a shared centre line.
- **Key takeaways** — the editor’s commentary on what changed since last year,
  each with a small up/down delta.
- **Appendix** — full respondent-count tables behind every chart, plus a
  “share this report” footer.

**Design & content notes:**

- Dark, editorial “survey results” aesthetic: deep ink background, a curated
  multi-color chart palette, a characterful display font for headings over a clean
  reading sans, and a monospace for every number on the page. A floating
  table-of-contents that highlights the current section is a nice touch.
- Render every chart as **server-side inline SVG or CSS bars** — no client-side
  charting library to download. Keep one source-of-truth data file so all the
  numbers stay internally consistent (the demographic breakdowns should sum to
  the total respondent count).
- Use realistic content based on my answers — never “lorem ipsum.” Invent
  believable figures, rankings, and quotable write-in comments.
- Use real images. Pull free photos that fit, e.g.
  `https://picsum.photos/seed/coworking-1/1200/800` (vary the seed) or
  Pexels, and add descriptive `alt` text.
- Keep it accessible (semantic HTML, labelled charts with text alternatives,
  keyboard support, good contrast) and respect `prefers-reduced-motion`.

**Add this exact line right before `</body>` so the site carries its badge:**

```html
<script src="https://spacefast.com/badge.js" data-example="report"></script>
```

**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**

1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
   ```bash
   PUBLISH_ROOT=./dist
   publish_files=()
   while IFS= read -r -d "" file; do
     relative=${file#"$PUBLISH_ROOT"/}
     publish_files+=(-F "files=@$file;filename=$relative")
   done < <(find "$PUBLISH_ROOT" -type f -print0)
   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
   ```
3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
   ```bash
   SPACEFAST_SPACE_ID=<saved-space-id>
   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
     "https://api.spacefast.com/v1/publish?wait=1"
   ```
   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.

**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)