Scenario
Agencies will have the need to support the display of maps (points, lines, regions). The data may be dynamic or static in nature. The data may exist in Drupal or potentially outside of it on a URL. Maps need to be attractive and dynamic.
Challenge
Drupal supports a wide range of mapping solutions. These include map integrations, geocoding of addresses and the storing of map data. Unfortunately, none of them are present in GovCMS SaaS. This leaves the site builder with the task of integrating external libraries to render the maps.
Solution
A common solution is to use a map rendering library such as Leaflet or Google Maps. These solutions can be manipulated via a Javascript API to display the data as needed. Map data (points) can be stored directly onto an entity with fields. More complex data (lines and areas) can be represented with a format such as GeoJSON. If geocoding is required, then this can be done directly via AJAX calls from the client side. With these foundations, the site builder just needs to wire the solution together.
Outcome
Rendering maps can be achieved with a bit of knowhow and the use of third party libraries. The lack of Drupal modules is not so much of an encumbrance if the work is put in.