Files
intotheeast-com/docs/working/backlog.md
T
m038 877d29b2b4 Merge branch 'feat/journal-post-form'
# Conflicts:
#	Makefile
#	docs/working/backlog.md
#	user
2026-07-08 00:10:14 +02:00

3.6 KiB
Raw Blame History

Backlog

Ideas and improvements not yet planned or scheduled.


Production — remaining items

  • Prod Twig prod-mode (cache: true, debug/auto_reload: false) — applied as a per-environment override via make remote-apply-env-prod (source: deploy/env/prod/system.yaml); committed system.yaml stays 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 — verified on prod (returns the login gate to unauthenticated visitors)
  • Register at carto.com and review terms for production traffic
  • Update GRAV_VERSION in .env.prod to 2.0.4 (was stale 2.0.0-rc.10; fixed on the running server via self-upgrade, but a future fresh install would repeat the RC)
  • git-sync on prod: install, add encrypted token, apply folders: fix, enable after first content round-trip

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.)

Content quality — luxury improvements (much later)

  • Re-import pixelfed photos at full resolution — the current import pulled pixelfed's optimised web renditions, so imported images cap at ~1440px on the long edge (portraits are 7001200px wide). This is fine for the feed and 1x banners, but the retina cover 2x only kicks in for genuinely wide (≥1440px) sources, so auto-picked trip banners are currently 1x-only. Find the original high-quality versions in the local filesystem and re-import them (or point the pipeline at the originals rather than the pixelfed web renditions). Purely a quality upgrade — no functional gap; future content shot/stored at full res won't have this ceiling.

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).