qgis2web VS OpenLayers3

There is qgis-server but if the content is static you can probably get by with https://plugins.qgis.org/plugins/qgis2web/

There's a QGIS plugin qgis2web that will take your QGIS project and create an HTML file out of it. I've used it once or twice and there were a couple of issues but I can't tell whether it's due to the plugin or my ignorance.

I think the easy option might be qgis2web plugin. Not quite sure it works exactly, but my understanding is it really simplifies the development process. Might be worth having a look https://github.com/tomchadwin/qgis2web

If you already / Once have your squares with data, then it's only displaying them on a map. QGIS2Web, Openlayers, Mapbox or CARTO can be some ways to start but if you want user interaction you'll probably have to code it yourself. Bokeh can probably be used for that too (Mapping geo data) but you'll probably have less liberty than in JS.

I suggest you start your research by looking into qgis2web (https://plugins.qgis.org/plugins/qgis2web/). Load your data into qgis, hit the qgis2web button, you'll have that map as a webpage.

You probably know this, but in Google Maps at least, you can use browser zoom (ctrl/cmd +/-) to change the size of labels without zooming into the actual map.

------

Speaking of maps, I got to work a fun zoom project a few years ago: https://map.fieldmuseum.org/

We used https://openlayers.org/ and thought long and hard about how to best handle zooming and variable levels of information density & visual hierarchy. If you zoom all the way out, we just highlight where the building is relative to the surroundings. As you start to zoom in, we start to highlight major exhibitions and entrances. Then as you zoom in more, we start showing recommended paths, smaller exhibitions, etc. The label sizes try to scale up and down at each level, smoothly, in order to balance readability and density.

Eventually you can reach the max zoom level and the labels will just grow bigger and bigger, but the SVGs dynamically shrink so they remain pictograms and not just contextless-lines.

Then if you keep going, you eventually find microscopic easter eggs :)

The code is pretty jank (and abandoned), but it's FOSS vanilla JS/HTML/CSS, and the only dependency is on OpenLayers: https://github.com/arcataroger/openlayers_indoor_map

In order to display the GeoJSON features on a map, we will use OpenLayers, which is a very powerful open-source mapping library that is also very simple to use.

OpenLayers is available via the ol npm package, offering developers a powerful toolkit for creating sophisticated maps. Here is a JavaScript implementation that utilizes OpenLayers to showcase a map:

Official Website: https://openlayers.org/

For web maps I'd strongly recommend using OpenLayers. While it's less convenient to get started with compared to the alternatives it's also much more feature-complete and you'll likely hit a ceiling in terms of functionality much later than you would with the others.