Here are my ideas:
- graphql is still a thing and i'd like to see it in a Plone project, but we have a (semi) fully-powered REST api after years of hard work. I'm afraid that a graphql api should be too big for a gsoc project. Unless we build it on top of plone.restapi.
- CastleCMS integration could be a great idea.
- What about modernizing Plone javascript environment, widgets and all the mockup thing? I don't know the status of Johannes's PLIP, but if we move mockup outside Plone, we could refactor it with a more modern technology (react?). It should be great if we could reuse some parts of volto, but i think that it's not gonna be easy.
- Does webpack themes need some improvements?
- Tinymce is still the right tool? Can we use a Volto-like editor?
- Tiles: Volto started building its own tiles engine..could be a good idea choose one of them and use it in both environments?
- Are there other things that we can stole from side-projects (like Volto) or standardize them also in Plone?
- Towncrier is where we want to go with our packages? Does some students could convert core packages that are not yet converted?
- What about finishing plone.org addons list/search thing?
These are more than only 2 cents, but i don't care, it's a brainstorming 