Opened 15 years ago

Closed 14 years ago

#12894 closed (fixed)

Not-so-nice anchor for section titles in docs.djangoproject.com

Reported by: anonymous Owned by: nobody
Component: *.djangoproject.com Version: dev
Severity: Keywords: model validation
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

On http://docs.djangoproject.com/en/dev/ref/models/instances/ the anchor for "Validating objects" is currently "#id1".
Other anchors in the Django doc are human readable. Cool URIs don't change (and I already referenced this anchor somewhere), but maybe it should change to "#validating-objects".

Change History (5)

comment:1 by Russell Keith-Magee, 15 years ago

Resolution: wontfix
Status: newclosed

I'm in complete agreement that the anchors aren't nice, but I'm not sure there is anything we can do about it. The #id1 tags are autogenerated by Sphinx, which is what we use to generate our documentation.

Please reopen if anyone knows enough Sphinx-fu to provide a workable solution.

comment:2 by Ramiro Morales, 15 years ago

Component: DocumentationDjango Web site
Resolution: wontfix
Status: closedreopened
Summary: Not-so-nice anchorNot-so-nice anchor for section titles in docs.djangoproject.com

I've tested this by generating the documentation locally with different relases of Sphinx and it gets solved by simply using version 0.6.

So, the solution for the docs.djangoproject.com site would be to upgrade the Sphinx component of the setup used there from 0.4.x (the version I suspect is being used currently). I don't know what else that migration would involve but I suspet it would also allow to drop a few hacks we are currently using in docs/_ext/djangodocs.py.

Reopening and changing Component field value.

comment:3 by Russell Keith-Magee, 15 years ago

milestone: 1.2
Triage Stage: UnreviewedAccepted

comment:4 by James Bennett, 15 years ago

milestone: 1.2

If upgrading djangoproject.com's Sphinx fixes this, then it's not a problem in Django itself and shouldn't be on a milestone.

comment:5 by Ramiro Morales, 14 years ago

Resolution: fixed
Status: reopenedclosed

This has been fixed at some point. Quite probably when the version of Sphinx used on doc.djangoproject.com was updated to 1.0.x.

Note: See TracTickets for help on using tickets.
Back to Top