| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
All external links in the navigation used http and redirected to https. The PSF voting-member link used the pyfound.blogspot.de country domain, which redirects to pyfound.blogspot.com. The Python News item claimed it showed Python Insider posts only. It points at /blogs/, which lists every imported feed.
The News menu linked to the PSF, community and PyCon blogs, but not to blog.python.org itself.
There was a problem hiding this comment.
Updates the seeded sitetree navigation fixture to use canonical HTTPS URLs for external News dropdown links and corrects the “Python News” hint/description to better match what the destination page contains.
Changes:
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Follow-up to an audit of the News dropdown in fixtures/sitetree_menus.json.
Add Python Insider. The News menu linked to the PSF, community and PyCon blogs, but not to blog.python.org itself. New item pk 126, "Python Insider", sits directly under "Python News". Its siblings shift by one sort_order, so the menu reads: Python News, Python Insider, Community News, PSF News, PyCon News.
Scheme. Every external navigation link used http:// and redirected to https://. I verified each destination with curl and updated the six of them:
Wording. The Python News item (pk 96) said "Python Insider Blog Posts" and described itself as the Core Developer blog. It points at /blogs/, which lists every imported feed, so PSF blog entries appear there as well. The hint and description now describe that. The old wording moves to the new Python Insider item, where it is accurate.
Note: brochure.getpython.info returns 503 over both schemes. That is a separate problem with the destination site, so I left the item in place.
These fixtures are seed data. Production navigation lives in the database, so it needs the same edits applied there.