| Age | Commit message (Collapse) | Author |
|---|
|
Co-authored-by: Paolo Melchiorre <pmelchiorre@rippling.com>
|
|
|
|
* Synced webpages from sitemap to Document model for search.
* Removed is_searchable from blog Entry model.
|
|
Co-authored-by: Paolo Melchiorre <pmelchiorre@rippling.com>
|
|
|
|
|
|
- Serve from a view, nginx is not going to handle this for us.
- Make clear what should be reported to the security@djangoproject.com
and what should be reported to the website working group
- Downgrade security.txt expiration test to a warning instead of a hard
fail.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It provides a cleaner and easier to read experience, comparing to .joinpath()
|
|
|
|
|
|
|
|
The blog results should have a property of whether it is included in
the search results.
* Added is_searchable.
* Used Entry.get_absolute_url to encapsulate www host.
* Extracted get_search_config helper function.
Co-authored-by: Baptiste Mispelon <bmispelon@gmail.com>
|
|
than plural.
|
|
* Fix language switcher on search results pages
* Makefile delete revert
|
|
This was requested by the fundraising working group.
I abstracted the top `CorporateMember` display from the `releases` app
sidebar into a new inclusion tag called `top_corporate_members` and
included it in its original place as well as in the `docs` sidebar as
requested.
Uploaded images for `CorporateMember`s may not display in local
development environments do to the way media files paths work with
subdomains.
|
|
|
|
|
|
|
|
|
|
|
|
* Speed up initial docs cloning
---------
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
|
|
|
|
Thank you to Paulo Melchiorre, Tom Carrick, Marijke Luttekes, and
Baptiste Mispelon for the reviews.
|
|
|
|
Thank you Marijke Luttekes for the review.
|
|
The FK relationship between the models lends itself well to
a select_related() instead of a prefetch_related().
Additionally, this gets around a bug in 5.2 (initial release).
|
|
|
|
This is a partial revert of efc51e848d870d4c7675f6636b9893324ba3bc3f.
Due to an unfortunate conflict in the nginx configuration of
the server after the deploying of the commit mentioned above,
the _images directory ended up still being served by Django
which added a / to the end of the image path, using a permanent
HTTP redirection (because of settings.APPEND_SLASH).
The solution (hopefully temporary) is to restore the serving
of images by Django while we figure out how to configure
nginx to keep serving the _images and handled the old cached
redirections with a trainling slash.
|
|
This was missed in efc51e848d870d4c7675f6636b9893324ba3bc3f
|
|
|
|
|
|
This reverts commit f1fca5e8a412da1bb8b5ffd11a59eac8579738bb.
|
|
|
|
|
|
Three new file fields (tarball, wheel, checksum) were added, making
the link generation to these files more robust to changes like the
one mandated by PEP625 (changing of file case).
A new is_active boolean field was also added, making it easier
to start work on a release without it being public.
|
|
This reverts commit f87e1dbd3c06fe9b1100ddcd06394de5ae338577.
|
|
|
|
|
|
This reverts commit af929f0734c319447a061e82b0353fc48b792ec4.
|
|
|
|
This reverts commit fa56d9b841e0bd23c5c8871826ba6abe2205fdb4.
|
