Skip to content
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

"Download" page #34

Open
OndroMih opened this issue Jul 13, 2016 · 4 comments
Open

"Download" page #34

OndroMih opened this issue Jul 13, 2016 · 4 comments
Labels

Comments

@OndroMih
Copy link
Contributor

New download page in bottom menu under Java EE:

  • link to Java EE SDK
  • link to download page of Glassfish
  • links to download pages of certified servers
    • links to other projects with downloadables (Forge)
@mikecroft
Copy link

I was going to get started on making a first draft of this page. Looking over the repo it looks like I can just create a ../pages/download.adoc and ../pages/download.adoc.yaml?

As for the content, I was going to link to GlassFish at the top as the RI then make a table of available app servers with a bit of detail about each, e.g. vendor, open source/closed source, versions, supported/unsupported etc.

Adding downloads to other projects might be a bit out of scope (bit too much overlap with tools?) though there is the argument for keeping all downloads to this page, and reserving other pages for only descriptions. We'll see how it looks.

@mikecroft
Copy link

Could you assign this issue to me? I don't know if non-collaborators can be assigned, so add me if you need to

@OndroMih
Copy link
Contributor Author

You are right, other downloadables should go into "tools" section, unless somewhat special and essential. The download section is meant to contain essential downloadables that most people need to get started. So far, having JavaEE SDK, GlassFish and info about other runtimes should be enough. Later, I would also put here some getting started artefacts, like project templates.

@OndroMih
Copy link
Contributor Author

OndroMih commented Jul 29, 2016

It's not possible to assign the issue to you, you have to get write access to the repo I guess. @tveronezi, @jcpevangelists/admins ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants