formatting fix

Author: CommanderStorm

src/content/roadmap/martin/data-geoparquet/index.mdx

@@ -11,6 +11,7 @@ GeoParquet combines columnar storage efficiency with geospatial capabilities, en
 Leverages Apache Arrow for zero-copy processing and supports partitioned datasets in cloud storage.
 
 Key features:
+
 - Direct cloud storage access (S3, GCS, Azure)
 - Columnar data processing with predicate pushdown
 - Memory-efficient streaming for petabyte-scale data

src/content/roadmap/martin/data-mbtiles/index.mdx

@@ -11,9 +11,10 @@ Native support for serving tiles from MBTiles archives.
 Martin serves both vector and raster tiles directly from MBTiles files with automatic metadata extraction and TileJSON generation.
 
 Features:
+
 - Vector and raster tile formats (PNG, JPEG, WebP)
 - Automatic format detection
 
 GitHub Issues: [#494](https://github.com/maplibre/martin/issues/494)
 
-Documentation: [MBTiles Sources Guide](https://maplibre.org/martin/sources-files.html)
+Documentation: [MBTiles Sources Guide](https://maplibre.org/martin/sources-files.html)

src/content/roadmap/martin/data-pmtiles/index.mdx

@@ -12,8 +12,9 @@ PMTiles enables serverless tile serving directly from cloud storage (S3, GCS, Az
 Optimized for CDN distribution with minimal infrastructure requirements.
 
 Features:
+
 - Direct serving from cloud storage
 - Local and remote file support
 - CDN-friendly caching headers
 
-Specification: [PMTiles Format](https://github.com/protomaps/PMTiles)
+Specification: [PMTiles Format](https://github.com/protomaps/PMTiles)

src/content/roadmap/martin/data-postgis/index.mdx

@@ -12,9 +12,10 @@ Martin serves tiles directly from Postgres tables, views, and functions without
 Features automatic schema discovery, connection pooling, and optimized spatial queries.
 
 Key capabilities:
+
 - Table and function-based tile sources
 - Custom SQL queries for complex tiles
 - Automatic spatial indexing
 - Dynamic zoom level configuration
 
-Documentation: [Postgres Sources Guide](https://maplibre.org/martin/pg-connections.html)
+Documentation: [Postgres Sources Guide](https://maplibre.org/martin/pg-connections.html)

src/content/roadmap/martin/frontend/index.mdx

@@ -9,8 +9,8 @@ released: August 2025
 Our Frontend is a modern, React-based tool providing visual configuration tools, server monitoring, and interactive tile preview capabilities.
 It is designed to make Martin accessible to users who prefer graphical interfaces over command-line tools.
 
-
 ### Features:
+
 - [x] see basic metrics
 - [x] inspect tiles
 - [x] view styles with mapunik as an add-on
@@ -19,15 +19,15 @@ It is designed to make Martin accessible to users who prefer graphical interface
 
 #### Dark mode
 
-| <img width="100%" src="https://github.com/user-attachments/assets/6aee1f98-d098-45da-a76e-2d97c30635c0" />  | <img width="100%" src="https://github.com/user-attachments/assets/f32c1597-3b89-48eb-8488-e2220380ad42" />  |
-| ------------- | ------------- |
+| <img width="100%" src="https://github.com/user-attachments/assets/6aee1f98-d098-45da-a76e-2d97c30635c0" /> | <img width="100%" src="https://github.com/user-attachments/assets/f32c1597-3b89-48eb-8488-e2220380ad42" /> |
+| ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
 | <img width="100%" src="https://github.com/user-attachments/assets/2911f874-f8f8-4252-9d44-377e07b357be" /> | <img width="100%" src="https://github.com/user-attachments/assets/b4214069-8022-4d9a-b04c-ea02b924d0b3" /> |
 | <img width="100%" src="https://github.com/user-attachments/assets/9534c952-0241-492e-bee6-cf2ec49f6e24" /> | <img width="100%" src="https://github.com/user-attachments/assets/cc231e62-9061-4eda-9e37-1c992bcd2171" /> |
 
 #### Light mode
 
-|  <img width="100%" src="https://github.com/user-attachments/assets/6aee1f98-d098-45da-a76e-2d97c30635c0" /> | <img width="100%" src="https://github.com/user-attachments/assets/5a1ad7ad-ec10-49ae-a3df-0d17825fa991" /> |
-| ------------- | ------------- |
+| <img width="100%" src="https://github.com/user-attachments/assets/6aee1f98-d098-45da-a76e-2d97c30635c0" /> | <img width="100%" src="https://github.com/user-attachments/assets/5a1ad7ad-ec10-49ae-a3df-0d17825fa991" /> |
+| ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
 | <img width="100%" src="https://github.com/user-attachments/assets/c579d420-e1dd-43c1-8ddb-8a268ef7ac72" /> | <img width="100%" src="https://github.com/user-attachments/assets/17a1e5d3-4f23-4e0c-94e9-360a2b68c851" /> |
 | <img width="100%" src="https://github.com/user-attachments/assets/efbd6733-f9f9-48b1-9095-d14a44ff987c" /> | <img width="100%" src="https://github.com/user-attachments/assets/60b6fc69-e102-4fb6-8f7c-f17083b7fac7" /> |
 

src/content/roadmap/martin/martin-core-library/index.mdx

@@ -12,6 +12,7 @@ To publish a v1.0 release of martin, we had to decouple the release cycle of our
 This empowers future embedding tile serving in web applications, building custom GIS tools, and rapid prototyping of geospatial services.
 
 Key features:
+
 - Embeddable tile serving
 - Plugin system for custom sources
 - Full async/await support

src/content/roadmap/martin/observability/index.mdx

@@ -11,12 +11,14 @@ Provides real-time metrics, structured logging, and distributed tracing to ensur
 Integrates well with standard observability tools and platforms.
 
 Core components:
+
 - (released) **Metrics**: Prometheus-compatible metrics for requests, tiles, cache, and system resources
 - **Logging**: Structured JSON logs with correlation IDs and configurable levels
 - **Tracing**: OpenTelemetry support for request flow analysis
 - **Dashboards**: Pre-built Grafana templates for ops and business metrics
 
 Key metrics tracked:
+
 - Request rate, latency, and error rates
 - Cache hit ratios and tile generation times
 - Database connection pool and query performance

src/content/roadmap/martin/style-optimistation/index.mdx

@@ -6,6 +6,7 @@ status: in-progress
 ---
 
 Together with the [Techical Unversity of Munichs' chair of Big Geospatial Data Management](https://www.bgd.ed.tum.de/), we are currently working on a thesis where the next generation of vector tile performance from tileservers could come from:
+
 - At the minimum, the outcome of this initiative will be a documentation page detailing which aspects of vector tiles are not improving performance and why.performance
 - At best, the outcome will be a new optimised mode for serving styles and the data in a co-optimzed fassion.
 
@@ -28,7 +29,6 @@ Here are the optimisations that are currently planned for evaluation:
 | overlap reduction             | -               | for some layers like roads or pois at the higher zoom levels overlap is common. If one knows the style redundant data can be removed (storage layout)                              |
 | static generation             | static source   | extract semantics and generate a new, optimal [static instruction set for constructing the tile database](https://github.com/onthegomap/planetiler/tree/main/planetiler-custommap) |
 
-List of some possible optimisations. *full scan* means that this optimisation would require executing one operation over the whole table at minimum. *sampling* means that this data can be gathered by sampling approaches, but evaluating if a full scan could add context will have to be looked at. For sampling-based approaches, the resampling frequency for the dynamic sources noted in `\cref{access:dynamic}` needs to be determined via statistical approaches. The cases where no scan is necessary does not mean that it might not still be beneficial, for example for parameter tuning.
-
+List of some possible optimisations. _full scan_ means that this optimisation would require executing one operation over the whole table at minimum. _sampling_ means that this data can be gathered by sampling approaches, but evaluating if a full scan could add context will have to be looked at. For sampling-based approaches, the resampling frequency for the dynamic sources noted in `\cref{access:dynamic}` needs to be determined via statistical approaches. The cases where no scan is necessary does not mean that it might not still be beneficial, for example for parameter tuning.
 
 GitHub Issues: [#1757](https://github.com/maplibre/martin/issues/1757)

src/content/roadmap/martin/style-rendering/index.mdx

@@ -11,13 +11,15 @@ Enable Martin to render MapLibre styles server-side, producing raster tiles and
 Uses CPU-based rendering with optional GPU acceleration where available via [Maplibre-Native](/projects/native/)
 
 Core capabilities:
+
 - Raster tile generation from vector data using MapLibre styles
 - Static map API for custom image generation
 - Batch rendering for large-scale map production
 - Multiple output formats (PNG, JPEG, WebP, PDF, SVG)
 - High DPI support for print and retina displays
 
 Technical approach:
+
 - Full MapLibre style specification support
 - Headless operation for cloud deployment
 - Intelligent caching of rendered output

src/content/roadmap/martin/style-serving/index.mdx

@@ -8,6 +8,7 @@ released: April 2025
 
 Martin should be the only service that one needs to run a maplibre map.
 As such, we currently, support
+
 - Tiles
 - Fonts
 - Sprites