Wagtail UI team: meeting updates #8265

thibaudcolas · 2022-03-31T21:10:10Z

thibaudcolas
Mar 31, 2022
Maintainer

👋 to make it easier for people to stay up to date with what the UI team is doing, we’re trialing sharing our meeting notes here!
Subscribe to this thread if you’d like weekly updates, unsubscribe if this isn’t for you (in "Notifications" to the side 👉).

Past meetings (latest first):

thibaudcolas · 2022-03-31T21:33:45Z

thibaudcolas
Mar 31, 2022
Maintainer Author

2022-03-31 UTC evening

Attendees: Kalob, LB, Thibaud, Naomi, Scott

Highlights

Now sharing weekly meeting notes on GitHub Discussions for better visibility, with 5-line highlights.
Experimenting with the page editor’s form markup. PR, live demo. Still a few UX & accessibility points to resolve.
The GSoC: High contrast mode project is a chance to generally improve theming. We’re researching how others do this.
Experiments on component documentation in Markdown are promising and we’ll go ahead with a PR to Wagtail.
Prototype setup of visual regression testing with Percy coming up soon.

Actions

LB Feedback on forms markup (PR) / live demo
✅ Thibaud Push PR with forms markup for code review + post link to UI channel
Thibaud PR with storybook-django docs extraction
Scott review PR with storybook-django docs extraction

Actions review

✅ Thibaud Ask Dawn to complete poll on meeting times
Steve :) Dark mode research
✅ Thibaud Prototype forms structure with Steve to review
✅ Thibaud - Prototype comment extraction with Markdown syntax -- simplest option (w/ Markdown MIME type), and Google Style. prepare a PR for the first version of dosctrings within a Django template to be used by Storybook. (Scott can review)
Thibaud - Prepare a PR on wagtail-fork for the proposed Percy checks (Scott can review, Naomi happy to try putting in a Pull Request to see how that can work for others).
Thibaud - Compare different approaches to UI component declarations (incl. Wagtail Template components)

Discussions

Welcome Kalob :)
- The tutorial guy
- Kalob Learn Wagtail Dot Org
- Here to see what's going on
Meeting times
- Thank you LB for being flexible 🙏
- This will be useful for core team hopefully
GitHub Discussions for meeting notes
- More exposure (people watching repository)
- Feedback is fine
Prototype forms structure
- Conundrum about clickability of heading / label for single-field panels
- Thibaud more effort to make char count look like a char count
GSoC: UX improvements throughout Wagtail
- LB lead mentor
GSoC: High contrast mode
- Jane lead mentor
- Asking for theming feedback web-a11y slack, no luck
- Suggestion: ask on https://design.systems/slack/
Wagtail 3.0
- RC likely some time between 11/04 and 19/04
- Lots of PRs to get to :)
- LB away next meet away / offline before RC

Here are meeting notes from previous meetings of the UI team:

2022-03-24 UTC morning

Attendees: LB, Thibaud

Actions

✅ Thibaud Ask Dawn to complete poll on meeting times

Actions review

Steve :) Dark mode research
Thibaud Prototype forms structure with Steve to review
Thibaud - Prototype comment extraction with Markdown syntax -- simplest option (w/ Markdown MIME type), and Google Style. prepare a PR for the first version of dosctrings within a Django template to be used by Storybook. (Scott can review)
Thibaud - Prepare a PR on wagtail-fork for the proposed percy checks (Scott can review, Naomi happy to try putting in a Pull Request to see how that can work for others).
Thibaud - Compare different approaches to UI component declarations

Discussions

Sidebar UI funkiness
Prototype comment extraction with Markdown syntax
Google Summer of Code -- UI team involvement with projects

2022-03-17 UTC afternoon

Attendees: Dawn, Naomi, Thibaud, Harris, Steve, Scott

Actions

Steve :) Dark mode research
Thibaud Prototype forms structure with Steve to review
Thibaud - Prototype comment extraction with Markdown syntax -- simplest option (w/ Markdown MIME type), and Google Style. prepare a PR for the first version of dosctrings within a Django template to be used by Storybook. (Scott can review)
Thibaud - Prepare a PR on wagtail-fork for the proposed percy checks (Scott can review, Naomi happy to try putting in a Pull Request to see how that can work for others).
Thibaud - Compare different approaches to UI component declarations

Actions review

Thibaud - Prototype comment extraction with Markdown syntax -- simplest option (w/ Markdown MIME type), and Google Style. prepare a PR for the first version of dosctrings within a Django template to be used by Storybook. (Scott can review)
Thibaud - Prepare a PR on wagtail-fork for the proposed percy checks (Scott can review, Naomi happy to try putting in a Pull Request to see how that can work for others).
✅ Thibaud - Short summary update in the core team chat after this meeting with links to minutes.
✅ All - review third party libraries and provide suggestions Third-party libraries selection for major UI components #7980
Thibaud - Compare different approaches to UI component declarations

Discussions

What's up?
Google Summer of Code -- UI team involvement with projects
- Create and select related content
  - https://github.com/wagtail/wagtail-autocomplete
  - Model autocomplete widget #6213
  - Harris looking after this on behalf of UI team
- Make Wagtail editor guide a stand-alone project
  - Unclear whether this is within our remit or not?
  - Check whether this involves design changes
  - Be involved with documentation changes concerning the Wagtail UI
  - Ben Enright
  - Make sure Phil Dexter keeps in touch with us
  - Stretch goal very relevant to us: integration within Wagtail admin
- Apply new page editor style to all views - To be refined, lead
- Windows High contrast mode (plus dark theme?) support for whole Wagtail admin
  - Steve pro dark themes
  - First goal: consider theme-ability options as part of front-end changes
  - Switch or OS-level? Both :)
  - See GitHub example
  - Stretch goal: Slack-style "paste your stylesheet" / colors
  - Adds burden to third-party widget developers?
  - Front-end for CSS variables
  - We'll see whether this comes through :)
Built-in accessibility tests for Wagtail pages on publish / editing
- A lot of accessibility considerations
HTML structure for page editor's form
- Toolkit
- Pair programming / code review
- Mocking the grouping
- Steve reviewing. Steve pair programming too :)

2022-03-10 UTC evening

Attendees: Thibaud, Naomi, Scott, LB, Harris

Actions

Thibaud - Prototype comment extraction with Markdown syntax -- simplest option (w/ Markdown MIME type), and Google Style. prepare a PR for the first version of dosctrings within a Django template to be used by Storybook. (Scott can review)
Thibaud - Prepare a PR on wagtail-fork for the proposed percy checks (Scott can review, Naomi happy to review the Pull Request side of things to see how that can work for others).
✅ Thibaud - Short summary update in the core team chat after this meeting with links to minutes.
✅ All - review third party libraries and provide suggestions Third-party libraries selection for major UI components #7980
Thibaud - Compare different approaches to UI component declarations

Actions review

✅ Thibaud Do another search on GitHub for Hallo packages
✅ Thibaud Review structured docstrings research
✅Steve, Thibaud - To propose visual regression testing soon
- Percy from Browserstack, Storybook test suite, E2E test suite

Discussions

Hallo packages
- Should not be a huge issue, not too many packages out there.
Structured docstrings research
- The most simple is probably the best way to go, the plan is to take a look in the next day or so.
- Need a volunteer to review a PR when ready (Scott will do)
Slack channel: #ui vs. #ui-team, or both
- Naomi - Would be good to split the channel out, but splitting out makes it harder for the wider community to feel that they can input.
- Sometimes the channel can be filled up with a bit of logistics but this is probably not a big deal and can be managed with a thread.
- Agreed - no change for now but just a reminder for everyone that we do want to be transparent with the community but also try to keep noise to a minimum (use threads).
Third-party libraries selection for major UI components #7980
- Looking for feedback / more suggestions before we proceed.
- Thibaud - the only one we need really soon is the tooltip, the others are futher down the line.
  - The datepicker choice is actually really hard, there is not an option we could find that was actually accessible and supports our requirements for assistive text.
- Naomi - best to go with what is the most 'default' as possible (Pythonic way), especially when all the other options are not great, we can go with the default and then can always adopt something more in the future.
- Tippy.js - seems good for accessibility and is actually a layer on top of floating-ui (aka popper.js).
- Looking for suggestions for any others, including tabs.
- Would be good to see what other large organisations (governments) are using for these kinds of things.
- Possibly useful tab guidance: https://inclusive-components.design/tabbed-interfaces/
Documentation for components -- will do a trial next
- Looking for volunteers
- See actions, looking at the simplest approach to get started.
Visual regression testing setup: with Percy from Browserstack
- For every PR, via existing CircleCI builds
- Running both on Storybook stories, and integration tests with Puppeteer
  - Running multiple "projects" is documented
- GitHub PR status
  - Do not require Percy approvals
- Set to auto-approve where relevant
- Next steps: trial all of the above on wagtail-fork project, incl. PR workflow
- Looking for volunteers to review
- Scott has a little bit of experience with Percy and is happy to take a look
- Naomi is happy to review the Pull Request side of things to see how that can work for others.
SVG icons
- Rollout is nearly there: Phase out icon font and use SVG everywhere #6107, Modify SVG icon handling so that they can be used in CSS #7511
- There is a list on github (about 40 or so) of existing icons that still need to be addressed.
- Would be a great time to finish this off before the next release if possible.
- Table headers (sort by), these have been a bit tricky, most others should be reasonably straightforward.
- Scott is happy to take another look at these.
Core team updates
- Naomi raised (in core team) that it would be good for sub-teams to have a standing update slot in core team meetings (or once a month).
- Maybe the highlights (decisions, main items) as a short summary.
- Short updates in the core team chat are also useful.

