Opened 3 weeks ago

Closed 2 weeks ago

#36736 closed Cleanup/optimization (invalid)

Please restore h-rules on the docs home page, which were removed in the 4.2 docs.

Reported by: George Chang Owned by:
Component: Documentation Version: 4.2
Severity: Normal Keywords: h-rule pedantic
Cc: George Chang Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

This:
https://i.imgur.com/659rSpL.png
looks so much better than this:
https://i.imgur.com/IGk3iQS.png

in my opinion. The h-rules are absent from 4.2 onwards also. Is there any particular reason why they were removed?

Change History (1)

comment:1 by Natalia Bidart, 2 weeks ago

Easy pickings: unset
Resolution: invalid
Status: newclosed

Hello George Chang, and thank you for your interest in improving Django.

It took me a bit of investigation to understand the underlying cause. In the future, providing any initial analysis or context you have already uncovered would be very helpful, as it can speed up the process for everyone.

In this case the change is not in Django itself. Starting with Docutils 0.17, the HTML5 writer began emitting semantic tags like <section> instead of the older <div class="section"> structure. Sphinx adopted that change and the Django documentation picked it up when the docs toolchain was updated. Because of that, some of the CSS in the djangoproject.com theme that targeted the old structure no longer applies (see https://github.com/django/djangoproject.com/blame/ecfa16f2fd51c412b2dc8de34036bdad3b2c9a9b/djangoproject/scss/_style.scss#L322 for reference).

The styles for the Django docs live in the djangoproject.com repository, not in Django core (and this tracker is for Django core issues only). If you would like to propose adjustments to restore the horizontal separators, please open an issue or pull request on: https://github.com/django/djangoproject.com/issues

https://github.com/django/djangoproject.com

Thanks again for the report and for helping improve the documentation experience.

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