-
Notifications
You must be signed in to change notification settings - Fork 0
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
Instruction to pass google mobile friendly test and make the theme responsive #1
Comments
I'm have extended this a bit for a dynamic width depending on screen size also for desktop - this gives a bit more of an example what is possible with CSS Inserts:
Then goto ATO Next-Previous Navigation and set: Last but not least - Atahualpa footer on posts/pages is not mobile friendly. I solved it by changing Footer Homepage and Footer Multi Post to: (note I took out category - you could alternatively try to get in some decent spacing - I did not manage that however). |
You will also need a mobile responsive menu plugin - as the normal atahulpa menu is not usable if you use pagination. |
This is the most important help topic in the forum - and should the bytesforall.com forum go down - here is a backup:
http://forum.bytesforall.com/showthread.php?t=23158
Originally posted by Juggledad.
To get your Atahualpa site pass the Google 'Mobile-Friendly Test' do the following. This will make your site mobile friendly. If you don't pass the test after doing this - disable ALL your plugins and test again to see if a plugin is causing the issue.
go to ATO->Style & configure LAYOUT->Layout WIDTH and type (FLUID or FIXED) and set it to a percentage (as opposed to a 'fixed' width) then set the 'Layout MIN width' option to 320 (iPhone 4 size) or remove it altogether.
add the following to ATO->Add HTML/CSS Inserts->HTML Inserts: Header
Note: in steps 4 and 5 you can adjust the number (767) to suit your choice.
Thanks to Flynn, sawyerjw, yukoner, kayphoonstar and extremecarver for their contributions.
The text was updated successfully, but these errors were encountered: