-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improvements #356
Comments
#353 adds a roadmap page to the site. |
#348 adds a news page to gwt-site |
#350 adds a comment that IE9 is no longer supported |
#351 adds information about the GWT eco system |
#353 adds a roadmap and information about how to contribute and donate. |
#354 updates the getting started page |
Hello Frank, A prominent hint like the one from the Getting Started page could help: Thanks, |
The gwt-site should reflect the current state of the GWT development and be up-to-date.
at the moment, it misses:
Also, there are a lot of dead links which let the gwt-site look like it is unmaintained.
Next, all docs do not reflect the current idea/state of how to develop with GWT (Maven multi module, application frameworks, widgets, communication, etc.) Instead it shows how to code in 2014 (using the webAppCreator, single Maven Module. projects, using DevMode).
Expectations are:
Important:
Does 'best practice" means looking only into the SDK or also look into the eco system and choose the best solution from both worlds?
The text was updated successfully, but these errors were encountered: