Individual component specification pages (see Jakarta specification pages for reference)

[rstjames]

iterate on https://microprofile.io/microprofile-config/ and move other specs forward.

[rstjames]

@Emily-Jiang what is the next step to move this forward. Contact spec leads and have them create a page as you did?

From my side:

• I think we should restructure the URL so that it is https://microprofile.io/**components**/microprofile-config/ ??? Any suggestions on what is the nest title for geographical domain? .io/????????????/microprofile-config/

[Emily-Jiang]

I created this page from my local fork as it nees the admin access right to enable settings. I think we just need a couple of people to do it for all of the specs. All specs just need to create the content and the admin enables the github pages. I had a quick look but I could not find a way to change the url as yet. I will take a further look later.

[dblevins]

Page for each specification version (#145, #154)

The goal if this task is to create in Wordpress a page (URL) per specification version. That would mean we no longer need to link to these Github pages from Microprofile.io:

• https://github.com/eclipse/microprofile/releases/tag/6.0

We would have links on the Microprofile.io site such as:

• https://microprofile.io/specifications/microprofile/6.0
• https://microprofile.io/specifications/microprofile/5.0
• https://microprofile.io/specifications/config/3.0
• https://microprofile.io/specifications/config/2.0

The goal is to communicate to people:

• What has changed in the specification from the previous versions (high level)
• What are the requirements for the spec (java version, etc)
• What are the links to download spec PDF, HTML
• What are the compatible implementations for this spec version

All of the data for the first three bullet will get supplied via Plan Reviews and Release Reviews. The data for the last bullet will get supplied via the CCRs. If we keep the information more or less limited to the above, we should be able to keep them maintained — we only do reviews a handful of times a year and they follow a template.

The JCP as similar page per version and we recreated some form of it in Jakarta as well. For example, here are the links for Servlet 3.0 through Servlet 6.0:

• https://jcp.org/en/jsr/detail?id=315 (Servlet 3.0)
• https://jakarta.ee/specifications/servlet/4.0/
• https://jakarta.ee/specifications/servlet/5.0/
• https://jakarta.ee/specifications/servlet/6.0/

If we start incorporating teaching goals, code samples, etc into Wordpress then it becomes very high touch and with a bottleneck. We likely want that information somewhere else developers can update directly (markdown/asciidoc files in git) and do that via #65