Add a page to list all spec's released javadoc/pdf/html

[Emily-Jiang]

Some feedback regarding the difficulty to find spec/javadocs for each spec in MicroProfile.

Most of the relevant docs are under here

[Emily-Jiang]

We need to have a page with a table to list all specs. For each spec, we need to list all versions. For each version, we need to list the pdf/html/javadocs.

[jclingan]

I'd like to simplify this a bit for reader usability. The page should only have the most current version of each spec on the page, and then a link to the github releases page for each spec. So, image this is some crazy nice table format Ryan comes up with:

Metrics (PDF | HTML | Javadoc). Previous releases.
Config (PDF | HTML | Javadoc). Previous Releases.
OpenAPI (PDF | HTML | Javadoc). Previous Releases.
Fault Tolerance (PDF | HTML | Javadoc). Previous Releases.

Hopefully this can be done in an automated manner so it is always up to date. I was thinking the table may be included on the resources page, but I suspect it may become unwieldy over time as the number of specs grow.

[OndroMih]

I would like to merge this activity with the idea of redesigning the Projects page (https://microprofile.io/projects/) we discussed in the Architecture Board meeting on August 13 (minutes here: https://docs.google.com/document/d/1uAKRymdAL5Wj1KADzrYKZzSnAFsq74lBfj8lxKQnI6I/edit#).

We could start by improving the Jenkins release job by producing some output that could be copy&pasted where needed, or to store some machine-readable info about the new release that could be picked up by a page at microprofile.io.

My original email in the forum here: https://groups.google.com/d/msg/microprofile/7PoUAsS1ebk/YbkrOFeDAwAJ

[OndroMih]

I propose these enhancements:

• the current Jenkins job will generate a text file that can be copy&pasted to the new github release to add all the details for released artifacts semi-automatically
• for each final release, the current Jenkins job will update a file stored in the Eclipse Downloads area to contain machine-readable information about the latest release (version, PDF, HTML, Javadoc, release info in Github)

Meanwhile, we can decide where and how to display the machine-readable information, which is produced by Jenkins, on the microprofile.io page.

[Emily-Jiang]

We should minor https://jakarta.ee/specifications/
I think that is a lot better than our projects page. I plan to chair a call to discuss this with Ryan to have some design drawn. I will try to find a time and then make it public.

[Emily-Jiang]

There is a dup of this on marketing git repo microprofile/microprofile-marketing#225. Let's use this one for further discussion.