Multiple fixes to Maps Frontend

[zacharlie]

We have deployed our own tailored frontend application for the G3W suite and as a result, it is difficult to identify what issues can be rectified from within our own instance and what issues are platform dependant and need to be addressed in the upstream repo.

Because there are a large number of these issues, I propose that we list these all within this issue and identify whether an issue has been raised with the upstream repo by marking the issue with a 📡 symbol, or if it is a local issue we can mark it with a 📍 icon. If an upstream issue has been rectified using a local "hack", we can mark it with a 📻 icon. You should be able to edit my comment with the master list below.

Example results:

• [ ] Local issue not rectified 📍
• [x] Remote issue raised in upstream repo📡
• [x] Upstream issue which has been corrected on local deployment 📻

[zacharlie]

Typos/ editorial improvements 📻

• [ ] powerd by => powered by (this typo is also present as an environment variable)
• [ ] ABOUT IT => ABOUT (Front end category)
• [ ] ABASTRACT => ABSTRACT (map metadata)
• [ ] Adminstration => Administration (frontend links)
• [ ] Access to backgeng admindistrations
• [ ] Login to go backend administration system => Login (frontend#login) 📍 To me, the "backend system administration" is implicit in the login. Regular users may need to use this login for permission controlled content, so leaving out the "backend" statements is advised
• [ ] Thematic Groups => Categories (frontend#maps)
• [ ] €Credits => 🛈 Info + allow this modal content to be customised via the admin interface

Improve/ review site descriptions 📍

I added some project-specific boilerplate to https://maps.wbr.kartoza.com/en/admin/generalsuitedata/

We may want to improve this content and I advise review by @NyakudyaA and @gubuntu

Add maps 📍

Because maps are QGIS project specific, and the UI is suited/ optimised to the curation of multiple content groups, having a single map makes the platform seem incomplete. Some very basic default maps have been added to attempt to offset this, but more may/ should be added which are more suited to client needs.

Basemaps 📍

• [ ] Change basemap thumbnails to be uniform square images 📍
• [ ] Add additional basemaps (for multiple map groups) 📍
• [ ] Options for "No basemap" to support different colors

Elements 📍

• [ ] Change frontend header (title+subtitle) fonts/ add stroke/ halo/ dropshadow (depending on the background, this is not always easily legible, so i would at least add a stroke setting to the current elements) 📍
• [ ] Remove Powerd By GIS3W? (optional, env setting) 📍

Platform 📡

• [ ] Front end maps use the default path and not the alias, e.g. https://g3w.example.com/en/map/group/qdjango/4/ 📡
• [ ] Map service should support url rewrites for aliases, e.g. https://g3w.example.com/map/alias/ows 📡
• [ ] frontend state/ link/ route management 📡 - The frontend state is not managed by routes, so site.tld/login will simply load site.tld/# with the default state and require manual navigation to login. This is not a very good UX. 📡
• [ ] Auth redirect 📡 - when trying to access permission controlled content, the default (middleware) auth page is used, rather than the frontend auth page. The UX should be uniform across services. 📡
• [ ] Add CSS variables for frontend to admin interface, or custom stylesheet config
• [ ] Add "Featured" maps category on web map frontend, so that "featured" maps are easily accessible, rather than being nested in groups (perhaps use carousel/ pagination) 📡
• [ ] Admin interface user profile/ logout button should be at far right of navbar (right of the home button), not between other elements to be more consistent with web standards 📡

Platform map functions 📡

• [ ] Get QGIS layer metadata from project 📡
• [ ] Change "source" to "driver", and collapse attribute field details table, rather replacing this content with QGIS project metadata such as Title and Abstract etc. 📡
• [ ] Toggle visibility/ hide layer attribute fields 📡
• [ ] Support QGIS "map themes" 📡
• [ ] Reorder/ define custom ordering for maps in group 📡

Platform print functions 📡

• [ ] Use current map scale and extent 📡
• [ ] Allow user defined scale 📡
• [ ] Use currently active map layers or select theme (not the default layers in the project) 📡
• [ ] The print modal should automatically be closed or show output thumbnail. Options for closing the print modal should be more apparent or a "back to map" button should be added. 📡

[zacharlie]

@NyakudyaA , @gubuntu, @lucernae, could you review these issues and identify any problems or gaps with the issues listed.

If you could identify what issues are local/ upstream/ are upstream issues we can patch that would be great so that we can start pushing issues to the upstream repo and letting them make improvements to the platform. I have currently just guessed at what is a locally resolvable issue and the list above may not be accurate.