Jakarta.ee Internal Broken Links

[chrisguindon]

As part of our ongoing SEO effort for Jakarta.EE, we need to fix broken links on the site.

Please fix the broken link listed in this report for jakarta.ee/specifications:
https://docs.google.com/spreadsheets/d/19FplHkHeqWlG5mPmuwhLN8YF0Fnr7s8-g-lW8Ez_hS8/edit?usp=sharing

Please let me know if you have any questions.

[ivargrimstad]

I'll bring it up to the spec committee. My initial comments:

Row 2-36

These are links internally in the released artifacts (HTML versions of spec documents and Javadoc). These cannot be updated without releasing a new version of the specification, so I guess we will need to file issues to the affected spec projects and let them fix it for their next release.

Row 37 - 190

This is related to Chinese translations. I far as I recall, the spec committee has decided that translations for the specification pages would not be provided.

[kwsutter]

Where are we at with this Issue? As @ivargrimstad pointed out, the first 2-36 rows need to be converted to separate Issues against the individual components. Are we (spec committee) responsible for doing that, or will you be doing that @chrisguindon?

The Chinese translations are interesting. There is also this PR that is related to the Chinese translations. I don't recall what our decision was with regards to this effort.

[chrisguindon]

I am hopeful that this something that the spec committee & community can take on.

More than happy to help if there are technical hurdles with this request!

For example, I can look at adding the Netlify Check link plugin to better report on broken links for the specification repository: https://www.npmjs.com/package/netlify-plugin-checklinks

[chrisguindon]

Update:

I received an email by Excentric, the agency that created this report and they mentioned that this is still a problem.

They say that we need to fix broken internal links for Jakarta to help improve the site’s domain authority.

The WG invested resources in this effort, we hope that this can be addressed.

[lukasj]

issues in xml binding spec are covered in #346

issues in jsonp were fixed at source by jakartaee/jsonp-api#272, update for the web (jsonp service release) will follow covered by #343

[ivargrimstad]

I don't see any reason why we should keep this issue open any longer.