What shipped in v1.0
The first stable build of Modern Maps is out, and four patch releases have landed on top of it since. This is the note I should have written on the day it went up, plus everything that happened in the weeks after.
Modern Maps v1.0
The first stable build, and the four patches that followed it.
- 1.0.4Editor script off the front end. The 1.0.1 fix targeted the wrong field and never took effect. Tested to WordPress 7.0.
- 1.0.3Attribution badge. A small “Powered by Modern Maps” mark that auto-themes against the map background.
- 1.0.2Tile host migration and privacy docs. Tiles moved to tiles.modernmapswp.com; per-service disclosure and pasteable policy text.
- 1.0.1Smaller saved markup. Style spec rebuilt at runtime, plus an attribution background fix on custom-color maps.
- 1.0.0Initial release.
The map
Version 1.0 shipped the thing the whole plugin exists to do: a vector map that renders the moment you add the block. No API key, no Google Cloud Console, no billing account to attach. Tiles come from infrastructure I run, the renderer is MapLibre GL, and on the Light and Dark presets the fonts and sprites are served from that same infrastructure. The Standard preset is the one exception: it pulls its fonts and sprites from the Protomaps project directly.
Three style presets ship with it, Light, Dark, and Standard, and the map picks up colors from your active Gutenberg theme palette so it looks like it belongs on your site rather than pasted onto it.
The editor
The block is Gutenberg-native rather than retrofitted. Type /map, search a location, drag the pin, publish. Styling happens inline in the block sidebar, and what you see in the editor is what renders on the front end.
What the patches fixed
Most of 1.0.1 through 1.0.4 was weight and correctness rather than features.
Two separate releases went after the same problem: an editor-only script that was loading on public pages. The fix in 1.0.1 targeted the wrong block-registration field and quietly did nothing, which I did not catch until 1.0.4. Front-end pages with a map now load only the view script.
1.0.1 also stopped saving the full style specification into your post content. The style is reconstructed at runtime now, so saved block markup is meaningfully smaller, and existing posts migrate on their next save. The same release fixed an attribution background that rendered white on custom-color maps, caused by a lightness value being multiplied by 100 twice and clamping out of range.
1.0.2 moved tile delivery to tiles.modernmapswp.com and rewrote the External Services disclosure into a per-service block covering what each one is used for, when it fires, and what data it sends. There is now suggested privacy-policy text in Tools, Privacy, Policy Guide that you can paste into your own policy.
1.0.3 added a small “Powered by Modern Maps” badge in the corner of the map, which auto-themes against the map background.
What is next
Marker clustering, then a store locator. No dates.
You can install Modern Maps Lite from the WordPress.org plugin directory, or download the full plugin from modernmapswp.com, which is the build that accepts a Pro license key.