support dataset specific templates (#1857)

[tomkralidis]

Overview

Adds support for dataset specific templates.

Related Issue / discussion

Fixes #1857

Additional information

Dependency policy (RFC2)

• I have ensured that this PR meets RFC2 requirements

Updates to public demo

• I have ensured that breaking changes to the pygeoapi master demo server have been addressed
  • https://github.com/geopython/demo.pygeoapi.io/blob/master/services/pygeoapi_master/local.config.yml

Contributions and licensing

(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)

• I'd like to contribute [feature X|bugfix Y|docs|something else] to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution
• I have already previously agreed to the pygeoapi Contributions and Licensing Guidelines

[webb-ben]

This all looks good to me.

One thing that remains a bit opaque in the documentation (and without a tangible example) is what is required in the content of a dataset specific template.

Is this template able to inherit the header and footer in _base.html? Or does it require a full HTML template?

[tomkralidis]

This all looks good to me.

One thing that remains a bit opaque in the documentation (and without a tangible example) is what is required in the content of a dataset specific template.

It is expected that a developer adding a custom template would review an existing default template to better understand the scope of the UI functionality for a given HTML render.

Is this template able to inherit the header and footer in _base.html? Or does it require a full HTML template?

This is at the developer's discretion (similar to custom templates at any level).

Having said this, I've added some additional info to the docs.