RFC 113: Wagtail 7.4 roadmap updates#113
Conversation
thibaudcolas
force-pushed
the
113-roadmap
branch
from
408de2c to
d7deb73
Compare
thibaudcolas
force-pushed
the
113-roadmap
branch
from
d7deb73 to
40c05de
Compare
thibaudcolas
changed the title
abigail-hampson
moved this from ❌ Blocked
to 👀 In review
in Wagtail 7.4 LTS release planning
| A range of UX improvements to the editing experience, with a focus on addressing known pain points / clearing our backlog of UX issues. To be refined, based on: | ||
|
|
||
| - [Issues labelled 'UX'](https://github.com/wagtail/wagtail/issues?q=sort%3Aupdated-desc%20state%3Aopen%20label%3AUX) | ||
| - [Issues labelled 'Design system'](https://github.com/wagtail/wagtail/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22component%3ADesign+system%22) |
There was a problem hiding this comment.
This is very open-ended, suggestions very welcome on specific pain points to include here. @laymonage and I were considering choosers but that is a massive effort 🙈.
|
|
||
| Move existing item to “Future”. Dependent on completion of [Model search improvements](https://github.com/wagtail/roadmap/issues/116). | ||
|
|
||
| ### Multilingual content lifecycle |
There was a problem hiding this comment.
This is a bit of a grab bag, I wish we had more focused improvements in mind but haven’t had the time to decide what exactly to do "first" based on the discussion in Improving support for multilingual websites #13693.
| Size: XL | ||
|
|
||
| Iterative improvements towards a new design for choosers, which brings them closer to the "Universal listings" UX rolled out across listing views. |
There was a problem hiding this comment.
🙈 tentative, that’s a challenging one
|
|
||
| Follow-up improvements to the [Autosave MVP](https://github.com/wagtail/roadmap/issues/47) based on user feedback and real-world usage. Tentatively including: | ||
|
|
||
| - [Deferred validation for required fields in StreamField](https://github.com/wagtail/wagtail/issues/13699) |
There was a problem hiding this comment.
Deferred validation in StreamFields will be great. Are you sure it's "small"? In any case, looking forward to being able to use it soon.
|
|
||
| Here are possible roadmap items that were discussed but not included in the roadmap this time, provided for feedback and for future reference. If one of those items is important to you, please comment! They may be available for external contributions or for a [feature sponsorship](https://wagtail.org/sponsor/). | ||
|
|
||
| - Documentation improvements incl. restructure |
There was a problem hiding this comment.
@thibaudcolas can you share some details what considerations were involved when deciding not to pursue documentation improvements?
The 'documentation' topic keeps coming up as an area Wagtail can improve on over the past couple of years, so it is interesting to me this was considered but hasn't made the cut.
There was a problem hiding this comment.
We’ve decided to work on this without it being on the roadmap for the time being, specifically this issue: More documentation guidelines for contributors #13801
I think it has potential as a roadmap item, just a bit fuzzy on the details of what we would for it to be at that kind of "scale"?
There was a problem hiding this comment.
Yeah, the exact deliverables for 'better developer docs' are fuzzy to me too. I'd count any effort towards clearing that up as a roadmap item too since it would constitute a considerable effort. Maintainer week and GSoC often make it as an item on the roadmap too for that reason I believe.
Here are some of my thoughts for what 'documentation improvement efforts' could be:
- content inventory, anything we want to change about the structure? Split up very long pages perhaps? Or maybe consolidate information that is spread out?
- interviews: ask people with not much Wagtail experience to find something specific in the docs. Maybe this yields new insights into friction encountered.
- For example: how do I create a site setting? How can I customize a snippet's index view columns? How can I make a many-to-many relation editable through Wagtail (can they find and figure out how to use InlinePanel, ClusterableModel, and friends)
- what technical improvements to make to the search to make it actually find things??
I'm interested in this topic, so if we're ever going to end up planning improvements to the docs, I would like to be involved 👍
There was a problem hiding this comment.
yep, that makes sense to me. I’ve started a separate discussion so we can make concrete short-term and long-term plans: Documentation improvement opportunities #13951
lb-
left a comment
lb-
left a comment
There was a problem hiding this comment.
Thanks @thibaudcolas - looks like there's a few small comments from others to resolve but I'm happy to approve. Thanks for putting these roadmap RFCs together.
github-project-automation
bot
moved this from 👀 In review
to ✅ Done
in Wagtail 7.4 LTS release planning
5 participants
Wagtail 7.3 is out, as usual we’re now looking at the next release 🚢. Noting v7.4 is set to be a Long Term Support (LTS) release.
View the RFC in HTML. Once reviewed with enough feedback and approved by the core team, those changes will go live on the Wagtail Roadmap.
7.4*: Provisional version numbers. See our Release schedule for more info.