Open zacharlie opened 3 years ago
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 advisedThematic Groups
=> Categories
(frontend#maps)β¬Credits
=> π Info
+ allow this modal content to be customised via the admin interfaceI 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
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.
Powerd By
GIS3W? (optional, env setting) πhttps://g3w.example.com/en/map/group/qdjango/4/
π‘https://g3w.example.com/map/alias/ows
π‘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. π‘@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.
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: