Community Forums › Forums › Archived Forums › General Discussion › Is Foodie Pro theme AMP compatible?
- This topic has 4 replies, 3 voices, and was last updated 3 years, 10 months ago by Victor Font.
May 20, 2019 at 10:19 pm #491257EmillieMember
I'm just learning about AMP now and found this post that suggests child-themes may not be AMP-compatible until a new Genesis framework is released. Is the 2/25/19 release of Foodie Pro AMP-compatible, or does someone know when this is planned?May 21, 2019 at 5:21 am #491262Victor FontModerator
AMP compatibility is planned for the Genesis 3.0 release tentatively scheduled for June. See this: https://www.youtube.com/watch?v=4mavA1xow1M&feature=youtu.be&t=1634
Keep in mind that Foodie Pro is not a Studio Press theme and there may be additional steps required by the 3rd-party developer to support AMP.
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?May 21, 2019 at 7:17 am #491268EmillieMember
Darn, I thought Foodie Pro was a studio press theme since I purchased it through studio press. Now I see that it is a third party theme, so hopefully it will work when June rolls around. Thanks!July 9, 2019 at 7:31 am #492224feastdesigncoMember
Feast is taking an active stance AGAINST AMP and we have no plans to support it. As a professional web developer with a more thorough understanding of the consequences of what AMP's goal is, it's our professional responsibility to push against it.
We design themes for food blogs. Food blogs do not benefit from news-based carousel rich snippets. Therefore, we have no reason to support AMP.
That's not to say we'll break anything Genesis implements, but we will not automatically enable support for it. Publishers wishing to use AMP will likely have to hire a developer to implement support for it manually.
But unless you're a news site competing for news-based rich snippet carousels, there's no reason your site needs AMP.
We've made our stance clear with Studiopress when this was being discussed. Discussion below:
I just wanted to drop in an objection to anything AMP related being supported or integrated into Genesis.
AMP is a publisher-hostile system whereby Google is attempting to claim its search results for itself, by loading other peoples' content via it's own system.
It's ostensibly a user-first implementation, but their push for simpler/faster pages guidelines via pagespeed insights should be improved to a point sufficient to allow webmasters and developers to compete on level footing: https://developers.google.com/speed/pagespeed/insights/
I'm not sure where the line between crackpot conspiracy and diligence lies, but I'm fully against efforts by large corporations to create a more closed-in ecosystem. They have the timelines, resources and skill to move inch-by-inch while the public's attention moves onto other things, and if left unchecked, will act in their own selfish self-interest.
Genesis, at its core, is a tool to assist publishers and small business. Some big, mostly small. The vast majority of these people aren't aware that AMP is a long-term death sentence that will erode their independence, and increase reliance on Google. As such, it's the responsibility of professionals to understand the motivations at play, and make appropriate recommendations against them.
This is similar to how we rely on food scientists to protect us from things like Glyphosate. Nobody here understands the long-term implications and damage pesticides are doing to our bodies - most scientists don't - and by allowing large corporations to "regulate" themselves, we're now seeing the damage it can do.
Its applicability remains primarily for news-results, which is a niche market. It's worthless to (best guess?) 99% of Genesis sites, which don't compete in amp-carousel news cycles.
That's to say nothing of Google's reputation for dropping projects (https://killedbygoogle.com/), ultimately wasting everybody's (developers and users) time who spent implementing and accommodating the projects.
The two possible endings for AMP are:
1) eroding the open web
2) being sent to the graveyard, ultimately wasting time that could have been spent on more productive tasks
Either of these are terrible.
AMP support should remain plugin-driven, or ideally, actively pushed against.
Linked to the discussions, because I find the input of many people provides a broader perspective. Original article can be found at the top of the discussions.
July 9, 2019 at 1:37 pm #492235Victor FontModerator
Genesis AMP support is only activated if the official AMP plugin is installed.
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?
- The forum ‘General Discussion’ is closed to new topics and replies.