Repository navigation
OpenJS Best Practices: Website Updates #8574
Description
Hello,
OpenJS recently performed an audit to ensure our hosted projects are following current best practices. I'm reaching out to request an update to Node's website footer to align with the latest OpenJS Foundation approved language.
These updates help ensure that copyright, trademark, and legal links are consistent and up-to-date across the ecosystem. You can find the official guidelines and various formats (Text, Markdown, and HTML) here: OpenJS Copyright Notices for Project Website Footers
If you have any questions, don't hesitate to reach out. Thanks for helping us stay aligned with these best practices!
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
avivkeller commentedon Jan 30, 2026
Hi @kj-powell!
The footer text you linked appears to contain a lot of text, and space is limited.
Do we need to include the entire text, or just the links shown below?
MattIPv4 commentedon Jan 30, 2026
Heh, that is a lot of text and links to fit into the footer. We might need to design assistance here, given I believe the current footer was designed by the foundation?
bmuenzenmeyer commentedon Jan 30, 2026
I am unconcerned - it just represents an expansion of our footer. AS IS on my mac it wraps anyway.
Pardon the terrible hack job I did in dev tools
Nearly identical experience to https://eslint.org/ for example
bmuenzenmeyer commentedon Jan 30, 2026
Eslint is also internationalized. I will start the work presently.
MattIPv4 commentedon Jan 30, 2026
Yah, it works like that, but that is a huge footer to have, presumably, above the fold on the homepage?
ovflowd commentedon Jan 30, 2026
@bmuenzenmeyer this needs some tuning:
Centering, colors, links alignment, etc/
avivkeller commentedon Jan 30, 2026
Could we get away with an element with a
title=[the really long text], and the added buttons?bmuenzenmeyer commentedon Jan 31, 2026
Of course it does. I was just illustrating that the footer height may evolve
bmuenzenmeyer commentedon Jan 31, 2026
I don't think we should get away with anything. Congruence when it comes to legal and compliance language across the organization is not negotiable. This also improves UX across Open JS sites, as visitors have congruent experiences should they come looking for this content.
kj-powell commentedon Feb 2, 2026
Hi all- I know it's a bit of a long footer. However, this language was decided by our Legal team and approved by the Board so unfortunately altering it is not a possibility.