-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Move remaining pages to be responsive #2519
Comments
See Pull Request #2523 |
i have started making the blog and top menu responsive, Any ideas for handling the sidebar? |
@webofnithin Re: the blog page, I would suggest you paginate and put the blog menus beneath the main content area. But it would probably also be worth coordinating with us on the Slack Aso, the top menu should already be responsive if you match what was done on some of the other PRs (see #2564 as an example) |
See Pull Request #2583 - new responsive styles and markup for Showcase component (ember-users and sponsors) |
See Pull Request #2587 - responsive layout for logos page. |
See pull request #2595 - responsive blog with pagination |
See pull request #2683 - responsive Community page |
See pull request #2684 - responsive team page |
See #2690 for the meetups page. |
If anyone has time to work on things here, we're definitely getting to the final stretch. API docs have been responsified but could use some love to make them nicer to use for us all ... |
See #2853 for the tomsters / mascots page |
https://emberjs.com/guidelines/ Also needs to be updated |
@ericorruption keep'em coming :) |
Hi everyone, I'm Judith and I will like to contribute to open source project right here but need a mentor so as to guide me. Thanks |
Hi @devifeoma , I would be glad to help. Just sent you an email. |
Hey, I'm Akash and I will like to contribute to this open source project and this would be my first contribution so I need someone to guide me. |
Thanks to #2477 the main site, header and footer are all now capable of being responsive. However, most of the pages weren't originally designed with that in mind and need to be have some styling re-worked in order to handle that. This issue tracks which pages need to be "responsified" and orders them roughly by ease / usefulness. Good PRs to resolve issues will show screenshots of how things look on your end so we can point out any obvious issues without doing a build on our end:
The text was updated successfully, but these errors were encountered: