We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C++ API URL:
https://api.qgis.org/api/3.34/classQgsAbstract3DRenderer.html
It contains api twice, which seems redundant. Is that a conscious choice?
api
Python API URL:
https://qgis.org/pyqgis/3.34/core/QgsAbstract3DRenderer.html
So no API sub domain. If the former has an api subdomain, it seems the latter should too. Or am I wrong?
Nothing at api.qgis.org
If I go directly to api.qgis.org, that redirects to https://qgis.org/download/.
If there is no page at the root of the subdomain, I would argue its not a good case for even having/using a subdomain. Or am I wrong?
No response
The text was updated successfully, but these errors were encountered:
I just read the original call for proposals, for the website overhaul: https://blog.qgis.org/2023/10/03/call-for-proposals-qgis-website-overhaul-2023-2024/.
I noticed that both the Python API and C++ API were at the same addresses before the overhaul.
Phase 3 is called "Auxiliary sites migrations".
Is Phase 3 done with? If not, perhaps phase 3 is concerned with my question/suggestion.
Sorry, something went wrong.
Yes we will address these type of issue in phase 3, thanks!
No branches or pull requests
Feature Description
C++ API URL:
It contains
api
twice, which seems redundant. Is that a conscious choice?Python API URL:
So no API sub domain. If the former has an api subdomain, it seems the latter should too. Or am I wrong?
Nothing at api.qgis.org
If I go directly to api.qgis.org, that redirects to https://qgis.org/download/.
If there is no page at the root of the subdomain, I would argue its not a good case for even having/using a subdomain. Or am I wrong?
Reference to Feature
No response
The text was updated successfully, but these errors were encountered: