We need a favicon for this site:

GET http://127.0.0.1:1111/favicon.ico                           [HTTP/1.1 404 Not Found 0ms]

Current Behavior

When browsing the site from a mobile device, the top menu gets broken, especially for smaller devices.

For instance, some menu items are split ("Project Standards" is displayed on 2 lines):

Expected Behavior

The menu items should be displayed properly for all resolutions.

Possible Solution

A possible solution would be to use a flex layout and wrap the menu items on the next line if they don't fit.

Steps to Reproduce

1. Open the site from a device with a small resolution (e.g.: 354x854), or use the browser inspector.

Context

Your Environment

Last commit:
  e7aa3c3 Adds favicon (#8)  (HEAD -> main, origin/main)
Browser(s):
  Mozilla Firefox 96.0.2
  Google Chrome 97.0.4692.99 
System Version: macOS 12.1 (21C52)

Current Behavior

The hero is broken for mobile. The text does not fit on the screen and the big logo disappears.

Expected Behavior

The text should be readable for any resolution. Maybe the logo could be placed above the text, at a smaller size.

Possible Solution

Use a flex layout to render the elements of the hero properly given any screen resolution.

Steps to Reproduce

1. Open the site from a device with a small resolution (e.g.: 354x854), or use the browser inspector.

Context

Your Environment

Last commit:
  e7aa3c3 Adds favicon (#8)  (HEAD -> main, origin/main)
Browser(s):
  Mozilla Firefox 96.0.2
  Google Chrome 97.0.4692.99 
System Version: macOS 12.1 (21C52)

Feature request

Current Behavior

We currently use the BNA logos.

Expected Behavior

Now that we are starting to have our own identity, we should use the BNA logos.

Feature request

Current Behavior

The guideline page does not provide any guidance regarding web development.

Expected Behavior

We already agreed internally to use the following technologies:

• npm
• node 18+
• react
• next.js
• tailwind css

So this should be officially documented.

If possible we should go one level further by also documenting:

• Which testing tools do we recommend?
• Which tailwind component collections we recommend/reject
• Do we recommend a specific project structure?
• Can we provide a code snippet that would help bootstrapping a new project?
• etc.

Current Behavior

• The measure link is missing on the main page.
• The Docs link in the navbar is not pointing to anything.

Expected Behavior

• The measure link should point to the github repository: https://github.com/PeopleForBikes/measure
• The docs link should be removed since there is no plan to have a documentation site fornow