-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Not All Pages Are Full Responsive #1
Comments
Hi @onerinas! I'm excited to have your help in making the site fully responsive! |
I'll start with the about us page. |
@meg-gutshall #7 fixes about us page. Please have a look. |
That was my plan - get one page merged first and then pick up other pages 😎 |
@meg-gutshall Didn't work on navigation. Tried to replace the js code we have for mobile nav and use the code from bootstrap's example. That looked like more work so dropped that plan for now. Please have a look at #8 which adds responsiveness for Home & Donate pages. |
hi! would it make sense to have issues for each screen instead of one for all the responsiveness issues? I'm checking the different screens and some would need specific fixes that will only apply for that screen. Maybe it's easier to keep track? |
Hi @arielj! Thank you for the suggestion! This site has been in MVP status for about a year and we're slowly working on getting it into v1 state. I anticipate having more time in September to work on doing this. Were there any pages in particular that you saw needed attention? I welcome you to create new issues for anything you see on our website! I see that you work with Ernesto at Ombu and know the quality of code that comes out of there—I'm a Philly native myself—so I'd welcome any of your contributions, whether via issue creation or pull requests. |
@meg-gutshall thanks! I'll create some issues for different things I noticed, some are more general applying to all pages (like the mobile header that looks a bit weird) and some for specific pages |
We have a few pages that aren't fully responsive. We need to fix that for folks browsing on mobile devices.
Here are a few:
The text was updated successfully, but these errors were encountered: