Walk co-ordinators now have one place to see the state of the whole walks programme rather than piecing it together from the walks list. A Programme Overview groups walks by status, with a row of headline counts across the top that take you straight to that set of walks when you click them. A Programme Calendar shows the same walks by month or week, coloured by status, grade or leader, with group events alongside them. A Programme Map plots the whole programme, coloured by status and filterable to one status at a time. You can move between all of them without going back to the menu, and the date range you are looking at follows you across.
\nWalk leaders get their own view for the first time. Until now the only way for a leader to find their own walks was to know to use advanced search with the leader filter set to themselves, and Walk Admin was closed to anyone without the walk administrator setting. My Walks is open to any walk leader, reachable in one step from the walks page, and shows their upcoming walks and anything still outstanding on them.
\nAll of this adapts to how a group populates its walks. Groups whose walks come from Walks Manager see draft and published walks, where draft walks were previously indistinguishable from published ones. Groups creating walks on the website see the full sequence from awaiting a leader through to published. Nothing needs configuring and nothing appears that cannot work in the current mode. The views also follow whatever a group calls its walks page, so a site using go-walking gets go-walking/admin rather than being forced onto a fixed path.
\nThe Walk Admin page itself is now built from editable action buttons in the same way as the main admin area, so its tiles, wording, icons and colours can be changed on the site instead of only in code. Help text a group had already written is carried across, while wording describing the withdrawn bulk import route is discarded, since importing is now from a CSV file only.
\nSeveral fixes elsewhere came out of the same work. The events count badge on the walks page no longer grows taller than the controls beside it. Index maps no longer fit to every location in the index, so a single far-flung entry such as a walking weekend in Keswick no longer zooms the map out to the whole country and squashes everything else into a huddle, and the Map Height slider in the index editor now does something: the map can be sized by dragging it to where you want, in the editor preview, the way the walks map already works. Choosing "Both" on a linear walk shows both ends straight away rather than after clicking around the other options. And dropdowns in the sticky toolbars are no longer painted through by walk card maps, their zoom controls and the edit button.
\nNew Programme Overview grouping walks by status, with clickable headline counts and the filter held in the web address so a view can be bookmarked or sent to someone else
\nNew Programme Calendar with a compact month grid and a roomier Weeks view, both covering the whole month, coloured by status, grade or leader, showing group events alongside walks and a key naming the actual grades or leaders on screen
\nThe Weeks view gives each week its own row, headed with its dates and how many walks fall in it, with taller days and walk titles shown in full rather than cut off
\nNew Programme Map showing the whole programme coloured by status, filterable to a single status, with map options hidden until you want them
\nNew My Walks view for walk leaders, reachable without the walk administrator setting and linked from the walks page
\nWalk Admin and My Walks follow the group's own walks page address instead of a fixed path
\nDraft walks from Walks Manager are identified as Draft instead of being counted as published, and a leader's draft walk counts as outstanding on My Walks
\nThe programme opens on all future dates by default, with Future, Past and All available where there are events on both sides of today
\nGoing back from a walk names the view it returns to and takes you there with the date range you had set
\nPaging the programme and moving between calendar periods keep your place on the page
\nWalks awaiting a leader, awaiting details or missing a location are no longer separate walks list filters, since the Programme Overview covers them properly
\nThe events count badge no longer stretches the walks toolbar; long messages truncate and show in full on hover
\nIndex maps can be set to hold a chosen view rather than always fitting to every location
\nMaps no longer fall back to a Kent centre on sites that have not set one
\nThe Map Height slider in the index editor now works, and the map can be sized by dragging it in the editor preview
\nChoosing "Both" on a linear walk fits to both ends on the first click, and going back to Start no longer leaves the finish marker behind
\nDropdowns in the sticky toolbars open above walk card maps and their controls instead of being painted through by them
\nThe primary hostname placeholder in environment setup no longer suggests a particular group's domain
\nwalk-programme-overview, walk-programme-calendar, walk-programme-map, walk-leader-dashboard and walk-programme-view-selector components added under pages/walks, with date-range-selector, date-range-direction-selector, walk-programme.service and scroll-position.service
hasWalksAreaSubPath in app-routing.module.ts consumes the area segment when followed by admin or my-walks, so both the group's own area path and the literal /walks resolve. WALKS_ADMIN_SEGMENT, WALKS_LEADER_SEGMENT, walksAdminPath() and walksLeaderPath() are the single source for these paths
programmeSummary derives status, counts and a page of results in one aggregation with $facet, so counts and list always agree and the whole programme is never loaded into request memory
ProgrammeOverviewStatus.DRAFT is derived from groupEvent.status only for records whose source is walks-manager. Locally created events default to WalkStatus.DRAFT, so an unscoped rule would have reported every local walk as draft. displayedWalkProgrammeStatus applies the same precedence as the aggregation, which it previously did not, leaving the calendar and overview disagreeing
openWalkViewFor / openWalkEditFor / returnToPreviousView on WalkDisplayService replace inline navigation, drop inherited query parameters and record the origin. walkViewLink() no longer assigns viewReturnUrl from inside a template binding, which had been overwriting the remembered origin on every change detection pass
section-toggle renders the view switcher, calendar controls, date range presets and map status filter, replacing four separate hand-rolled button groups. It now coerces fullWidth and disabled with booleanAttribute, since written as bare attributes they passed the empty string and never applied, and its imposed margin-bottom is gone
relativeDay() on DateUtilsService and defaultProgrammeRange() in search.model.ts centralise relative dates and the default range, the latter derived from the All Future Dates preset so the two cannot disagree
Migration 20260802120000-seed-walk-admin-action-buttons seeds the action buttons per environment, resolving the walks area from page content, and declines to carry across help text describing the withdrawn bulk import route. Guarded and idempotent
walk-search.ts: the inline alert sizes to content rather than taking an equal share of the toolbar row, with a search-alert-inline class above the large breakpoint. The alert markup was duplicated between the toolbar and pagination cases, which is how they got out of step, and is now one ng-template
Index maps honour autoFitBounds alongside the other map row types, the editor preview bypasses the session view cache, and the auto-fit caption is settable per host
The calendar builds CalendarWeek rows from the same day list in both modes, so Month and Weeks share one set of day cell markup and one navigation step of a month, rather than each mode having its own range, title and stepping rules
Index map config uses mapHeight like map rows and area map rows do, instead of its own height field that the shared map controls never wrote to. Pages saved before this have their stored height copied to mapHeight when defaults are applied, on both the view and edit paths, and written back on next save. IndexRowConfig now refers to IndexMapConfig rather than being a hand-copied duplicate that had fallen behind. Height changes resize the existing map rather than tearing it down and rebuilding it, and resizing follows the pointer on a frame
map-edit.ts rebuilds the map when showCombinedMap or endLocationDetails changes, not only locationDetails. Start to Both previously changed neither of the watched inputs, so nothing fired until another option was clicked
Leaflet containers and map wrappers are isolated so their tile pane, controls, markers, popups and overlay compete within their own map rather than at page level from 200 to 10000. The sticky toolbar sits at 1030: above ordinary content and the edit overlay, below modals, the datepicker and the full screen map
\nThe hard-coded [51.25, 0.75] centre is removed from sixteen places across index maps, area maps, route maps, the map editors and the page transformation engine. Centre and zoom come from MapDefaultsService, using the group's configured centre and falling back to a UK-wide view. Other Kent-specific defaults removed with it: the areas API region, the area map coordinate fields, the legacy redirect domain, the migration path and the CLI S3 bucket examples