OpenJS Best Practices: Website Updates

[kj-powell]

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!

[avivkeller]

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?

The OpenJS Foundation | Terms of Use | Privacy Policy | Bylaws | Code of Conduct | Trademark Policy | Trademark List | Cookie Policy

[MattIPv4]

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]

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]

Eslint is also internationalized. I will start the work presently.

[MattIPv4]

Yah, it works like that, but that is a huge footer to have, presumably, above the fold on the homepage?

[ovflowd]

@bmuenzenmeyer this needs some tuning:

Centering, colors, links alignment, etc/

[avivkeller]

Could we get away with an element with a title=[the really long text], and the added buttons?