- Aligns with the naming convention set from Wagtail 4.2
- Add deprecation warnings if classnames is accessed & unit tests for this
- Update other unit tests to use the naming
- Built on original PR #7372 and feedback on that solution
- Add unit tests and documentation
- Fix typo in API documentation for `CustomPagesAPIViewSet`
- Ensure that pk is used (not id) while filtering to prevent assumption that id is pk
This can be used in other places, but ensures caches are invalidated
whenever something about a page changes.
- Add a util to get wagtail-specific fragment cache keys
- Don't pollute context when injecting site variable
- Add documentation on wagtail fragment caching
- Define an intelligent cache key for pages
- Allow the components of the cache key to be easily modified
- Note that some manual changes may not create a new cache key
Co-authored-by: Andy Babic <andyjbabic@gmail.com>
Closes#5074
- Prep for #10197
- Fix a few cases where Draftail was spelt incorrectly
- Align with `client-side` not `clientside` as this is used most commonly
- fix javascript code snippet
- Link getting started section to elasticsearch backend, not performance page as this is more relevant.
- Mention frontend caching on performance page
- Mention prefetching image renditions on performance page
This cleans out some very old, potentially out of scope content, and makes way for the page being much easier to contribute to and extend in future.
Move deploy tutorials to 3rd-party tutorials page
- Optimized/Customized/Catregorize -> Optimised/Customised/Categorise
- Github -> GitHub (80% were spelt with capital H, this is the way GitHub spells itself)
- GitPod -> Gitpod (most were without the capital P, Gitpod's site does not use capital P)
- Remove duplicate words (to to, the the)
- De-coupled -> decoupled
- implementors -> implementers (all other references used 'site implementers' so just aligning with the common case)
- Fix a/an usage in one case
- Fix one comment usage of ok, replace with OK
* Extract userbar BaseItem.get_context_data()
* Extract Axe config into smaller attributes and methods for easier overrides
* Add TypeScript interface for WagtailAxeConfiguration
* Improve typings for userbar.ts
* Separate Axe `runOnly` and `rules` options
* Pass request object to all axe configuration methods
* Remove Axe runOnly option if it's falsy
* Add docs for customising the accessibility checker
* Use lists for Axe include and exclude selectors
* Parse JSON script when testing accessibility checker config
* Add tests for customising accessibility checker configuration
Co-authored-by: Thibaud Colas <thibaudcolas@gmail.com>
Since Wagtail 4.1 the Settings Tab and the corresponding scheduling of pages has been moved to the Status side panels. As mentioned in the release notes of Wagtail 4.1: [See here](https://docs.wagtail.org/en/stable/releases/4.1.html#new-ui-for-scheduled-publishing).
In the documentation section for customising the edit interface, this snippet is still available. When implemented, there is no effect and no error is shown.
Therefore this line is obsolete and only the two tabs 'Content' and 'Promote' should be available.
Co-authored-by: Julian Bigler <disperate@users.noreply.github.com>
Perform the data migration while it's still a rich text field, to avoid the need for `use_json_field=False`. Also work around the unavailability of `page.revisions` on frozen ORM models (which has been absent since 4.0, since it's now a property on RevisionMixin rather than a true relation).
Fixes#9939
Also remove the mentions of redirects from the documentation - the fact that the method has to check for a different redirect URL is an internal implementation detail, and not relevant to what the assertion is intending to test (namely that a page is successfully created).
Most of these are no longer applicable due to the introduction of Wagtail guide, where possible the new guide links are used now
- Re-add missing docs image for extending Draftail
- There is no Guide page (yet) for Inserting videos or images so those links have been removed
- Fix some additional reference issues where the page name and reference were causing issues
* Clean up the performance page structure
Many of the sections mentioned here will improve performance for much more than just the editor experience.
* Link to Django's performance page
- Allow users to override the default attributes given to an image
- Update tests to account for new tags
- Add documentation for custom image attributes
- Recommend that loading=lazy & decoding=async be considered for performance in front-end sites
- fix some broken refs that were lost in the migration to markdown files
- use lower_snake_case for all internal refs (most follow this convention)
- release process sub-section in docs should be named release schedule instead
LB Johnston