Attendees
- Steve Piercy
- Víctor
- Alin
- Tiberiu
- Fred
- Claudia
Agenda/Notes
Events and time zone support
These critical features are in Classic UI but are missing in Volto. Scheduling PloneConf and regular Plone team meetings.
- Download .ics or .ical file.
- Events do not display a timezone #151
- Cannot set events with a user preferred time zone #141
- Cannot set events with a user preferred time zone plone/volto#5324
Documentation
- Feedback needed: [docs] Reorganize content in README.md #5437
- Reorganize documentation using diataxis and this toplevel structure: https://docs.django-cms.org/en/latest/
- Feedback needed: [DOCS] Missing Volto generator defaults documentation #5439
- Google Season of Docs
- Google Season of Docs | Google for Developers
- Targets professional technical writers, unlike GSoC which targets students.
- Accepted organizations will receive between US$5,000 and US$15,000 to use for a documentation project.
- Apply mid-February - mid-March, 2024.
- Steve Piercy will talk with Paul Roeland about getting it started.
- Post to Community, and create a PLIP in Documentation, to collect ideas for ‘scoped’ writing project from other community members and point them to the purpose of the application/project.
- Ideas to apply for GSoD needed by the end of January 2024.
Open Issues
- Volto Team Meeting Project Board: Volto Team Meeting · GitHub
- Monorepo is in place (any question, problem about it?) (All in with monorepo by sneridagh · Pull Request #5409 · plone/volto · GitHub)
- Create a community.plone.org explaining the monorepo and pointing to the right docs
- @plone/client transfer to the monorepo (Initial transfer of client in the monorepo. Cleanup. by sneridagh · Pull Request #5490 · plone/volto · GitHub)
- Discussion on older components to move to monorepo structure:
- docs folder: keep it in the root, it is not consumed or uses other packages. Future improvement: remove docs/source sub folder
- api folder:
- naming can be confusing, api / content / backend /frontend
- maybe remove api folder because it is confusing
- create issue and discuss this further
- at least migrate api buildout setup to mxdev
- Make post on community to point to monorepo change and developing for volto core documentation.
- Developer documentation is buried: Develop Volto core – Frontend – Contributing to Volto — Plone Documentation v6.0
- Types unification (Unify Types under @plone/types by sneridagh · Pull Request #5493 · plone/volto · GitHub)
- Conditional variations support (Add conditional variations support by sneridagh · Pull Request #5424 · plone/volto · GitHub)
- Fred: I’m also on the marketing team. MT is now doing the low hanging fruit when it comes to marketing plone on plone.org: events, releases, community. We have a basic product marketing page but generic. I’d like to get more feedback from Volto team on how we can better market Volto+Plone, not only features but also market the Developer experience better
- path prefix PR in core volto:
- is a bigger PR, current PR needs to be rebased. Victor would like good cypress testing for it, also for regression checking
- When PR is updated lets discuss it at the next Volto Team meeting