any guidance to do that?
It’s explained in the docs How to contribute to Vaadin
1 Like
If you are new to Vaadin, then one very impactful way of contributing is to share you experience from getting started with using Vaadin. What where the things that made it easy for you to learn how to use? What struggles did you have? What helped you overcome those challenges?
This is the one thing that we insiders simply cannot do even if we tried because we already know too much.
From our experience about Vaadin “struggles” with new devs
- difference between production and development mode and why it matters (for the framework)
- should a bundle be generated or not, and when
- getting hotswapagent to work (though the vaadin plugin revival is doing a great job!)
- the myriad of config options in the maven plugin
- understanding and debugging session serializability
- given a view class, what is stored in the session and what not (a session “lens” would be great)
- creating page elements in ctor vs onAttach vs setParameter
2 Likes
Forgot to mention (but maybe i’m taking this a bit too far, apologies):
- Vaadin is promoted as a Java-only framework and I guess that’s what most people chose it for, so anything Hilla should be an explicit opt-in by including a dependency and/or configuration etc. Basically the opposite of this blog Streamlined Vaadin Flow setup for V24.4 | Vaadin i.e. “How to add Hilla to your application”.
1 Like