-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC #106: Wagtail 6.5* and 6.6* roadmap updates #106
Open
thibaudcolas
wants to merge
8
commits into
wagtail:main
Choose a base branch
from
thibaudcolas:106-roadmap-updates
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+140
−0
Open
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
23af75c
Add first draft of RFC 106
thibaudcolas b4834ec
Fix order of items
thibaudcolas 7d92a94
Fix outdated content
thibaudcolas 843a2e8
Add RFC 105
thibaudcolas b974bfe
Update content with less TBC
thibaudcolas 6b7446d
Updates based on feedback
thibaudcolas 86a776a
Update based on comments
thibaudcolas 1e00905
Update 106-roadmap-updates.md
thibaudcolas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,93 @@ | ||
| # RFC 106: Public roadmap updates | ||
|
|
||
| - RFC: 106 | ||
| - Author: Thibaud Colas | ||
| - Created: 2025-01-29 | ||
| - Last Modified: 2025-02-05 | ||
|
|
||
| ## Abstract | ||
|
|
||
| This RFC provides a high-level overview of proposed [public roadmap](https://github.com/wagtail/roadmap) updates for future releases. This follows process changes introduced in [RFC 84](https://github.com/wagtail/rfcs/pull/84). See also RFCs [#86](086-roadmap-updates.md), [#88](088-roadmap-updates.md), [#91](091-roadmap-updates.md), [#98](098-roadmap-updates.md), [#101](101-roadmap-updates.md), [#103](103-roadmap-updates.md). | ||
|
|
||
| ## Version number for the May 2025 release | ||
|
|
||
| With no specific discussion to date, we currently expect the February 2025 release will be version 6.5\*. | ||
|
|
||
| \* Provisional version number. | ||
|
|
||
| ## Review of roadmap items for Wagtail 6.4 (February 2025) | ||
|
|
||
| 4 of 5 roadmap items will be marked as Done. | ||
|
|
||
| The following Wagtail 6.4 roadmap items will be marked as Done, with possible follow-up work outside of the formal roadmap: | ||
|
|
||
| - [Admin UI performance improvements](https://github.com/wagtail/roadmap/issues/80) | ||
| - Follow-up outside the roadmap: further performance improvements | ||
| - [StreamField blocks drag'n'drop](https://github.com/wagtail/roadmap/issues/85) | ||
| - Follow-up outside the roadmap: likely UI tweaks | ||
| - [StreamField blocks preview](https://github.com/wagtail/roadmap/issues/84) | ||
| - Follow-up outside the roadmap: likely UI tweaks | ||
| - [Headless improvements roadmap](https://github.com/wagtail/roadmap/issues/91) | ||
| - Follow-up on the roadmap: Headless userbar, headless API improvements | ||
|
|
||
| The following Wagtail 6.4 roadmap items will be moved to v6.6\*: | ||
|
|
||
| - None | ||
|
|
||
| The following Wagtail 6.4 roadmap items will be moved to Future: | ||
|
|
||
| - [Autosave support refactorings with Telepath](https://github.com/wagtail/roadmap/issues/47) | ||
|
|
||
| ## Proposed roadmap items for Wagtail 6.5\* (May 2025) | ||
|
|
||
| ### Validation on publish | ||
|
|
||
| Implementation of a frequently-requested feature: save draft versions of pages in an incomplete state, while still enforcing validation when publishing. This is a pre-requisite to implementing auto-save as proposed in [RFC 99: Preliminary work to support auto-save functionality](https://github.com/wagtail/rfcs/pull/99). | ||
|
|
||
| For more information, see [RFC 104: Validation on publish](https://github.com/wagtail/rfcs/pull/104). | ||
|
|
||
| ### Headless userbar | ||
thibaudcolas marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| Adding built-in support for the Wagtail userbar in headless mode, including accessibility checks, and built-in headless preview support. | ||
|
|
||
| For more information, see [RFC 100: Enhancing headless support](https://github.com/wagtail/rfcs/pull/100). | ||
|
|
||
| ### Headless API improvements | ||
|
|
||
| Implementation of top 3-5 headless improvements as identified in the [2024 headless survey](https://wagtail.org/blog/2024-headless-survey/), with a particular focus on the built-in REST API and documentation. | ||
thibaudcolas marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| For more information, see [RFC 100: Enhancing headless support](https://github.com/wagtail/rfcs/pull/100). | ||
|
|
||
| ### Site settings permissions | ||
|
|
||
| A new permission model for sites, where groups can be assigned permissions at the level of individual sites. This better maps organisational structures, compared to the current model of permissions being assigned at the level of the settings model rather than instances. | ||
|
|
||
| For more information, see [RFC 105: Site settings permissions](https://github.com/wagtail/rfcs/pull/105). | ||
thibaudcolas marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| ### CSP compatibility audit | ||
|
|
||
| An up-to-date review of [CSP compatibility issues](https://github.com/wagtail/wagtail/issues/1288) in Wagtail, with the view to help resolve them all in future releases. | ||
thibaudcolas marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| ## Proposed roadmap items for Wagtail 6.6\* (August 2025) | ||
|
|
||
| ### Google Summer of Code 2025 | ||
|
|
||
| Exact items TBC. Showcasing our participation to [Google Summer of Code](https://summerofcode.withgoogle.com/) on the project roadmap. | ||
|
|
||
| ### Headless demo site | ||
|
|
||
| An official headless demo site – primarily so our contributors and maintainers can more easily work on headless improvements. | ||
|
|
||
| For more information, see [RFC 100: Enhancing headless support](https://github.com/wagtail/rfcs/pull/100). | ||
thibaudcolas marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| ## Proposed roadmap items for "Future" releases | ||
|
|
||
| ### [Sustainability improvements #72](https://github.com/wagtail/roadmap/issues/72) | ||
|
|
||
| Existing item – moving to "Future" to earmark more specific improvements / find a feature sponsor. | ||
|
|
||
| ## Proposed roadmap items to close | ||
|
|
||
| ### [Admin interface accessibility improvements #71](https://github.com/wagtail/roadmap/issues/71) | ||
|
|
||
| This seems too fuzzy at this stage to be meaningfully considered "done" in any specific release. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: perhaps make explicit that
Validation on publishwas identified during the 6.4 release cycle as something that takes precedence, which is why this was de-prioritized.Question: out of curiosity, does this feature have sponsors? Do any roadmap items have sponsors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we have a sponsor for validation-on-publish, and in fact it's constraints on the funding (and when budgets can be spent) that have led to this being prioritised above the Telepath work, rather than any technical need for it to come first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, thanks for that context Matt 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the last release, drag'n'drop support was sponsored. In this upcoming release, in addition to validation on publish, we also have site settings permissions and some of the headless work (which bits exactly TBC)