djangoproject.com.git/djangoproject/templates/base.html, branch issue-1630

Add djade linter and format templates.

2026-05-08T10:45:50Z

Allowed creation of site-wide banners via the admin interface.

2026-04-15T01:40:39Z

Fixes #1550. A banner requires a title, and optionally HTML body and CTA label/URL. A banner can be active or inactive, and only one can be active at a time. Banners can be previewed from the admin via the "View on site" options on a Banner's detail page. This initial implementation is intentionally minimal to provide a robust but flexible MVP, with the goal to gather feedback for future iterations. Future improvements could include: - Active since and until dates. - Flexible CTA URL handling, such as URL names or local URLs. Thanks to Sarahs for the reviews.

Removed the donation banner to reach the 2025 fundraising goal.

2025-12-31T15:45:38Z

Use CSS instead of JavaScript for floating warning

2025-12-30T13:07:01Z

Some of the functionality of the floating warning on unsupported and in-development documentation versions was implemented using JavaScript. This is longer necessary if we use the following approach with modern CSS: Attach the warning element the top of the page with `position: sticky`. This almost solves the problem, but we still have to scroll past header elements when an internal page link is clicked. This is achieved with a combination of the `:has` pseudo-class and the `scroll-margin-top` property. We apply `scroll-margin-top` to elements that can be scrolled to by their `id` attribute. This is done with responsive breakpoints to get appropriate spacing when the floating warning has one, two, or three lines of text. Thanks to `:has`, this only happens when a warning element is on the page. The modern CSS features used are widely-supported: - https://caniuse.com/css-has - https://caniuse.com/css-sticky - https://caniuse.com/mdn-css_properties_scroll-margin-top Other than making the primary CSS changes and removing the related JavaScript, this patch does the following: - Simplify the CSS so that the class on all floating warning elements implements the common rules and the CSS for the IDs on the elements implements the colors - Add a `z-index` to warning elements so that they always display in front of the header element - Move the floating warning element to the top of the page in the HTML - Remove the `body_extra` block that was only being used by the floating warning element - Add a new `before_header` block for the floating warning element Thank you to Baptiste Mispelon and Thibaud Colas for helping me arrive at this solution.

Created a DSF donate banner to encourage end of year donations.

2025-12-18T06:46:01Z

Added a management command to generate roadmap SVG

2025-12-04T08:07:44Z

--------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> Co-authored-by: Baptiste Mispelon

Removed PyCharm 2025 discount banner. (#2345)

2025-11-20T20:30:17Z

:pencil: Extend PyCharm discount end date to Nov 19

2025-11-11T14:08:26Z

Used underlined class instead of u element.

2025-10-30T04:42:51Z

Add underline to PyCharm discount message

2025-10-30T04:42:51Z

(Also requested by Catherine)