-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Harmonize the NeXus web pages #1472
Comments
The landing (home) page is sourced from another repository at this time. It
is republished automatically when changes are pushed to that repo. Meeting
updates and the like.
These updates are not documentation of the NeXus standard. I believe it
would cause confusion for these pages to be combined with the manual. The
two repositories have separate purposes.
…On Fri, Sep 27, 2024, 3:26 AM Ray Osborn ***@***.***> wrote:
As recently discussed at a Telco, I think it would improve a newcomer's
impression of the NeXus format if we harmonized the look and feel of the
NeXus website. My suggestion is that the current landing pages, including
the NIAC page, be absorbed into the Sphinx-generated manual. Since the
Sphinx pages are (I believe) automatically generated when Github commits
are approved, this would (I hope) actually simplify the mechanism for
updating the current landing pages. We would need to @prjemian
<https://github.com/prjemian> to confirm these beliefs and hopes.
—
Reply to this email directly, view it on GitHub
<#1472>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARMUMAQYISS4K2DEGOG4XDZYUJCFAVCNFSM6AAAAABO6U7LH6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2TEMZSHE2TGMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Could change the theme of the home page to match the manual. This is a cosmetic change that might satisfy the intent of the issue. Then, the home page content and the manual would have the same look and feel without blending the purposes. |
Consistent look and feel includes consistent logos, too. |
A PR would need to change the build tools. It is possible to do this using a GitHub Actions workflow. The manual is published from such a workflow. |
Currently, the text in the wiki which appear in our main website (www.nexusformat.org) is built using Jekyll. |
Discussed in the NIAC, it make sense to harmonize the look and feel between the main website and the Sphinx docs. @RussBerg will implement an initial pass which moves the main website to the look and feel of the Sphinx docs, assisted by @PeterC-DLS and @sanbrock. That PR will close this issue. A separate set of work will be done by @RussBerg and others to update our theme. |
As recently discussed at a Telco, I think it would improve a newcomer's impression of the NeXus format if we harmonized the look and feel of the NeXus website. My suggestion is that the current landing pages, including the NIAC page, be absorbed into the Sphinx-generated manual. Since the Sphinx pages are (I believe) automatically generated when Github commits are approved, this would (I hope) actually simplify the mechanism for updating the current landing pages. We would need to @prjemian to confirm these beliefs and hopes.
The text was updated successfully, but these errors were encountered: