{"id":"6a283f20d16072619b0883f3","title":"2026 06 09 Issue 188","path":"how-to/committee/release-notes/2026-06-09-issue-188","contentMarkdown":"# 09-Jun-2026 — self-host Font Awesome and improve venue map editing [#188](https://github.com/nbarrett/ngx-ramblers/issues/188)\n\n## [build 676](https://github.com/nbarrett/ngx-ramblers/actions/runs/27219444046) — [commit 8a770e4](https://github.com/nbarrett/ngx-ramblers/commit/8a770e45bd41c4bc1ca01fe7c1dd0e2173426954)\n\n_____\n\n## Why\n\nThe Font Awesome Kit JS snippet was loaded on every page across all group\nsites, counting toward the free plan's 10,000 monthly pageview limit. With\n10+ deployed sites this was about to be exceeded. The Kit was only needed for\nthe Leaflet venue map markers - every other icon already used the bundled\n`<fa-icon>` SVG component, which never touched the Kit.\n\n## What changed\n\n**Self-host Font Awesome (removes the Kit dependency)**\n\n- Removed the `kit.fontawesome.com` `<script>` from `index.html`.\n- Added `@fortawesome/fontawesome-free` CSS (already a dependency) to the\nAngular `styles` build, so the webfont is served from our own origin with\nno pageview counting and no external fetch.\n\n**Unify the map pin icons with the venue-type source**\n\n- The map's `venue-map-selector` now derives each pin's icon from the venue\ntype's own `IconDefinition` (`${prefix} fa-${iconName}`), the same source\nthe Type dropdown uses, instead of a separate hardcoded list that only\ncovered a subset of types and fell back to a `?`.\n- Updated two FA6-renamed icons (`fa-beer` -> `fa-beer-mug-empty`,\n`fa-coffee` -> `fa-mug-saucer`) and removed dead unicode-mapping code.\n\n**Live-preview the edited venue's pin from the Type dropdown**\n\n- The marker for the venue being edited now reflects the selected type and\nupdates immediately when the dropdown changes, in both the admin venue\neditor and the walk venue editor.\n\n**Reposition venues by dragging the map pin**\n\n- The edited venue's pin is now draggable. Dropping it looks up the postcode\nfor the new point and feeds the new lat/lon/postcode back to the form.\n- Clicking the map no longer starts a separate new venue while an existing\nvenue is loaded - that flow was unrelated to the venue being edited and was\nconfusing. Click-to-create still works when starting fresh with no venue\nloaded. The map's helper text now reflects the current mode.\n\n## Follow-up (manual)\n\n- The Font Awesome Kit account can be closed once this is deployed to all\nenvironments; nothing in the code references it anymore.","contentHtml":"<h1>09-Jun-2026 — self-host Font Awesome and improve venue map editing <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/188\">#188</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/27219444046\">build 676</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/8a770e45bd41c4bc1ca01fe7c1dd0e2173426954\">commit 8a770e4</a></h2>\n<hr>\n<h2>Why</h2>\n<p>The Font Awesome Kit JS snippet was loaded on every page across all group\nsites, counting toward the free plan&#39;s 10,000 monthly pageview limit. With\n10+ deployed sites this was about to be exceeded. The Kit was only needed for\nthe Leaflet venue map markers - every other icon already used the bundled\n<code>&lt;fa-icon&gt;</code> SVG component, which never touched the Kit.</p>\n<h2>What changed</h2>\n<p><strong>Self-host Font Awesome (removes the Kit dependency)</strong></p>\n<ul>\n<li>Removed the <code>kit.fontawesome.com</code> <code>&lt;script&gt;</code> from <code>index.html</code>.</li>\n<li>Added <code>@fortawesome/fontawesome-free</code> CSS (already a dependency) to the\nAngular <code>styles</code> build, so the webfont is served from our own origin with\nno pageview counting and no external fetch.</li>\n</ul>\n<p><strong>Unify the map pin icons with the venue-type source</strong></p>\n<ul>\n<li>The map&#39;s <code>venue-map-selector</code> now derives each pin&#39;s icon from the venue\ntype&#39;s own <code>IconDefinition</code> (<code>${prefix} fa-${iconName}</code>), the same source\nthe Type dropdown uses, instead of a separate hardcoded list that only\ncovered a subset of types and fell back to a <code>?</code>.</li>\n<li>Updated two FA6-renamed icons (<code>fa-beer</code> -&gt; <code>fa-beer-mug-empty</code>,\n<code>fa-coffee</code> -&gt; <code>fa-mug-saucer</code>) and removed dead unicode-mapping code.</li>\n</ul>\n<p><strong>Live-preview the edited venue&#39;s pin from the Type dropdown</strong></p>\n<ul>\n<li>The marker for the venue being edited now reflects the selected type and\nupdates immediately when the dropdown changes, in both the admin venue\neditor and the walk venue editor.</li>\n</ul>\n<p><strong>Reposition venues by dragging the map pin</strong></p>\n<ul>\n<li>The edited venue&#39;s pin is now draggable. Dropping it looks up the postcode\nfor the new point and feeds the new lat/lon/postcode back to the form.</li>\n<li>Clicking the map no longer starts a separate new venue while an existing\nvenue is loaded - that flow was unrelated to the venue being edited and was\nconfusing. Click-to-create still works when starting fresh with no venue\nloaded. The map&#39;s helper text now reflects the current mode.</li>\n</ul>\n<h2>Follow-up (manual)</h2>\n<ul>\n<li>The Font Awesome Kit account can be closed once this is deployed to all\nenvironments; nothing in the code references it anymore.</li>\n</ul>\n"}