update doc tooling to Zensical

[tomkralidis]

This PR updates doc build/tooling from MkDocs to Zensical (rationale).

Notes:

• this is a first pass, so improvements are welcome :)
• does not currently address i18n (for Portuguese cc @doublebyte1)
• removes PDF support (we can open a dedicated issue (pending Support mkdocs-with-pdf plugin functionality zensical/backlog#25) to restore PDF support once this PR is merged)
• removes termynal support (doesn't seem to work)

[justb4]

Yes, I read the rationale, was not aware. Will impact quite some projects, but mkdocs 2.0 is an uncertain (FOSS) path.
Think will miss first the Material design, or is that in here? Zensical are its authors btw.
And i18n? We can do without termy..

The "Doing Geospatial in Python" has already been done, result here:
https://geopython.github.io/geopython-workshop/ IMHO a bit barren, but maybe we should also go for a more lighter "text web". But why not, as a start, embellish later...I'll go with any flow..

[tomkralidis]

@justb4 good points. The critical path is to ensure a safe arrival into Zensical before things get too stale in MkDocs proper. Note that the I've updated the PR to match the pygeoapi blue in the theming.

[doublebyte1]

Yes, I read the rationale, was not aware. Will impact quite some projects, but mkdocs 2.0 is an uncertain (FOSS) path. Think will miss first the Material design, or is that in here? Zensical are its authors btw. And i18n? We can do without termy..

The "Doing Geospatial in Python" has already been done, result here: https://geopython.github.io/geopython-workshop/ IMHO a bit barren, but maybe we should also go for a more lighter "text web". But why not, as a start, embellish later...I'll go with any flow..

@justb4 I think internationalisation is now supported in the core, so we don't need a plugin.

[geographika]

Thanks for the heads-up @tomkralidis. I'll look at following this update path with the MapServer workshop. I was never a fan of termynal anyway!

Issues like the mkdocs struggles highlight how good it is for a project to be part of something like OSGeo with PSCs and CoCs.

[doublebyte1]

• 1 . I have added the update to support Portuguese translation on this branch: https://github.com/geopython/diving-into-pygeoapi/tree/pr-223

[doublebyte1]

Maybe also add pip3 install --upgrade pip?

[tomkralidis]

• 1 . I have added the update to support Portuguese translation on this branch: https://github.com/geopython/diving-into-pygeoapi/tree/pr-223

@doublebyte1 can you PR your branch (rebased against latest main, which includes this PR/merge)?