I think the template used for the specification pages is derived from (or equal) to the template used for news articles. For news, the 'date' field is the publish date for a news item.
In our case, I suggest we use it as a 'created' or 'last updated' date. It is not the best solution, but we are not displaying the release date anywhere on the web site anyway.
Chris usually handles this kind of stuff, but the rest of the webdev team can help as well.
I only checked because you pointed out the work being done in
Steering committee. This morning, I saw the subsequent discussion
in the issue that Ivar created. Was the page not rendering
intentional, or was it just confusion about using that metadata
field?
I guess the answer to my other question about "how to remedy"
issues like this: File an issue against jakarta.ee repository
(https://github.com/jakartaee/jakarta.ee/issues). Ivar, is Chris
Guindon the person who would normally look into issues like this?
Generally, it might be more clear if the date for which the page
will be rendered is called something else -- Checking the actual
meta-field, it is 'date:' I think in other circles, "embargo date"
is used. Maybe this is just how Hugo works?
It certainly looked odd, especially since the PR had been
approved and draft had been removed -- yet there was nothing to
view. I wonder if some kind of "coming soon" status type page
would make sense where we want this, intentionally (i can
certainly see potential uses, I just was caught by surprise as
were the few people I asked about it as well.)
The "problem"
is that Andy had set the date for the Milestone to be 2020-06-05
(today).
So, it does look a little funny to have just the title until
then,
but it is now displaying just fine...
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
On Thu, Jun 4, 2020 at 12:46 AM Ed
Bratt
<ed.bratt@xxxxxxxxxx>
wrote: I was looking at the Milestone page
for
Jakarta EE Restful Web Services (3.0). But the merge doesn't
seem to have
worked correctly since the page is blank. The netlify
sample page
(earlier in the
PR process) shows what I would have expected, but the merged
page (from PR
155) isn't
rendering (at least
not for me). What, if anything is the remediation
for this? -- Ed PS FWIW, the CDI 3.0 milestone page
does
seem to be updated.