The intention is that AMP plugin will only handle AMP specifically. SEO would be the responsibility of a plugin like Yoast. Now with 1.0 the plugin is intended to be used with your existing themes and plugins, so it can just focus on issues related to AMP.
Well said. Thanks for the wonderful app. Hopefully I will get use to it, as time goes on. Please if there is a possibility to add site menu on the configuration. That will be amazing.
@jameseze Site nav menu is available with 1.0. If you switch from Classic mode to Paired (e.g. http://make.xwp.co/?amp) or Native (e.g. http://weston.ruter.net) then your active theme’s templates and stylesheets are also used in AMP responses. It isn’t a turn-key solution, especially if you’re using a theme that heavily relies on JS, but it is a good starting point.
I use Hueman theme, I tried both as you said, but it wasn’t the same as shown above. Do I need to add some more codes ?
If it appears that the styles are broken then it is likely that the theme or a plugin has too much CSS for AMP, or the admin bar from WordPress is causing too many styles to be added to the page. You can disable the admin bar for AMP pages to prevent this from happening, and that will help bring the limit down. I did a quick check of Hueman on a vanilla install and it showed the template looked fine in AMP.
You can open a new support topic for specific issues.
jameseze.
