Skip to content

improvements #356

@FrankHossfeld

Description

@FrankHossfeld

The gwt-site should reflect the current state of the GWT development and be up-to-date.

at the moment, it misses:

  • quick finding links: how to get in contact, where developer talk, etc.
  • a roadmap (GWT SDK) that gives the user an idea what to expect with the upcoming releases (linking to GitHub Milestones)
  • a news page (GWT SDK) with news about releases (GWT SDK & GWT modules), request for help, etc.
  • information about GWT modules (editor, widget, regexp, etc.)
  • information about the eco-system
    • state of the art dependencies, frameworks, etc.
    • archetype creator

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:

  • GWT SDK news page
  • GWT SDK Roadmap
  • more recent articles and no dead links
  • Up to date docs, that covers best practices (which also means: use stuff from outside the GWT SDK)
  • Information about the eco-system
    • list of maintained dependencies: frameworks, plugins, etc. (just name, short description and link)
    • important news from the eco system (nice to have)

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions