Replymessage unavailable
The problem I see with those links is that they are the auto-translated from the Qt/C++ documentations.
Long time ago we had a similar discussion that between only having a few docs that we wrote by hand, and having some half-backed translated ones from Qt/C++, we opted for the last.
Addressing that type of fixes is very difficult because we might need to add corner cases in the doc translator.
This open a new question: does it make sense to replicate the documentation of something non-python specific in the qt for python docs?
That precisely contains some CMake things that make no sense in the Python world, that's why we decided to have Tutorials and examples on that topic:
https://doc.qt.io/qtforpython-6/tutorials/index.html#quick-qml-basic-tutorials
As you can see, your links only comes from the fact that you are probably using the "search" functionality, instead of using the grid categories from the main page: https://doc.qt.io/qtforpython-6/index.html which is what we have manually crafted.
If your answer is "But I want to have a Qt Quick best practices page with python code" that needs to be extrapolated of ALL the overview pages, and other things that Qt/C++ has.
Sadly, we are a small team of 5 people (2 full times on qt for python, and 3 with half-time working on the project), that really cannot be done with the current configuration,
but it's a super simple way of start contributing to the project, because finding the most important overview pages, manually updating them, and avoid doing the auto-generation might be the only way.
Plan B is for you (and everyone else) to report which overviews pages needs to be manually updated, so we can create new tutorials on that topic.