m038andClaude Opus 4.8
b0cb67a079
Surfaced during the front-end journal entry edit brainstorm; referenced by the entry-edit plan's Scope Boundaries. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H1FrCYNq6RXdGYbn5PFrhM
39 lines
2.5 KiB
Markdown
39 lines
2.5 KiB
Markdown
# Backlog
|
|
|
|
Ideas and improvements not yet planned or scheduled.
|
|
|
|
---
|
|
|
|
## Production — remaining items
|
|
|
|
- [ ] Set `twig.cache: true` in `user/config/system.yaml` on the server (do not commit — breaks local dev)
|
|
- [ ] Smoke test: submit one post via `/post`, confirm entry appears in dailies immediately (verifies cache-on-save with twig cache on)
|
|
- [ ] Confirm `/post` requires login — unauthenticated visitors must not be able to post
|
|
- [ ] Register at carto.com and review terms for production traffic
|
|
- [ ] Japan & Korea 2026 trip page: set `date_start`, add `cover_image`, upload GPX route file(s)
|
|
|
|
---
|
|
|
|
## Hero-image cleanup (journal)
|
|
|
|
The `hero_image` field was removed from the post form (journal heroes now come
|
|
from the first uploaded photo). Follow-up: purge the now-unused field from the
|
|
journal entity end-to-end.
|
|
|
|
- [ ] **Remove hero from the journal entity** — drop `hero_image` from the entry blueprint/template so journal entries no longer carry or reference it (journal rendering already uses `entry.media.images|first`)
|
|
- [ ] **Remove hero from posts + demo content** — strip `hero_image` frontmatter from existing journal entries and the `italy-2026-demo` seed content (`user/docs/demo/`), then re-run `make demo-load`
|
|
|
|
---
|
|
|
|
## Journal entry detail page
|
|
|
|
- [ ] **Retire the journal-entry detail page** — the trip/home feed already renders each entry's full body inline (`entry.content|raw` in `partials/entry-journal.html.twig`), so the standalone `entry.html.twig` route per journal entry is largely redundant. Consider removing the route/permalink for journal entries. **Journal only** — stories are full standalone pages and keep their detail view. (Surfaced during the front-end edit brainstorm; unrelated to edit/delete itself.)
|
|
|
|
---
|
|
|
|
## GPX Manager (`/gpx-manager`)
|
|
|
|
- [ ] **Polish the UI** — the current design is functional but bare; align with the Field Notes aesthetic, add better empty states, drag-and-drop upload area
|
|
- [ ] **Link from Admin2** — Admin2 is a compiled SPA so we can't inject a sidebar link; options: (1) add a link to the site's nav when logged in, (2) a bookmarklet, or (3) wait for Admin2 to support plugin-contributed sidebar entries
|
|
- [ ] **Komoot integration** — explore how to pull GPX routes directly from Komoot without a manual export step. Komoot has an API (`api.komoot.de`) that returns GPX for a tour given its ID. Could be: a field on the GPX manager where you paste a Komoot tour URL/ID and it fetches + saves server-side, or a script run via `make`. Worth researching auth requirements (public tours may not need auth).
|