rustfoundation / foundation.rust-lang.org Goto Github PK

View Code? Open in Web Editor NEW

25.0 9.0 29.0 113.97 MB

website for Rust Foundation

Home Page: https://foundation.rust-lang.org/

License: Apache License 2.0

JavaScript 4.18% CSS 12.43% Nunjucks 83.39%

foundation.rust-lang.org's Introduction

foundation.rust-lang.org

The website for the Rust Foundation

Running the site locally

The site uses Eleventy. https://www.11ty.dev/docs/usage/

From the root of the website GitHub repo...

npm install
npx @11ty/eleventy --serve

foundation.rust-lang.org's People

Contributors

Stargazers

Watchers

foundation.rust-lang.org's Issues

viewport makes the site hard to read on mobile

Either it shows a bunch of blank space:

Or it's far too zoomed in:

I am getting a secure connection failed error (SEC_ERROR_OCSP_SERVER_ERROR) in Firefox 101.0a1 (2022-04-12) (64-bit) when I have HTTPS-Only Mode enabled. Adding a temporary exception for https://foundation.rust-lang.org stops the error.

README

sponsorship content

Very thin font

The font used for some of the subheadings like "A new approach to sustaining and growing a large, participatory, open source ecosystem" is extremely thin, making it hard to read.

Screenshot in case this is a platform specific issue (Firefox on Ubuntu 20.04):

RSS feeds are empty

https://foundation.rust-lang.org/feed/feed.json and https://foundation.rust-lang.org/feed/feed.xml both contain zero list items. I would expect them to contain the foundation's news items as both pages are linked in <head> of https://foundation.rust-lang.org/news/

about content

events data entry

non critical RCE vuln in pug

doesn't actually affect our security but we should fix to make the alert go away

ag_dubs@Ashleys-MBP foundation.rust-lang.org % npm audit
 
                      === npm audit security report ===

┌──────────────────────────────────────────────────────────────────────────────┐
│                                Manual Review                                 │
│            Some vulnerabilities require your attention to resolve            │
│                                                                              │
│         Visit https://go.npm.me/audit-guide for additional guidance          │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High          │ Remote Code Execution                                        │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ pug                                                          │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=3.0.1                                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ @11ty/eleventy [dev]                                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ @11ty/eleventy > pug                                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/1643                            │
└───────────────┴──────────────────────────────────────────────────────────────┘
found 1 high severity vulnerability in 508 scanned packages

Images don't have width constraints and x-overflow on mobile

On https://foundation.rust-lang.org/news/2022-04-11-member-spotlight-tangram-vision/, if you activate mobile view on devtools, you'll get this:

This is because img tags don't have a width property set in CSS. I briefly tested setting width: 100% and it seemed to fix it.

remove travis

contact content

Staff entry for Jan David

Jan David needs a Staff entry on the About page -- and don't forget the crab! -- but in the meantime the blog announcement (#261) is holding his place due to the "staff" tag.

LICENSES

fix meta tags

Blog post timestamp

As pointed out on reddit, the timestamp on the bottom of the blog post is too precise:

Mon Feb 08 2021 00:00:00 GMT+0000 (Coordinated Universal Time)

It should probably only include the date, not the time and time zone.

Also, <h2> is the wrong HTML element for this.

404 content

favicon

Footer Link Color change makes link text unreadable

Hi! Just wanted to point out that when you hover over a footer link on Desktop, the color change makes the text unreadable wrt the background - screenshot attached below. I'm currently using Firefox 87.0 on Ubuntu.

Spacing

Spacing is all over the place. The header has a weird padding-bottom. Some things are centered, some are left-aligned, but the left-aligned sections have different paddings on the left. Spacing between sections is also rather arbitrary. The "Learn more about how we're different" and "Get in touch" buttons have slightly different heights. The aws logo looks much larger than the other ones. On the "members" page, the mozilla logo is wrapped on a new line on my screen, making it stand out. On mobile, the spacing is too large, some text is too large, some is too small or has a bad line height.

I'd be willing to help with these problems, if that's okay.

Founding Platinum vs. Platinum members

On the members page, I think it's misleading to list "Founding Platinum" and "Platinum" members separately, as if they have some ongoing distinction in the foundation. Maybe instead we could list them together, but with some sort of "founding" badge?

Squashed images on mobile

This is how it looks on iOS Chrome/Firefox

footer

Is "docs.rs is managed by the members of the Core team" accurate?

In https://github.com/rust-lang/foundation.rust-lang.org/blob/c7ccdb7db0efc81c7706457400f56396dd3917a0/policies/privacy-policy.md#docsrs the website says

Docs.rs is managed by the members of the Core team and the Dev Tools docs.rs sub-team.

Is that accurate? I think some members of the infra team have access to the production server, but I don't think all of the core team does, and neither team is involved in day-to-day operations.

The post "Announcing three new ..." is on the Board

One of these things is not like the others...

Optimise images

We could do with agreeing a standard for images in headshot and ferris. Currently there is a mix of JPG / JPEG / PNG, different dimensions, wildly varying file sizes, etc. The load time for the about page and the mouseover images is slower than I'd like.

The images are displayed at width: 15em; height: 15em; so there's no need for them to be particularly large. 300 x 300?