search

eclipse-openj9 / openj9-website

openj9-website
24 stars 28 forks source link

Update README to reflect publishing changes #342

Closed pshipton closed 1 year ago

pshipton commented 1 year ago

As per https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1849#note_1082668 we can no longer use staging.eclipse.org, the website staging is published via GitHub Pages instead.

The links at https://eclipse-openj9.github.io/openj9-website-publish/ don't work ATM, since they are based from openj9 rather than openj9-website-publish. i.e. the News link is to https://eclipse-openj9.github.io/openj9/news but should be to https://eclipse-openj9.github.io/openj9-website-publish/news. Somehow we handle this for https://eclipse-openj9.github.io/openj9-docs/ vs https://www.eclipse.org/openj9/docs/ so I assume it can be fixed in a future website update.

pshipton commented 1 year ago

@Sreekala-Gopakumar fyi

doveye commented 1 year ago

Most of the links at https://eclipse-openj9.github.io/openj9-docs/ work because they are relative and low-level enough that it doesn't matter where the files are (eg "New to OpenJ9?" in the toc: <a href="../openj9_newuser/" class="md-nav__link">). There are some links that don't work in the same way that the new website staging ones don't, especially in the footer (eg "New to OpenJ9?" in the bottom left corner: <a href="/openj9/docs/openj9_newuser/" >New to OpenJ9?</a>).

So I guess the solution for the staged website is to make the links relative and low-level, if that's possible.