# Add the rekopub.monoexp.com website and VERSION

Branch `feature/site` · version 1.1.0

## What changed

- **`site/`**: a one-page website for rekopub.monoexp.com, styled like monoexp.com (same stylesheet, colours and dark mode). It has a summary and features, the latest downloads for each platform with the version, build date and the commit they were built from, usage (flags, where books are saved, Kobo and reMarkable steps), and the licence with the Go libraries ReKoPub uses and their licences.
- **`VERSION`**: `1.1.0`. The deploy pipeline builds the binaries with it, and the page shows it. The code is the same as the old 1.0.1; the minor bump marks the rename, the new install path and the new download site.
- **`.goreleaser.yaml` removed**: the pipeline now builds the release archives, so there's one way to make them. `/dist/` is gone from `.gitignore`.
- **`README.md`**: Download links point to rekopub.monoexp.com, with stable file names (`rekopub_<os>_<arch>`, no version). "Releasing" explains that every merge into `main` rebuilds and publishes the site and binaries, and that `VERSION` sets the version. The project layout lists `site/` and `VERSION`.

## Notes

- This needs the `cli` kind from bajdev/devops `feature/cli-kind`, installed with its `sites.json` entry, plus the webhook on this repo, before this PR is merged. Otherwise nothing is published.
- `site/index.html` contains `@VERSION@`, `@DATE@`, `@COMMIT@` and `@SHORT@`, which the pipeline fills in. Opened straight from the repo, the page shows them as they are.
- The download files keep the same names in every release, so links to them always give the latest version. Older versions aren't kept on the site; tag `v<version>` and build from the tag to get one.
- Every merge republishes, even if `VERSION` didn't change: the binaries then have the same version but a newer commit, which the page shows.

## Testing

- Ran the devops `release` script from `feature/cli-kind` against this branch in a sandbox (a local bare remote instead of Gogs). It took 15 s, built all six archives and `checksums.txt` (`sha256sum -c` passes), and filled in every placeholder. The unpacked Linux binary prints `rekopub v1.1.0` for `-VERSION`; the Windows zip holds `rekopub.exe`, `README.md` and `LICENSE`.
- Served the published folder locally and checked the full page at 1280 px and 390 px wide. Fixed what that showed: licence names and inline code wrapping mid-word, long file names in the download table on phones (now stacked), and the long macOS command (now in a code block).
- `go test ./...` passes (no Go code changed).

## Screenshots

`desktop.png` and `mobile.png` show the top of the page as the pipeline publishes it.