2022-03-03 UTC morning

Attendees: LB, Thibaud

Actions

✅ Thibaud Do another search on GitHub for Hallo packages
Thibaud Review structured docstrings research
Thibaud Prototype comment extraction with Markdown syntax -- simplest option (w/ Markdown MIME type)
Steve, Thibaud - To propose visual regression testing soon
- Percy from Browserstack, Storybook test suite, E2E test suite
Thibaud Compare different approaches to UI component declarations

Actions review

✅ Thibaud Review Internationalisation / i18n - testing and guidelines 🌐 #8017
✅ Thibaud - Invite Ben Enright to our future meetings.
✅ Coen Raise PO files methodology & blocktrans trimmed issue
Steve, Thibaud - To propose visual regression testing soon
- Percy from Browserstack, Storybook test suite, E2E test suite
✅ Naomi Research structured docstrings
- From the sphinx.ext.autodoc documentation, there are two other styles for docstrings, which are described well in the sphinx.ext.napoleon documentation (which converts them to RST for autodoc. Of those three options (autodoc, NumPy, Google) I like the Google style, which is more similar to the Markdown style that Thibaud showed. I wonder if it would be possible to use napoleon's docstring parsing both for linting and to output something other than RST, but my guess would be that it's more trouble than it's worth? It also does not include a way to give default values for arguments.
- YAML seems like it could be a good option since it's JSON based, so it would convert easily to what Storybook wants. Though at some point it feels like what's the difference between doing this and just shoving the whole story config into the template file.
Thibaud Compare different approaches to UI component declarations

Discussions

Should we find all Hallo packages - add an issue flagging that next release Hallo will be an external package?
- Only one found so far with dual editor support
- Will check again
When will we formalise that the next release will be 3.0? (release notes file, communication, references in external packages)
- Soon™ (discussed in this week's team meeting)
- wagtail-hallo: will have to fix the core packages reorganisation, hopefully will be picked up by nightly CI
- v0.1.0 for 2.16, v0.2.0 for 3.0
Structured docstrings
- Keep it simple?
- Comments syntax lighting
- {% comment "Optional note" %} https://docs.djangoproject.com/en/4.0/ref/templates/builtins/#comment

2022-02-24 UTC afternoon

Attendees: Naomi, Harris, Scott, Thibaud, Steve, Dawn

Actions

Thibaud Review Internationalisation / i18n - testing and guidelines 🌐 #8017
✅ Thibaud - Invite Ben to our future meetings.
Coen Raise PO files methodology & blocktrans trimmed issue
Thibaud Implement auto-fixable ordering of declaration blocks in CSS
Steve, Thibaud - To propose visual regression testing soon
✅ Naomi Research structured docstrings
- From the sphinx.ext.autodoc documentation, there are two other styles for docstrings, which are described well in the sphinx.ext.napoleon documentation (which converts them to RST for autodoc. Of those three options (autodoc, NumPy, Google) I like the Google style, which is more similar to the Markdown style that Thibaud showed. I wonder if it would be possible to use napoleon's docstring parsing both for linting and to output something other than RST, but my guess would be that it's more trouble than it's worth? It also does not include a way to give default values for arguments.
- YAML seems like it could be a good option since it's JSON based, so it would convert easily to what Storybook wants. Though at some point it feels like what's the difference between doing this and just shoving the whole story config into the template file.
Thibaud Compare different approaches to UI component declarations

Discussions

Actions review
- ✅ Steve - Follow up with ben about multilingual (test and see if the browser can translate too).
- Doesn't work so well in Figma
- ✅ LB, Steve - Research how to test multilingual issues in the wild and follow up with the slack channel. Done Internationalisation / i18n - testing and guidelines 🌐 #8017 - lots of research results there, nothing that stands out as a solution but rather lots of smaller things we can adopt.
- Thibaud - Invite Ben to our future meetings.
- Coen Raise PO files methodology & blocktrans trimmed issue
- Thibaud Implement auto-fixable ordering of declaration blocks in CSS
- Steve, Thibaud - To propose visual regression testing soon
- ✅ Thibaud - Create a poll about Node build tools to customise wagtail
- Aiming to make a tentative decision within the next month for a UI framework decision and component level (Dropdown, Tabs, Modal, Tooltips, Datepicker)
Internationalisation testing / guidelines
- Internationalisation / i18n - testing and guidelines 🌐 #8017
- https://rtlstyling.com/posts/rtl-styling
Pattern library setup demo (#8025)
UI components file structure
UI components documentation
Storybook it? Documentation table is one of the main benefits
Example: changing what buttons look like vs. reusing a template -- do we expect people to be able / willing to Storybook this?
Brand new views with existing components vs. brand new components
Structured comment format -- YAML
Amazing bonus points:
- Check file for variables that are used, check comments, throw errors
- Custom comment tag with syntax highlighting & formatting
- Python documentation for functions
Standardised format for docstring / triple-quote comments
- Yeah docstring not inherently very structured https://www.python.org/dev/peps/pep-0257/
- Sphinx is a system that auto documents python functions and is fairly standard, so this is a place I would start looking https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html
UI components API
- {% icon name="potato" %}
- django-components -- Reusable UI components for Django, going further than template partials.
- django-component -- Modern components for django templates Declarative and composable components inspired by javascript frameworks.
- slippers -- Reusable components for Django, without writing a single line of Python.
- Custom implementation
- Depends on contributors' backgrounds? One more thing to learn?
- How much do those libraries bring?
- Custom template tags generally -- can be annoying to have to figure out how the template tags work
Wagtail Space US
- Harris join organizers? ;)
- Dawn interested to help new contributors -- particularly around UI work
  - Suggestions welcome!

2022-02-17 UTC evening

Attendees: Steve, Thibaud, LB, Naomi, Coen, Harris

Actions

Steve - Follow up with ben about multilingual (test and see if the browser can translate too).
✅ LB, Steve - Research how to test multilingual issues in the wild and follow up with the slack channel. Done Internationalisation / i18n - testing and guidelines 🌐 #8017 - lots of research results there, nothing that stands out as a solution but rather lots of smaller things we can adopt.
Thibaud - Invite Ben to our future meetings.
Coen Raise PO files methodology & blocktrans trimmed issue
Thibaud Implement auto-fixable ordering of declaration blocks in CSS
Steve, Thibaud - To propose visual regression testing soon
✅ Thibaud - Create a poll about Node build tools to customise wagtail
Aiming to make a tentative decision within the next month for a UI framework decision and component level (Dropdown, Tabs, Modal, Tooltips, Datepicker) Third-party libraries selection for major UI components #7980

Discussions

Actions review
- Scott & Thibaud Finish Only run Circle CI jobs if appropriate files have been changed #6790
  - Still in progress (with Thibaud :[ )
- Thibaud Set up Windows-only build of front-end tooling once Only run Circle CI jobs if appropriate files have been changed #6790 is merged
  - Blocked by the above
- ✅ Thibaud Try out Storybook composition
  - Done, it works really well, was very simple. 10/10
- ✅ Coen Review list of components from Django perspective Wagtail | Page editor 2022 UI overview
  - Shared on Slack
- ✅ Steve Review designs for multilingual issues / talk to Ben
- Coen Raise PO files methodology & blocktrans trimmed issue
- Thibaud Implement auto-fixable ordering of declaration blocks in CSS
  - Still TODO
- Thibaud Try out Normalize.css upgrade with visual regressions
  - Please also review this PR as it explains the issue encountered when upgrading previously Revert "Upgrade modernizr" back to v2.6.2 #7626
  - Still TODO (blocked by visual regression R&D)
- ✅ Thibaud Read LB's investigation & provide feedback
  - Done, need to do another round.
- ✅ Thibaud Ask Karl, Jacob, (?) for input on UI frameworks
  - I've spammed everyone I know and more. Will have a dedicated chat with specific people next
  - One point of feedback: we're assuming Wagtail implementers don't want to use Node build tools to customise Wagtail. Would be nice to have a quick poll to confirm.
- ✅ Steve Follow up on design tokens definition
- ✅ Thibaud Pass on feedback re opening contributions outside of current team
  - Done, we're keen
Multilingual Wagtail
- Multilingual support - chat with Ben -- which language(s) should we test the designs with?
- Brand font feedback from Vince: would be nice to try it out with more scripts / languages? (Arabic)
  - Use Steve's wagtail-ui-testing site for this?
- https://www.mediawiki.org/wiki/Internationalization/Styling_and_typography
UI framework decision
- Thibaud asked around for people's top picks
- Good discussions on Slack. Lots of propositions to go with "vanilla JS" compared to other frameworks
- To review: https://2021.stateofjs.com/
- Aiming to make a tentative decision within the next month
- Two things
  - 1. Lightweight base framework
  - 2. Component (ish) tools -Third-party libraries selection for major UI components #7980
[Third-party libraries selection for major UI components Third-party libraries selection for major UI components #7980](Third-party libraries selection for major UI components #7980

2022-02-10 UTC morning

Attendees: Coen, LB, Fabien, Thibaud

Actions

Scott & Thibaud Finish Only run Circle CI jobs if appropriate files have been changed #6790
Thibaud Set up Windows-only build of front-end tooling once Only run Circle CI jobs if appropriate files have been changed #6790 is merged
Thibaud Try out Storybook composition
Coen Review list of components from Django perspective Wagtail | Page editor 2022 UI overview
Steve Review designs for multilingual issues / talk to Ben
Coen Raise PO files methodology & blocktrans trimmed issue
Thibaud Implement auto-fixable ordering of declaration blocks in CSS
Thibaud Try out Normalize.css upgrade with visual regressions
- Please also review this PR as it explains the issue encountered when upgrading previously Revert "Upgrade modernizr" back to v2.6.2 #7626
Thibaud Read LB's investigation & provide feedback
Thibaud Ask Karl, Jacob, (?) for input on UI frameworks
Steve Follow up on design tokens definition
Thibaud Pass on feedback re opening contributions outside of current team

Discussions

Actions review
Multilingual issues
- PO files should be done earlier? Should be part of PRs
- Sync script happening before releases
Lightweight UI framework
- Transition could be gradual
- Also considering Turbo? (Coen tried)
  - Works well in the Django paradigm
  - Stimulus Reflex = Stimulus + Turbolinks
  - Can be considered in the future -- nice to know there is a bigger ecosystem
Styleguide -- online or embedded in Wagtail?
- Online first
- Embedded in Wagtail -- what's the use case?
- Problem with current styleguide is it's out of date
- Where should it be hosted?
  - Would be nice if it was versioned?
  - Good questions
- Removing the current styleguide -- hopefully minimal
- Do we need versioning?
  - Can just check out a different branch if needed
  - Landing page with instructions on how to run it locally for a specific version
  - Publish latest by default
Page editor 2022 impact on existing backlog
- https://github.com/orgs/wagtail/projects/1/views/4
Scope for other parts of Wagtail?
- Gradual is the way to go
- Make sure other people can pick up the work elsewhere
- (non-Torchbox)
Review of jQueryUI usage
- Main one: Hallo
- File uploads (way beyond support)
- Tagit
- Code complexity is also because browser support from 10 years ago
https://github.com/wagtail/wagtail/projects/13#card-76521029
✅ Removal of Hallo
- Discussed in core team
- Next release (will be 3.0)
Deprecations / breaking changes
- Make the Stimulus decision as soon as possible
- Coen is keen based on concepts / working well for Wagtail in particular

2022-02-03 UTC afternoon

Attendees: Naomi, Scott, Thibaud, Steve, Harris

Actions

Scott & Thibaud Finish Only run Circle CI jobs if appropriate files have been changed #6790
Thibaud Set up Windows-only build of front-end tooling once Only run Circle CI jobs if appropriate files have been changed #6790 is merged
✅ Thibaud Merge Prettier PR in 24hours & share steps to fix conflicts on Slack
Thibaud Try out Storybook composition
Coen Review list of components from Django perspective Wagtail | Page editor 2022 UI overview
Steve Review designs for multilingual issues / talk to Ben
Thibaud Implement auto-fixable ordering of declaration blocks in CSS
Thibaud Try out Normalize.css upgrade with visual regressions
- Please also review this PR as it explains the issue encountered when upgrading previously Revert "Upgrade modernizr" back to v2.6.2 #7626
✅ Thibaud Ask for system font stack feedback in #ui as part of implementation
Naomi, Thibaud Read LB's investigation & provide feedback
✅ Thibaud Ask Karl, Jacob, (?) for input on UI frameworks
✅ Steve Make spreadsheet with design tokens
✅ Steve Schedule serious bikeshedding meeting
- With spreadsheet with design tokens
- Comments on spreadsheet

Discussions

Actions review
UI framework discussions
- HTMX & plain JS -- still on the table? (tweet)
- Pick one of the two options on the Web Components
- Further look into options set aside by LB
- Score against use cases LB drafted?
- Scott interested in seeing how HTMX works even outside of Wagtail admin
Prettier
- Worth the heads' up
- See actions
Design tokens naming
- Colors - numbers sound good
- Text
- Generic label1, label2, label3?
- Alias to what the style actually is used
- Document what they are for?
Page editor 2022 impact on existing backlog
- https://github.com/orgs/wagtail/projects/1/views/4

2022-01-27 UTC evening

Attendees: Naomi, Harris, LB, Scott, Steve, Thibaud, Dawn, Coen

Actions

Thibaud Review and merge Only run Circle CI jobs if appropriate files have been changed #6790
LB Review Prettier PR
Coen Review Prettier PR
Thibaud Try out Storybook composition
Coen Review list of components from Django perspective
Thibaud Next version of declaration-strict-value PR
LB Review afterwards
Thibaud Research ways to help enforce usage of flexible-width components
Thibaud Implement auto-fixable ordering of declaration blocks in CSS
Thibaud Try out Normalize.css upgrade with visual regressions
- Please also review this PR as it explains the issue encountered when upgrading previously Revert "Upgrade modernizr" back to v2.6.2 #7626
Thibaud Ask for system font stack feedback in #ui as part of implementation
Dawn, Naomi, Harris, Scott, Steve Read LB's investigation & provide feedback

Discussions

Internet submarine cables topology
New members! 🌈
- Welcome Harris!
  - Principal dev @ Freedom of the Press foundation
  - Want to help with this -- something that feels smaller than core team!
- Hey Dawn :)
  - SWE at Wharton, Philadelphia, core team
  - Keen to be involved with this. Maybe with two mentees too
- Rounds of intros! Thibaud, Steve, LB, Naomi, Scott
Actions review
CSS resets
- The version we're using is very old and rather different from the current one, but the current one looks reasonable. I (Naomi) think we should update to the current version, but either we'll have to test well since some things are affirmatively different (like going from b and strong having font-weight: bold to having font-weight: bolder). I agree with Normalize's approach of not being opinionated. I think that if we want something opinionated, we should go with using an entire accessibility-focused design system such as uswds, which I've never used before, but they're legally required to be serious about accessibility.
- Potential breakage? (this is good timing if there is any)
- Decision needed: introduce this side by side with supporting existing CSS / UI components? Or separate
- Thibaud to test how much is changing in practice
Building upon USWDS design system?
- More accessibility fundamentals to be built upon
- Need to be careful with our dependencies
- Need to achieve bespoke UIs, but also don't want to reinvent the wheel for utils
- Dropdown implementation
- Tabs implementation
- Modal
- Tooltips
- Date picker
System font stack
- Go for it
- Check which guidance is the most recent (follow that)
- Roboto
- Scott has all the devices :)
- Chinese or Japanese testing
- Ask in #watercooler
- Use Squash for this
- Ask in #translators channel / look at Transifex contributors
- https://infinnie.github.io/blog/2017/systemui.html
- Roboto issue
- system-ui
LB's lightweight frameworks review
- 💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯💯
- 🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈🌈
- Ask for others to review, particularly people involved with Telepath
- RFC?
- ES6 modules RFC overlap?
- Look at thread from people with production experience
45min meetings!
Recurring meetings for

2022-01-20 UTC morning

Attendees: Thibaud, LB

Actions

✅ Steve Share and demo Alpine implementation of dropdown
Thibaud Review and merge Only run Circle CI jobs if appropriate files have been changed #6790
LB Review Prettier PR
Coen Review Prettier PR
Thibaud Try out Storybook composition
Coen Review list of components from Django perspective
✅ Scott Stylelint declaration-strict-value PR review
Thibaud Research ways to help enforce usage of flexible-width components
Thibaud Implement auto-fixable ordering of declaration blocks in CSS
✅ Naomi Research normalize.css & other resets
✅ Scott Research system font stack for Wagtail (#7724)
Naomi looked into this a bit and commented. It looks like yes we should do this and we should be careful about testing font weights

Discussions

Actions review
jQuery deprecations
JS framework for Wagtail

2022-01-13 UTC afternoon

Attendees: Naomi, Scott, Fabien, Thibaud, Steve

Actions

Steve Share and demo Alpine implementation of dropdown
Thibaud Review and merge Only run Circle CI jobs if appropriate files have been changed #6790
LB Review Prettier PR
Coen Review Prettier PR
Thibaud Try out Storybook composition
Thibaud Review page editor related issues and PRs
Coen Review list of components from Django perspective
LB Stylelint declaration-strict-value PR review
⏳ Scott Stylelint declaration-strict-value PR review
Thibaud Research ways to help enforce usage of flexible-width components
Thibaud Implement auto-fixable ordering of declaration blocks in CSS
Naomi Research normalize.css & other resets
Scott Research system font stack for Wagtail (#7724)

Discussions

Actions review
- ✅ Thibaud Ask an Alpine.js / htmx expert to pitch us
  - https://codepen.io/thibaudcolas/pen/rNGrPjz
- Thibaud Review and merge Only run Circle CI jobs if appropriate files have been changed #6790
- LB Review Prettier PR
- Coen Review Prettier PR
- ✅ Thibaud Prettier semi-automated PR conflict fixes step-by-step
  - git rebase --strategy-option=theirs --exec '(djhtml -i git show --name-only --pretty="" HEAD "*.html" || true) && git add git show --name-only --pretty="" HEAD "*.html" && git commit --amend --no-edit --no-verify' origin/master
- Thibaud Try out Storybook composition
- ✅ Fabien Review RTL support plans
- ✅ Thibaud Review CSS refactoring list https://github.com/wagtail/wagtail/projects/4#card-17060767
- Coen Review list of components from Django perspective
- LB Stylelint declaration-strict-value PR review
- ⏳ Scott Stylelint declaration-strict-value PR review
- Thibaud Research ways to help enforce usage of flexible-width components
- Thibaud Implement auto-fixable ordering of declaration blocks in CSS
Wagtail 2.16
- Slim sidebar
- TypedTableBlock
- Modal choosers bug fix
- Breaking changes expected in Wagtail 2.17
  - SVG icons
  - Modernizr
  - jQuery Datetimepicker
  - Good idea
Wagtail design system components list
Modern CSS reset
- Example: https://www.joshwcomeau.com/css/custom-css-reset/
- Pick one and move on :)
- Or... careful because of the potential breakage
- Box-sizing
- https://necolas.github.io/normalize.css/ consider first
- UI regression test suite would be nice
- Percy + Browserstack sponsorship
- https://github.com/thibaudcolas/wagtail-tooling
System font stack (Wagtail brand font #7724)
- Who has done research? / wants to
- Customisable system font
- Dyslexia font support / browser extensions or browser-level font customization
- Good resources on this?
- web-a11y
Browser support & testing goals
- iOS Safari 12?
- Windows testing
- Windows: yes, Edge (scrollbar)
- Safari last 3 major versions
- Device management issues & Safari version tied to OS

2022-01-06 UTC evening

Attendees: Steve, Scott, Naomi, Thibaud

Actions

Thibaud Ask an Alpine.js / htmx expert to pitch us
Thibaud Review and merge Only run Circle CI jobs if appropriate files have been changed #6790
LB Review Prettier PR
Coen Review Prettier PR
Thibaud Prettier semi-automated PR conflict fixes step-by-step
Thibaud Try out Storybook composition
✅ Fabien Review RTL support plans
Thibaud Review CSS refactoring list https://github.com/wagtail/wagtail/projects/4#card-17060767
Coen Review list of components from Django perspective
LB Stylelint declaration-strict-value PR review
Scott Stylelint declaration-strict-value PR review
Thibaud Research ways to help enforce usage of flexible-width components
Thibaud Implement auto-fixable ordering of declaration blocks in CSS

Discussions

Quick recap of last meeting
- Alpine.js!!! and htmx
- Boring tools = good
- How would this be for new contributors?
- Compared to React & vanilla JS
- Looking at Wagtail’s contributor base in particular
Actions review
- ✅ Thibaud Share good resource on design tokens (thank you Coen, https://spectrum.adobe.com/page/design-tokens/)
- ✅ Thibaud Look into ways to automate checking which PRs might have UI changes
- Thibaud Prettier semi-automated PR conflict fixes step-by-step
- Thibaud Try out Storybook composition
- Fabien Review RTL support plans
- ✅ Thibaud First draft of feasibility review with build per component
  - https://docs.google.com/spreadsheets/d/1l7tnpEyJiC5BWE_JX0XCkknyrjxYA5T2aee5JgPnmi4/edit#gid=702715712
- ✅ LB Follow up on Django-friendly frontend customisations in chat
  - General gist - we need to make sure we support lots of customisations through Django
  - A simple example, adding classes - this should work for lots of things and be able to be done in Django land
Prettier
- Spaces for HTML? 4
- Spaces for JS? 2
- Spaces for CSS? 2
- Single quotes
- We want to be different (but don’t care that much)
- https://github.com/wagtail/wagtail/compare/main...thibaudcolas:chore/prettier-setup?expand=1
- JSON, YAML: yes
- Markdown: no
- djhtml
Components review
- https://docs.google.com/spreadsheets/d/1l7tnpEyJiC5BWE_JX0XCkknyrjxYA5T2aee5JgPnmi4/edit#gid=702715712
- Django review
- Messages -- use vanilla Django
- Error lists
- StructBlock validation -- can only attach error messages to blocks within StructBlock, not at the StructBlock level
  - Potentially the same for StreamBlock, ListBlock
- "It's very functional if you are sighted and have good motor skills"
- Styleguide
  - (It's not very good)
Webpack + other tooling upgrades
- Stylelint
- Stylelint declaration-strict-value: Set up declaration-strict-value rule to enforce usage of variables stylelint-config-wagtail#9
- Stylelint RTL styles enforcement: Use stylelint built-in rules to disallow left/right positioning stylelint-config-wagtail#10
- RTL
- Consideration of word width
- Order of properties: https://github.com/hudochenkov/stylelint-order
  - Would be nice if automate-able, otherwise might not be worth it? Yes it's auto-fixable
  - Mixins first
  - Sample: https://github.com/thibaudcolas/stylelint-config-cookbook/blob/main/src/config.js#L93
- Modern CSS: https://github.com/ismay/stylelint-no-unsupported-browser-features

2021-12-16 UTC evening

Attendees: Thibaud, Fabien, Steven, LB, Coen

Apologies: Naomi

Actions

Thibaud Share good resource on design tokens
Fabien Review Thibaud's RTL plans
Thibaud First draft of feasibility review with build per component
LB Follow up on Django-friendly frontend customisations in chat
General gist - we need to make sure we support lots of customisations through Django
A simple example, adding classes - this should work for lots of things and be able to be done in Django land

Discussions

Backlog review!
- Below -- everything Thibaud is planning to do ahead of starting the page editor redesign's builds in February
- Areas you'd like to be involved with: 🥭 Naomi, 🍎Coen, 🍐 Fabien, 🍑 LB, 🍒 Scott, 🍓 Steve
- 🍋 immediate priority for Thibaud
- 💥: needs further validation / sounds silly / are you sure about this?
Page editor 2022 backlog -- planning
- Design feasibility review🍋 🍓
- Design accessibility review🍋
- Project scoping / backlog refinement🍋
- Spikes / PoC for specific features (quick nav / minimap)
- Breaking changes review🍋
- GitHub issues / existing PRs review 🍑
Page editor 2022 backlog -- code changes
- Design tokens setup🍓
  - Design tokens as JS files
  - Tailwind theme to reuse design tokens in stylesheets🍓
  - npm package to share design tokens (& eventually UI components) to maintain consistency across other projects 🍎🍓
- Design system's UI components setup
  - Sass + BEM + ITCSS for UI component styles🍓
  - Tailwind for basic utility classes (spacing, grid) and dead CSS removal. 🍓
  - Django templates + vanilla JS/TS OR React (TS only) for UI component markup & behavior 🍐 🍓
  - django-pattern-library + Storybook to🍋 🍎🍐 🍓
  - RTL 🍐
- Static analysis overhaul
  - Prettier for automated formatting 🍐 🍑 🍋
  - djhtml for automated formatting 🍐 🍋
  - Stylelint config ++: disallow hard-coding any value that is a design token, consistent spacing, consistent usage of RTL-friendly styles 🍑 🍋
  - ESLint config ++: update to recent version of current setup 🍑 🍋
- UI testing
  - Using the tests project within Wagtail as a manual UI testing environment with dedicated fixtures 🍎
  - Automated browser accessibility test suite in CircleCI #7751 🍋🍎
- Tech debt
  - Gulp -> Webpack
  - Windows compatibility
  - IE11 hacks / cruft removal🍋
Design tokens --fundamental units of design systems reuse
jQuery future?
- Disallow with linting rule
- Not necessarily a goal on its own but we want to do this alongside other work
- Also makes it easier to write unit tests for this code
React -- where do we want to use it?
- Choosers?
- htmx -- is there a place for it?
- Potentially -- more lightweight than React, easier to work with for Django devs
- Alpine? Same question
- htmx --AJAX calls
POC? 🍐
Windows compatibility
- Frequent questions on Slack
Wagtail as a platform
- Collaborative editing & autosave
RTL support
- Fabien has clients needing this
- And some experience
Wagtail as a Django CMS
- For example needing to do forms in a Django formset/widget/field friendly way

2021-12-02 New team kickoff

Actions

Not this time

Discussions

Attendees:

Welcome & introductions
What do we all want to achieve with the new team?
- Thibaud
  - Automated tests
  - Pattern library / design system setup
  - Stronger baseline for UI enhancements
  - Having a group of people to run things past at the planning level & code review
- Naomi
  - Return to CSS refactoring from however many years ago :)
  - Modular CSS
  - Pattern library
  - A robust enough design system set up so developers can reuse components as-is
  - Utilities for things like e.g. spacing, not semantic
  - Sass vs SCSS (Naomi "SCSS is the better choice (for an open source project")
- Scott
  - Using Wagtail for 6 years now! Pre 1.0
  - Core team since 2020
  - Working at NASA JPL, Wagtail users in federal govt
  - Headless Wagtail! w/ Nuxt & Vue
  - UI team -- continuation of accessibility team
  - HTML semantics & quality designs FTW
- Fabien
  - Based in France! Worked with Torchbox a few months ago
  - Also headless!
  - Also Google Meet refreshes :)
  - Keeping track of front-end discussions for a bit. Wanting to see a Wagtail design system happen
  - Could be useful for client work
  - React experience & JS in general
- LB
  - Core team for 4 years!
  - Also a 2 year old :)
  - Full time job 100% front-end, React, Sass (SCSS!).
  - Getting this set up so they are easy to develop
  - Making JS stuff in Wagtail as easy to customise & extend as the Python
  - Making JS customisations more approachable
  - Keen on design systems, & accessibility
- Coen
- Ben
- Steve
IE11!
- Officially out
- But still a problem for some teams
How the team works
- Initial plan: open membership, 45-min chats every so often, 6 months term
- Video software
  - Zoom 👍(Naomi)(LB)(Scott)
  - Meet 👍👍(LB)
- Other options very welcome?
- Meeting schedule options:
  - Every week -- Align with core team meetings? 👍
    - Technically every other week for people in the US & Australia
    - Either right before or right after
  - Every week -- Identical time but opposite week of core team meetings? 👍
    - Technically every other week for people in the US & Australia
    - UTC morning core team meeting = UTC afternoon UI team, & vice versa
  - Every week -- switching between 3 slots? 👍👍
    - Thursdays
    - Tuesdays or thursdays (wednesday & friday for LB)
    - UTC morning (Asia + Pacific + Europe)
    - UTC afternoon (Europe + Americas)
    - UTC evening (Americas + Asia + Pacific) 👍
  - Kickoff time + 30min
- Change the core team to rotate between three times
- Something else?
- 6 months membership?
Core team meeting at 9pm UTC? Ideally 9:30pm
Pros & cons of pattern libraries
- Makes it easier to add components, but harder to make new components
Board!
- https://github.com/wagtail/wagtail/projects/13
Accept access requests

0 replies

thibaudcolas · 2022-04-07T16:41:54Z

thibaudcolas
Apr 7, 2022
Maintainer Author

2022-04-07 UTC afternoon

Attendees: Karl, Naomi, Scott, Thibaud, Harris

Highlights

We have a new team member, @kaedroho!
Storybook now contains auto-generated documentation for some of our design tokens: colors, text styles, brand font, and icons. Demo: Contrast Grid, screenshot of color palette.
We’re going to be refactoring the admin’s CSS files so we load one stylesheet for the whole of the admin, rather than different stylesheets per view. With the exception of widgets which have their own widget-specific stylesheet.

Actions

Thibaud PR to combine stylesheets
Scott Review PR to combine stylesheets
Scott review PR with storybook-django docs extraction

Actions review

✅ LB Feedback on forms markup (PR) / live demo
✅ Thibaud Push PR with forms markup for code review + post link to UI channel
✅ Thibaud PR with storybook-django docs extraction
Scott review PR with storybook-django docs extraction
Moved regularly-postponed actions we currently don't have time for to our board.

Discussions

Welcome Karl!
- Dabbles in JavaScript :)
- Keen to be more involved with UI decisions
- Working on the page editor project currently
Forms markup
- Feedback has been helpful
- Trying to get this into Wagtail 3.0
- Risk not getting this into the release (7 days to go)
- Should we consider pushing back this specific release?
- Core team open to the idea, we'll see how we go until Friday
- Page editor team will be doing RC testing
Interested in joining: Hazho Human (Singapore TZ)
- Not many meeting times work well with this time zone
- Invite sent for UTC morning meeting on 14/04
Storybook documentation demo
- Documented design tokens: colors, type scale, font family
- Auto-generated icons grid
- It works
- Color contrast: Contrast Grid
- WCAG 3.0
- Thibaud lightning talk
- That's exciting
CSS output files refactoring
- Write really good CSS & Be Naomi
- Potentially dangerous to do this refactoring
- Widgets & template components can pull in extra CSS (Media)
- Combine normalize.scss & jQuery UI & jQuery Datetimepicker & core.css

0 replies

thibaudcolas · 2022-04-21T11:00:16Z

thibaudcolas
Apr 21, 2022
Maintainer Author

2022-04-14 UTC morning

Attendees: LB, Thibaud

Highlights

Wagtail now has an official monospace font.
We have a lot of solid proposals for the two GSoC projects where the UI team will be involved.
We’re interested in refactoring Wagtail’s styles so there is only one global stylesheet, with separate stylesheets for given components only (specific widgets or panels – but not for layouts).

Actions

LB Review monospace font stack PR
✅ LB review the high contrast proposal(s) -- done, minor comments
Thibaud Research JS parsers pulling JSDoc comments (Esprima)
✅ Thibaud review GSoC proposals
LB to create a Google Doc to outline how we could better structure the UI guidelines (see notes below)
✅ LB Try out fnm again: worked great

Actions review

Thibaud PR to combine stylesheets
- Started. I'm going to bite the bullet and combine all stylesheets at once.
Scott Review PR to combine stylesheets
- Waiting for Thibaud's PR
✅ Scott review PR with storybook-django docs extraction
- Reviewed: Update UI guidelines & UI development docs #8304

Discussions

Single css
- Draftail - stylesheet for widgets only
- Small use / standalone widget
  - Component based if really needed
- User bar
- Everything else will be one sheet (inc. auth forms)
  - Contrib - not really much reason for them to have their own stylesheets
Lexical vs Draft.js
- https://prosemirror.net/
- https://trix-editor.org/
- https://tiptap.dev/
- New name? New research?
Monospace font stack Monospace proposed stack (Issue #8043): #8338
- For the CMS and outside
- Defined in tokens
- Sass reusing tokens from Tailwind
- LB reviews
Proposal reviewing and feedback for GSoC - Windows high contrast and styling UX
- LB reviewed
- Thibaud review next
- Couple of solid proposals, a few ok, extended timeline (not keen)
- WHCM proposal
- Solid contributors involvement so far
fnm
- Does it work?
- LB
- New dotfile?
UI guidelines -- is "UI" clear enough? Are we happy to have visual design, UX, front-end info all on the same page?
- Keen to proceed with UI
- Needs to be more cross-functional
- Let's make an outline
- Assign sections
- Things to consider
  - Naming conventions
  - When/where to use tailwind classes vs apply
  - Consider the audience/abstractions (remember we are writing for various audiences, including those that want to build on top & customise, all the way through to those that use the UI every day of their working week)
  - Testing!

0 replies

thibaudcolas · 2022-04-22T10:59:48Z

thibaudcolas
Apr 22, 2022
Maintainer Author

2022-04-21 UTC evening

Attendees: Karl, Steve, LB, Thibaud, Naomi, Scott

Highlights

We are drafting new proposed UI development guidelines for maintainers, highlighting considerations for end users, maintenance, and site implementers customising Wagtail.
We’re considering how to make Wagtail’s design tokens available to people creating customisations within the CMS, with CSS variables. The first ones will be for our font stacks.
Our tabs component needs an API so it can be made reusable without copy-pasting HTML. We’re going to start with a very basic setup with Django templates’ simple template tags.

Actions

Thibaud Review LB's proposed outline
✅ LB Make CSS variable font PR for Wagtail 3.0 -> make new font stacks available as css custom properties (3.0) #8415
Thibaud Review LB's 3.0 font stack CSS variable PR
Thibaud Review LB's 4.0 font stack CSS variable PR
Thibaud Research JS parsers pulling JSDoc comments (Esprima)
Thibaud PR to combine stylesheets
- Started. I'm going to bite the bullet and combine all stylesheets at once.
Scott Review PR to combine stylesheets
- Waiting for Thibaud's PR

Actions review

✅ LB Review monospace font stack PR
✅ LB review the high contrast proposal(s) -- done, minor comments
- One proposal with solid candidate
Thibaud Research JS parsers pulling JSDoc comments (Esprima)
✅ Thibaud review GSoC proposals
✅ LB to create a Google Doc to outline how we could better structure the UI guidelines (see notes below)
✅ LB Try out fnm again: worked great
Thibaud PR to combine stylesheets
- Started. I'm going to bite the bullet and combine all stylesheets at once.
Scott Review PR to combine stylesheets
- Waiting for Thibaud's PR

Discussions

UI development docs
- https://docs.google.com/document/d/1P_ckY9GKc1V8_pvWTAqXoQ3h3NFcFbBngkPeJv-vBtg/edit?usp=sharing
- Update UI guidelines & UI development docs #8304 (comment)
- 12-sided dice!
- Merge existing PR as-is once feedback has been addressed
- Work on this iteratively over the next release
Monospace font
- Fighting with normalize
Wagtail fonts as CSS variables: Feature request: expose Wagtail’s fonts as CSS variables #8406
- w- prefix?
- Use css custom properties for new font stacks #8409 PR up
- ... And if so, should we update the other CSS custom properties
- And... are there other things we should put into CSS custom properties
  - We'll get to it when we get to it
  - Keep backwards compatibility in mind once we start defining variables
  - Colors good candidate
  - Focus outline width
Tabs reuse -- UI component API
- Feature request: UI component API for tabs #8408
- Could start with simple tags separate for start and end HTML tags
- Works, simple to set up
- There is a way to create joined tags, (block endblock), undocumented.
- Single template tag that generates the tablist item and the panel? Possible but a lot of complexity (hoist child template tag's data up to parent template)
- Relevance of TabbedInterface -- for (Django) forms definitely
- React-like children API for component tag (children prop)
- Other libraries use the Web Components style slots API
- For us -- simpler first.
Tailwind and accessible defaults
- Noticed motion-reduce:w-transition-none usd on https://github.com/wagtail/wagtail/pull/8411/files - is there any way for this to be just a global default?
- Similar to focus states, can we ensure that, by default, some accessible basics just work in our css without having to be added in each place? (tailwind or otherwise)
- Needs further discussion (do we want to disable animations for the whole of Wagtail?)

0 replies

thibaudcolas · 2022-05-05T12:28:58Z

thibaudcolas
May 5, 2022
Maintainer Author

2022-04-28 UTC afternoon

Attendees: Naomi, Scott, LB, Thibaud, Karl

Highlights

We’ve discussed how adoption of Tailwind is going so far, problems it resolves, problems it creates. There’s more needed on that front, at the very least better documentation of our methodology.
We’re keen to support more color theme customisations in Wagtail 3.0 if there is still time, if not Wagtail 4.
CSS variables to customise / reuse our fonts are coming. As a very basic behind-the-scenes stopgap for Wagtail 3, as a well thought-through setup in the next release.

Actions

Thibaud Review LB's proposed outline
✅ Thibaud Review LB's 3.0 font stack CSS variable PR
Thibaud Review LB's 4.0 font stack CSS variable PR
Thibaud PR to combine stylesheets (in progress)
Scott Review PR to combine stylesheets (Waiting for Thibaud's PR)
✅ Thibaud Research JS parsers pulling JSDoc comments (Esprima)

Actions review

Thibaud Review LB's proposed outline
✅ LB Make CSS variable font PR for Wagtail 3.0 -> make new font stacks available as css custom properties (3.0) #8415
✅ Thibaud Review LB's 3.0 font stack CSS variable PR
Thibaud Review LB's 4.0 font stack CSS variable PR
Thibaud PR to combine stylesheets (in progress)
Scott Review PR to combine stylesheets (Waiting for Thibaud's PR)
✅ Thibaud Research JS parsers pulling JSDoc comments (Esprima)

Discussions

How do we balance tailwind usage and also making it easy to create a 'tabs' or a 'button' by those that want to do it.
- Ideally without building a complex system of shared templates as components.
- Just concerned that we want reusability without having to copy/paste heads of classes.
- We want to support more components
- Site implementers reuse components w/o Tailwind knowledge
- Docs needed for common customisations
- Need to validate how appealing/repealing Tailwind is
- Appealing to Django devs?
- Poll?
- Template tags vs. partials vs. components
- We also need to consider whether this creates friction for new contributors
Colors
- Give it a go if time
- Single color as a stopgap

0 replies

thibaudcolas · 2022-05-05T12:33:42Z

thibaudcolas
May 5, 2022
Maintainer Author

2022-05-05 UTC morning

Attendees: LB, Thibaud, Karl

Highlights

We’re considering which automated documentation generators we could use for JS code (particularly for UI components & design tokens). We’re unclear of whether this is worthwhile at this stage. We need to use JSDoc more consistently as a first step.
We’re still discussing whether Wagtail needs a new lightweight JS framework to support UI component development. Next step is to get guidance from the core team on whether this does feel worthwhile to explore or not.

Actions

Thibaud Review LB's proposed UI guidelines outline
Thibaud Review LB's 4.0 font stack CSS variable PR
Thibaud PR to combine stylesheets (in progress)
Scott Review PR to combine stylesheets (Waiting for Thibaud's PR)
Thibaud Core team poll on whether we should continue investigating

Actions review

Thibaud Review LB's proposed UI guidelines outline
✅ Thibaud Review LB's 3.0 font stack CSS variable PR
Thibaud Review LB's 4.0 font stack CSS variable PR
Thibaud PR to combine stylesheets (in progress)
Scott Review PR to combine stylesheets (Waiting for Thibaud's PR)
✅ Thibaud Research JS parsers pulling JSDoc comments (Esprima)

Discussions

GSoC projects
Font stack CSS variables
- meta.inspect likely not needed
- $font-sans used way too many times
- Prefix of CSS custom properties to be confirmed (w-)?
  - Not a matter of conflicts, more to make the variables identifiable?
- Two variables, one to reuse the immutable value, one to customise what the admin uses?
- Good to consider usage of prefixes beyond font stacks
JS documentation parsers
- Documentation.js https://github.com/documentationjs/documentation
  - Thibaud used this in the past
  - It seems to work. Not terribly active project
- Other options available but seem harder to leverage
- Unclear of the value of one more tool for this
- Where does this documentation live: docs.wagtail.org, or Storybook?
  - Ideally no distinction
- Step one: leverage more JSDoc comments
- End goal: Storybook generating docs for this, hosted alongside RTD
- Django: Sphinx autodocs, used for basic description of what different APIs do, w/ little use of parameters
- Wagtail-localize uses Google-style docstrings w/ mkdocs
Lightweight framework
- Where is this at
- What do we do with it next
- Stimulus still strongest contender from LB's research, but is a very low-level library
- Core team poll

0 replies

thibaudcolas · 2022-05-27T16:04:53Z

thibaudcolas
May 27, 2022
Maintainer Author

2022-05-12 UTC evening

Attendees: Naomi, LB, Thibaud, Scott

Highlights

We’ve reviewed approaches for the Windows High Contrast mode GSoC project. There are two very different approaches. We’re leaning towards using CSS variables throughout, which still needs some validation.
We’re considering a community poll about UI customisations with CSS and HTML – how much of a need there is, what might work. Similar to the Node tooling poll.
Thank you to the core team for validating our continued research for a lightweight JS framework.

Actions

Thibaud Book accessibility team kick-off meeting
✅ LB Kickstart planning of UX project (tentative until GSoC starts)
✅ Thibaud Check with Ben plan to publish design system
Thibaud Review LB's proposed UI guidelines outline
Thibaud Review LB's 4.0 font stack CSS variable PR
✅ Thibaud PR to combine stylesheets (in progress)
Scott Review PR to combine stylesheets (Waiting for Thibaud's PR)
✅ Thibaud Core team poll on whether we should continue investigating lightweight JS framework

Actions review

Thibaud Review LB's proposed UI guidelines outline
Thibaud Review LB's 4.0 font stack CSS variable PR
✅ Thibaud PR to combine stylesheets (in progress)
Scott Review PR to combine stylesheets (Waiting for Thibaud's PR)
✅ Thibaud Core team poll on whether we should continue investigating lightweight JS framework

Discussions

Approach for Windows High Contrast Mode GSoC project: overlap with theming support
- UI team guidance will help make the most of this project
- Case-by-case overrides, or redo our approach to colour tokens?
- Better support for multiple themes, not just high-contrast modes
- Make variables as part of making overrides
- Make more variables when we encounter new use cases
- Approach sounds good but doesn't completely remove the need for overrides
- Refactor code if possible rather than rely on overrides?
- Variables: naming hard, aside from that making a variable is straightforward
- Tough case to consider: legacy dropdown
- Variables structure: descriptive of values, or usage?
- Variable layers: single, multiple?
- For overrides, go with usage (button, button-border)
- Layers: https://spectrum.adobe.com/page/design-tokens/#Design-token-types
- Mixed usage of global variables & semantic aliases currently
- Do this gradually (dependent on skillset?)
- Practical next step: review current @media forced-colors overrides
- Clear tasks for contributor: page-by-page assessments
- Mentor guidance to figure out when to refactor to custom properties (provide examples)
- Idea - start with something like --w-icon-fill (maybe make the default as transparent in :root) and then add a global @media (forced-colors: $media-forced-colours)
  - wagtail/admin/static_src/wagtailadmin/scss/layouts/home.scss - li.icon::before, li svg.icon color: $system-color-link-text;
  - wagtail/admin/static_src/wagtailadmin/scss/userbar.scss - userbar-icon fill: $system-color-link-text; (note: this may not use the custom properties?)
  - client/scss/components/_icons.scss - .icon fill: $system-color-link-text;
- Refactoring to variables still valuable even when partially done
- BEM pet-peeve: .component--modifier or &--modifier
  - Rule of thumb: &::before only, not for partial classes?
  - $root: #{&};
UX page editor project
- Same need for implementation & planning guidance
- Wagtail 4.0 release code freeze mid-July
- https://www.figma.com/community/file/1098619062654073532
Poll for UI customisation requirements
- What questions do we want to ask?
- CSS variables vs. utility classes vs. BEM components
- Reminder - we should ask on Slack and GitHub Discussions
- Terminology - customising not overriding
- Focus on what you do rather than what you want
  - How do you customise the look of Wagtail in your project?
  - Methodology / approach to writing styles
  - Which components do you customise / reuse?
  - Preferred way of customising things in <systems like Wagtail>: stylesheet, template overrides, JS
  - Building custom things within Wagtail
  - Survey completion goal: 2min
  - Keep it simple in Slack? Emoji responses, threads
  - Expect few answers, things to consider rather than comprehensive results
Writing JS code in a lot of different ways currently (:
- Wouldn't it be nice if we had a lightweight blazing-fast framework so we didn't have to init tabs
- Still making improvements even if there is a lack of consistency
- Can always refactor later (;

0 replies

thibaudcolas · 2022-05-27T20:09:11Z

thibaudcolas
May 27, 2022
Maintainer Author

2022-05-19 UTC afternoon

Attendees: Thibaud, Karl, Naomi, Steve, Scott

Highlights

With the UX Unification project going ahead, we’re considering how best to support it, and what to aim for in Wagtail 4 in particular.
We discussed our usage of ITCSS to structure stylesheets. We’re still happy with it.
Steve’s latest {% dialog %} component PR is a good example of ITCSS + BEM + Tailwind, and of using template tags for components.

Actions

✅ Thibaud Book accessibility team kick-off meeting
Thibaud Review LB's proposed UI guidelines outline
✅ Thibaud Review LB's 4.0 font stack CSS variable PR
Scott Review PR to combine stylesheets (Waiting for Thibaud's PR)

Actions review

Thibaud Book accessibility team kick-off meeting
✅ LB Kickstart planning of UX project (tentative until GSoC starts)
✅ Thibaud Check with Ben plan to publish design system
Thibaud Review LB's proposed UI guidelines outline
Thibaud Review LB's 4.0 font stack CSS variable PR
✅ Thibaud PR to combine stylesheets (in progress)
Scott Review PR to combine stylesheets (Waiting for Thibaud's PR)
✅ Thibaud Core team poll on whether we should continue investigating lightweight JS framework

Discussions

New team member?
- Hazho invited next week
Project: Wagtail UI consistency (aka UX Unification)
- Goal: Apply our new visual language to the whole admin for Wagtail 4.0
- Implement new editing forms UX (fields, choosers) via Google-sponsored page editor project
  - Reskin other parts of Wagtail (dashboard, page listing) via GSoC project
  - Deliver more UX improvements to other parts of Wagtail with regular contributors
  - Improve process for delivery of UI changes: triage, backlog refinement, build
Page editor features rollout as part of snippets overhaul
- Work by Sage
- Header & side panels
ITCSS - are we still really doing this?
- We had a discussion about BEM the other week, however our development docs state we also follow BEM + ITCSS + Tailwind
- Considering the 'Apply UX project' goes through, it would be good to be clear on our direction here.
- Core change to move away from u pre-fixed classes u-hidden to w-hidden - does this indicate a move away from ITCSS?
- https://github.com/wagtail/wagtail/blob/main/client/scss/core.scss - explains the folder structure, prefix approach and others
- https://docs.wagtail.org/en/latest/contributing/ui_guidelines.html#css-guidelines - explains a different approach
- How do we get to a clearer picture here?
GSoC - UX Unification
- Draft project plan with enabling work required https://docs.google.com/document/d/1veKry2dQ60ZjEGnYnWr3JXiS3ljvRw1DUeuVotXaz5w/edit#
- Note: LB decided on this name instead of 'Apply Page Editor UX to all of Wagtail'
New {% dialog %} UI component Add new dialog UI component #8475
- New dialog component #8513 - Tailwind using apply version
- Dialog component css version #8541 - BEM (not ITCSS) and uses Tailwind as the theme (aka variable) provider with a small amount of apply usage (not sure why)

0 replies

thibaudcolas · 2022-05-27T20:13:26Z

thibaudcolas
May 27, 2022
Maintainer Author

2022-05-26 UTC morning

Attendees: Thibaud, Paarth

Actions

Scott Review PR to combine stylesheets

Actions review

✅ Thibaud Book accessibility team kick-off meeting
✅ Thibaud Review LB's proposed UI guidelines outline
✅ Thibaud Review LB's 4.0 font stack CSS variable PR
Scott Review PR to combine stylesheets

Discussions

GSoC - UX Unification – Draft project plan with enabling work required https://docs.google.com/document/d/1veKry2dQ60ZjEGnYnWr3JXiS3ljvRw1DUeuVotXaz5w/edit#

0 replies

thibaudcolas · 2022-06-02T21:32:48Z

thibaudcolas
Jun 2, 2022
Maintainer Author

2022-06-02 UTC evening

Attendees: Thibaud, Naomi, Scott, LB

Highlights

LB is going to prepare an RFC for the adoption of Stimulus as a lightweight JS framework in Wagtail, based on his recent research and core team discussions.
There are a few supporting tasks we’re going to go through imminently to support GSoC UI contributors: docs overhaul, folder structure cleanup, basic visual regression testing setup
We’re working on a backlog of UI tasks that are well defined and ready to be picked up by new contributors with dedicated support (not "good first issues")

Actions

Thibaud Read https://github.com/lb-/wagtail/pull/4 ABOUT.md
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
LB Draft RFC :) for lightweight framework
Scott Review PR to combine stylesheets #8564

Actions review

Scott Review PR to combine stylesheets #8564

Discussions

Shirts with patterns
Podcasts (who has the time for 1h30)
Our new team members, Paarth, Helen
GSoC - UX Unification
- Draft project plan with enabling work required https://docs.google.com/document/d/1veKry2dQ60ZjEGnYnWr3JXiS3ljvRw1DUeuVotXaz5w/edit#
- Helpful pre-work; UI Tables adoption, Classed based views adoption (PR review request migrate Home (dashboard) to class based view #8382) Update: this PR is now merged but other views needed
- Plan for sprints with Paarth
- Preparatory work by UI team (Thibaud & LB)
Interest in UI/UX tasks from Vibhuti (GSoC candidate for Editors' guide)
- UI up-for-grabs project: https://github.com/orgs/wagtail/projects/6/views/1
- 10-15 tasks set aside for new contributors with support like in this case
Lightweight framework
- Update from 18th of May - discussed at core team and asked that we do need some direction
- Matt had some great feedback UI architecture technical debt #7689 (comment)
- End to end code for two core-ish components (skip to link & upgrade notification)
- https://github.com/lb-/wagtail/pull/4
- Posted to get feedback UI architecture technical debt #7689 (reply in thread)
- Two components; simple ones but enough to see the changes are not too huge based on our existing conventions
- Auto inclusion of controllers (opt in via controller static methods) - inspired by https://stimulus.hotwired.dev/handbook/installing#using-webpack-helpers
- Typescript end to end (including stimulus loading)
- Unit tests (including async updates)
- Basic Documentation (including how to add custom stimulus components for Wagtail customisations)
- Basic Developer documentation (including as baseline eslint setup so that we have some consistency as we add new controllers).
- Not sure it really got much buy in from the core team, but no major push back :)
- Would be good to see things like the chooser modal JS align to some kind of convention though - Refactor out duplicated code from chooser modal JS #8532 vs the tabs work - they have completely different approaches but both trying to do a similar thing (a JS class that attaches behaviour to a DOM) https://github.com/wagtail/wagtail/blob/main/client/src/includes/tabs.js .
- We also ran into issues where the tabs were not initiated in the right way in some cases which is a problem we could avoid with the proposed approach https://github.com/wagtail/wagtail/pull/8529/files
- RFC?
- Lack of feedback isn't necessarily a bad sign
- RFC!

UI Development Documentation - few points to agree/dicss regarding styles structure

1. Folder structure (SCSS/CSS/Styles)

A. SCSS/Styles - rename scss to styles & incorporate all tailwind stuff in that folder
- 👍

B. ITCSS - remove 'objects' - RECOMMENDATION: We scrap this - it is barely used "Do not overuse objects (or omit them completely)" https://www.xfive.co/blog/itcss-scalable-maintainable-css-architecture/#do-not-overuse-objects-or-omit-them-completely

3 objects only exist (avatar - can be a component, pill - can be merged with status as that is all that is used, icon - soon to be legacy)
Remove objects/ folder and move styles to other folder

Remove objects from table on

wagtail/client/scss/core.scss

Lines 19 to 20 in 1f43d8e

    
           │ objects    │ classes                │ 5 Objects    │ o-     │ 
        
           │            │   layout               │              │        │

Note: Plan is to document these folders purposes in the new UI documentation

3. Folder structure (src - JS/TS)
- A. Make components just for React components (mostly as is)
  - 👍(yes)
  - READMEs in folders
  - Risk of de-sync with contributors documentation?
  - Use READMEs to describe file structure
- C. Make 'adapters' folder for code that is a JS side Telepath adapters
  - README.md: "This is for Telepath "adapters" (classes? thingies?). Here is a link to our documentation".
- D. Rename 'entrypoints' to 'modules' - entrypoints is a Webpack specific term but modules better reflects what these are and how they are used, it will also help us move our thinking towards an ES6 module approach in the future.
  - Describe with a README, keep the cryptic but specific folder name
- E. Remove 'config' as this could be confusing (is this config for the project, no it is a global config object setup), we can move this to includes for now but longer term we can find a better way to do this I think.
  - Leave for now

"burn that bridge when we get to it"
"Can't lead a dead horse to water"

0 replies

thibaudcolas · 2022-07-11T20:03:01Z

thibaudcolas
Jul 11, 2022
Maintainer Author

2022-06-09 UTC afternoon

Attendees: Harris, Naomi, Thibaud

Highlights

RFC 78 Stimulus has been published by LB!
We discussed stricter ESLint & stylelint linting rules to help enforce some of our development guidelines, in particular rules on CSS selectors and class names.

Actions

Thibaud Read RFC 78 Stimulus
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog

Actions review

Thibaud Read https://github.com/lb-/wagtail/pull/4 ABOUT.md
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
✅ LB Draft RFC :) for lightweight framework

Discussions

Wagtail UI components & views overview
- Pa11y
- Backstop
  - Demo next week + looking for volunteers
RFC 78 Stimulus
- Needs further review
UI Development Documentation - few points to agree/dicss regarding styles structure
- 1. - see last meeting - resolved then.
- 2. Apply more strict stylelint items
  - Summary: Limit nesting to 2 levels. Many developers think that using the parent selector (&) is a requirement just because they use Sass. There’s nothing wrong with flat structure with full selectors expanded, either. Often it’s easier to scan and search the code.
  - A. Add ability to enforce BEM classes with prefix #19
  - B. Add ability to block union classes (via parent selector) #20
  - C. Introduce selector-max-combinators, selector-max-specificity & max-nesting-depth #21
  - D. Block `@apply` (force usage of theme) - implies we are happy to unravel any existing apply usage
- 3. Folder structure (src - JS/TS)
  - F. Remove ‘api’ folder, this is one of the earliest folders in the client folder; the api/admin.ts would move to includes and the api/client would move to utils (as this is a generic wrapper around fetch).
  - Note: Plan is to document these folders purposes in the new UI documentation. Also, plugins/tokens would move to the styles folder.
- 4. Revisions to eslint
  - A. Add must use named export - discussion on slack, seems we are ok with this, aligns with what we are mostly doing already (except React Components)
  - B. Remove class methods must use this - not really how we are doing things currently, promoting static methods in these cases has other caveats (cannot be inherited)
  - C. Remove 1 class per file only - not really how we are doing things (not even in React code), and supports the approach of ‘it is ok to have one file do a few things with named exports’
  - D. Revise `'lines-between-class-members'` less strict - allow one liners (e.g. static methods / typescript declarations) to not need the new line. 'lines-between-class-members': ['error','always',{ exceptAfterSingleLine: true },]
UX Unification
- Breadcrumbs!

0 replies

thibaudcolas · 2022-07-11T20:05:21Z

thibaudcolas
Jul 11, 2022
Maintainer Author

2022-06-16 UTC morning

Attendees: Thibaud, Paarth, Helen, LB

Highlights

The UX Unification project is currently tackling breadcrumbs and headings

Actions

Thibaud Read RFC 78 Stimulus
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
Thibaud Draft next version of UI development docs
Helen Review next version of UI development docs

Actions review

Thibaud Read RFC 78 Stimulus
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog

Discussions

What’s up?
Backstop
- Demo next week + looking for volunteers
UI Development Documentation - few points to agree/dicss regarding styles structure
- 1. - see last meeting - resolved then.
- 2. Apply more strict stylelint items
  - Summary: Limit nesting to 2 levels. Many developers think that using the parent selector (&) is a requirement just because they use Sass. There’s nothing wrong with flat structure with full selectors expanded, either. Often it’s easier to scan and search the code.
  - A. Add ability to enforce BEM classes with prefix #19
  - B. Add ability to block union classes (via parent selector) #20
  - C. Introduce selector-max-combinators, selector-max-specificity & max-nesting-depth #21
  - D. Block `@apply` (force usage of theme) - implies we are happy to unravel any existing apply usage
- 3. Folder structure (src - JS/TS)
  - F. Remove ‘api’ folder, this is one of the earliest folders in the client folder; the api/admin.ts would move to includes and the api/client would move to utils (as this is a generic wrapper around fetch).
  - Note: Plan is to document these folders purposes in the new UI documentation. Also, plugins/tokens would move to the styles folder.
- 4. Revisions to eslint
  - A. Add must use named export - discussion on slack, seems we are ok with this, aligns with what we are mostly doing already (except React Components)
  - B. Remove class methods must use this - not really how we are doing things currently, promoting static methods in these cases has other caveats (cannot be inherited)
  - C. Remove 1 class per file only - not really how we are doing things (not even in React code), and supports the approach of ‘it is ok to have one file do a few things with named exports’
  - D. Revise `'lines-between-class-members'` less strict - allow one liners (e.g. static methods / typescript declarations) to not need the new line. 'lines-between-class-members': ['error','always',{ exceptAfterSingleLine: true },]
UI Development Documentation – Actions - should we prepare a draft PR for feedback with the development docs updated? (note: we should do the dev docs before we do any moving around)
- Codify what we’re doing already – will be a good step
UX Unification
-Breadcrumbs progress
- Need design direction for header content - UX Unification - header component with variations #8539
BackstopJS

0 replies

thibaudcolas · 2022-07-11T20:07:38Z

thibaudcolas
Jul 11, 2022
Maintainer Author

2022-06-23 UTC evening

Attendees: Scott, Thibaud, Naomi

Highlights

We reviewed the UX Unification project’s scope via the Wagtail 3.0 UI Inventory, and discussed naming of new button variations.
We looked at a demo of Backstop.js as it was used to generate the UI inventory

Actions

Thibaud Read RFC 78 Stimulus (in progress)
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
Thibaud Draft next version of UI development docs
Helen Review next version of UI development docs

Actions review

Thibaud Read RFC 78 Stimulus (in progress)
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
Thibaud Draft next version of UI development docs
Helen Review next version of UI development docs

Discussions

UX Unification
- UI inventory
- Breadcrumbs
  - Dropdown with actions?
  - Whole page path
  - Root > Welcome to the Wagtail Bakery! > Blog > The Greatest Thing Since Sliced Bread History ⌄
  - Dropdown label is current view’s name
- Breadcrumbs collapsing
  - Pages > … > Parent… > Current page Edit ⌄
  - When click on the ellipsis for hidden breadcrumbs, pop up a dropdown with a vertically-stacked list of what was hidden
- Headers search
  - Need a way to sort by title
- Buttons
  - Nomenclature
  - Ghost vs. secondary vs. black & white vs. outline
    - Primary / secondary / tertiary
  - Destructive / Danger
    - Destructive for buttons
  - Ghost w/ icon
    - Feels promising, worth trying
    - Only with filled circle (button-y & high-contrast)
Very fashionable meeting
Backstop demo

0 replies

thibaudcolas · 2022-07-11T20:10:46Z

thibaudcolas
Jul 11, 2022
Maintainer Author

2022-06-30 UTC afternoon

Attendees: Jacob, Paarth, Thibaud

Highlights

We reviewed a demo of upcoming rich text editor features
The slim header component is coming to page explorer listings

Actions

Jacob Talk to Jake / performance team about perf implications of live-reloading preview
Thibaud Read RFC 78 Stimulus (in progress)
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
Thibaud Draft next version of UI development docs
- Helen Review next version of UI development docs
Jacob Review in-Draftail implementation

Actions review

Thibaud Read RFC 78 Stimulus (in progress)
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
Thibaud Draft next version of UI development docs
Helen Review next version of UI development docs

Discussions

UX Unification
- Headers
  - Adding slim header to listing views (scoping work to do)
- Breadcrumbs
  - Adding breadcrumbs to other parts of the admin (CRUD views)
Welcome Jacob!
- Core team member, doing lots of stuff with React. Interested in discussions about Draft.js
Rich text block picker demo
- Pull request reviews for Draftail
  - Thank you Jacob for volunteering
- Controls API – breaking change
- Plugins
Preview panel work from Sage
- Shock of having the preview moved elsewhere?
  - Should be ok, lots of things are moving, new version is much better
  - “Intro to Wagtail 4” video
- Refresh
  - Button – do we want it there
- Error state
  - Overlap is nice
  - Avoid shifting compared to previous version
- Loading state
  - Refresh button with spinning icon vs. “Updated x seconds ago” status message
- Performance implications
  - Length of preview loading
  - Delay based on duration of last request?
- Preview mode
  - Would be better at the top
  - Tab order doesn’t match visual element order
- Userbar in preview page
  - Don't render edit link in userbar on previewed pages #8766
  - Jacob agrees hiding Edit would be nice

0 replies

thibaudcolas · 2022-07-11T20:14:25Z

thibaudcolas
Jul 11, 2022
Maintainer Author

2022-07-07 UTC morning

Attendees: Fabien, Thibaud

Highlights

We’re interested in taking RTL support to completion. Two important steps are the removal of float layouts and icons mirroring.

Actions

✅ Thibaud Invite Jacob to whole series of meetings & GitHub team
Fabien Trial float refactoring
Jacob Talk to Jake / performance team about perf implications of live-reloading preview
Thibaud Read RFC 78 Stimulus (in progress)
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
Thibaud Draft next version of UI development docs
- Helen Review next version of UI development docs
✅ Jacob Review in-Draftail implementation

Actions review

Jacob Talk to Jake / performance team about perf implications of live-reloading preview
Thibaud Read RFC 78 Stimulus (in progress)
Harris Read RFC 78 Stimulus
Thibaud Prepare 10-15 tasks in UI up-for-grabs backlog
Thibaud Draft next version of UI development docs
- Helen Review next version of UI development docs
Jacob Review in-Draftail implementation

Discussions

RTL support: float removal
RTL support: icons mirroring
-Decide case by case for each icon
- Review w/ Arabic / Farsi speakers

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Wagtail UI team: meeting updates #8265

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 15 comments

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Wagtail UI team: meeting updates #8265

thibaudcolas Mar 31, 2022 Maintainer

Replies: 15 comments

thibaudcolas Mar 31, 2022 Maintainer Author

2022-03-31 UTC evening

Highlights

Actions

Actions review

Discussions

2022-03-24 UTC morning

Actions

Actions review

Discussions

2022-03-17 UTC afternoon

Actions

Actions review

Discussions

2022-03-10 UTC evening

Actions

Actions review

Discussions

2022-03-03 UTC morning

Actions

Actions review

Discussions

2022-02-24 UTC afternoon

Actions

Discussions

2022-02-17 UTC evening

Actions

Discussions

2022-02-10 UTC morning

Actions

Discussions

2022-02-03 UTC afternoon

Actions

Discussions

2022-01-27 UTC evening

Actions

Discussions

2022-01-20 UTC morning

Actions

Discussions

2022-01-13 UTC afternoon

Actions

Discussions

2022-01-06 UTC evening

Actions

Discussions

2021-12-16 UTC evening

Actions

Discussions

2021-12-02 New team kickoff

Actions

Discussions

thibaudcolas Apr 7, 2022 Maintainer Author

2022-04-07 UTC afternoon

Highlights

Actions

Actions review

Discussions

thibaudcolas Apr 21, 2022 Maintainer Author

2022-04-14 UTC morning

Highlights

Actions

Actions review

Discussions

thibaudcolas Apr 22, 2022 Maintainer Author

2022-04-21 UTC evening

Highlights

Actions

Actions review

Discussions

thibaudcolas May 5, 2022 Maintainer Author

2022-04-28 UTC afternoon

Highlights

Actions

Actions review

Discussions

thibaudcolas May 5, 2022 Maintainer Author

thibaudcolas
Mar 31, 2022
Maintainer

thibaudcolas
Mar 31, 2022
Maintainer Author

thibaudcolas
Apr 7, 2022
Maintainer Author

thibaudcolas
Apr 21, 2022
Maintainer Author

thibaudcolas
Apr 22, 2022
Maintainer Author

thibaudcolas
May 5, 2022
Maintainer Author

thibaudcolas
May 5, 2022
Maintainer Author

thibaudcolas
May 27, 2022
Maintainer Author

thibaudcolas
May 27, 2022
Maintainer Author

thibaudcolas
May 27, 2022
Maintainer Author

thibaudcolas
Jun 2, 2022
Maintainer Author

thibaudcolas
Jul 11, 2022
Maintainer Author

thibaudcolas
Jul 11, 2022
Maintainer Author