Closed benrfairless closed 9 years ago
Just a note here that https://www.whatdotheyknow.com/ is using responsive design techniques to provide a better experience on small screens.
Assigned to @equivalentideas to get our theme working with Alaveteli's new responsive styling without changing the design.
Ok, so flicking RESPONSIVE_STYLING:
to true
in general.yml , makes the layout flexible, but it stops loading custom.css so it breaks some of the layout and all the type and colour styles:
I'm going to look at how custom.css gets loaded and make that stick around for starters.
As a test I added *= require custom
to responsive/application.css
to see what happens when you combine our custom css with the responsive css:
Quite a bit of it is messed up.
Next step is to work out how to add the custom css through our theme rather than changing Alavateli.
Following the instructions at http://alaveteli.org/docs/customising/themes/#changing-other-styling I replaced the theme responsive/custom.scss
.
Major difference areas that need fixing are:
Another component to this is that the header and footer are different html partials than the ones currently used in our theme.
The immediate standout is the search bar that comes before the logo and header nav in the static partials, is at the bottom of the nav menu in the responsive partials.
After testing this out on my phone. These need to be tested on staging, something weird happening here that I can't replicate using local emulator:
update: after testing this on staging the date picker and image rendering is fine.
~~* Date picker is not activated on iPhone5 *Fix image rendering problems on iPhone 5:~~
The signup form needs to flick back to horizontal layout on wider screens:
Current responsive:
Right To Know:
Much closer now:
Current responsive:
Right To Know:
We're deploying this to staging and I'm going to break it out into individual issues.
Closed by merging https://github.com/openaustralia/righttoknow/issues/452
Over 40% of our users access RTK via mobile devices. We should make this experience better for them by changing the CSS to be more mobile friendly.