[MapServer-dev] Updating OGC Features API templates

[Lime, Steve D (MNIT)]

Yeah, I guess we shouldn’t be distributing old, unsupported versions of other frameworks. If someone were really gung-ho I could still see multiple frameworks being supported though…

From: MapServer-dev <mapserver-dev-bounces at lists.osgeo.org> On Behalf Of Seth G via MapServer-dev
Sent: Tuesday, September 9, 2025 10:13 AM
To: Steve Lime <sdlime at gmail.com>
Cc: MapServer Devs <mapserver-dev at lists.osgeo.org>
Subject: Re: [MapServer-dev] Updating OGC Features API templates

This message may be from an external email source.
Do not select links or open attachments unless verified. Report all suspicious emails to Minnesota IT Services Security Operations Center.

________________________________
Maybe naming the folder "html-default-theme" and regularly updating this with MapServer releases would be more practical? It would allow us to switch frameworks if Bootstrap disappears, and not tie us to specific Bootstrap releases.

Old versions of the themes will always be available in branches in GitHub. I'm not sure how useful leaving old versions of the themes in the main branch would be. Leaflet 1.7.1 and Bootstrap 4.5.3 were both released in 2020.

It looks like several package managers won't be installing these themes by default anyway so it might be simpler for users to download the latest "html-default-theme".

--
web:https://geographika.net<https://geographika.net/> & https://mapserverstudio.net<https://mapserverstudio.net/>
mastodon: @geographika at mastodon.social<mailto:geographika at mastodon.social>

On Mon, Sep 8, 2025, at 11:03 PM, Steve Lime wrote:
I guess I'd favor saying html-bootstrap contains templates relative to the current major version of bootstrap but then I'd keep the older, version specific, ones as part of the repo. Maybe they don't get installed and are just there for reference - or a user could install by hand. The drag is that one needs to keep pace with Bootstrap releases. So, for now html-bootstrap would contain Bootstrap 5 templates and when version 6 comes out you'd create a html-bootstrap5 directory that wouldn't get installed and html-bootstrap would contain Bootstrap 6 files.

On Mon, Sep 8, 2025 at 12:46 PM Seth G via MapServer-dev <mapserver-dev at lists.osgeo.org<mailto:mapserver-dev at lists.osgeo.org>> wrote:
Hi devs,

I have made updated HTML templates for the OGC Features API in https://github.com/MapServer/MapServer/pull/7338 using Bootstrap 5.
I've added these to a new html-bootstrap5 folder, but maybe it is better to replace the current files in the html-bootstrap4 folder and rename it html-bootstrap (so it is not tied to a specific version)?

Advantages of this approach are fewer files to deploy, and users get updated templates when updating MapServer versions.
Disadvantages are users who have set OGCAPI_HTML_TEMPLATE_DIRECTORY to the html-bootstrap4 folder will need to update their CONFIG files and users may also prefer to keep older versions of templates (although then can save a copy locally).

My preference is to replace, and rename the folder html-bootstrap.

There are also plans to make installing the templates optional - see https://github.com/MapServer/MapServer/pull/7309

Thoughts and comments welcome,

Seth

--
web:https://geographika.net<https://geographika.net/> & https://mapserverstudio.net<https://mapserverstudio.net/>
mastodon: @geographika at mastodon.social
_______________________________________________
MapServer-dev mailing list
MapServer-dev at lists.osgeo.org<mailto:MapServer-dev at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/mapserver-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20250909/35fae5c4/attachment-0001.htm>