In this episode of Post Status Excerpt, David Bisset and Cory Miller talk about some upcoming enhancements to the Post Status job board and Cory’s experience with the current #gig channel in Post Status Slack.
Also covered: David talks about a Brian Krogsgard tweet rant on WordPress settings screens. David asks Cory if he thinks some old “wrinkles” in WordPress might eventually be harmful.
Every week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what’s new in WordPress in a flash.⚡
🔗 Mentioned in the show
- David Bisset (Twitter)
- Cory Miller (Twitter)
- “Setting Screen” Conversation In Post Status Slack (Member Access Required)
- Brian Krogsgard’s tweet and one from David Bisset.
- Is the WordPress Comment System Still Relevant?
Sponsor: Wordfence
Wordfence protects over 4 million WordPress websites with a world-class firewall and malware scanner. It is the most popular security plugin available, protecting WordPress sites from spam, malware, and other threats through the real-time threat defense feed.
Regarding this, please refer to the newly-updated Core Web Vitals & Page Experience FAQs on Google Search Console Help. There is a large section all about AMP and Google’s commitment to the technology. I know personally from my ongoing work on the AMP plugin for WordPress, that our team is full steam ahead on our shared mission to make good page experiences accessible to WordPress site owners. As I see it, AMP democratizes performance in the same way that WordPress democratizes publishing. With Core Web Vitals (CWV), there are now metrics that can be used to measure page experience (PX) regardless of technology. If you can achieve good PX metrics without AMP, then great. But for the majority of WordPress site owners, performance is hard. We are building up the AMP plugin to provide guide rails to achieve good performance and maintain it.
Thanks Weston. We will surely follow up and read those and perhaps feature them in a future newsletter.
I don’t think AMP is going away and that wasn’t the intent in mentioning the links in the newsletter or the podcast. But (in my opinion and from my feedback of quite a few using the AMP plugin) many people were using AMP for speed… for Google rankings. The fact that Core Vitals “whether implemented using AMP or any other web technology” means that AMP for some might be seen in a different light – especially if (like Ethan, as you could read in his post) didn’t prefer it in the first place.
This doesn’t mean AMP or plugins that help with AMP are less useful overall, but Google’s statement there I think is interesting at least.
Thanks for the comment, and the team behind the AMP plugin is doing a fantastic job.
Yes, although it’s important to note that AMP has never been a ranking signal in Search. Speed is a ranking signal. So if you can achieve high performance without AMP, more power to you! However, our understanding of the web development ecosystem is that 1% of developers have the resources to invest in knowing all the best practices to make a highly-performant website with a great page experience. AMP is not necessarily for that demographic, but rather for the 99% who don’t have time for that.
It’s also important to note that AMP itself is being made more flexible. AMP’s highly performant web components are being evolved to work outside of valid AMP pages (which again are just a constrained set of HTML/CSS/JS). If you can’t constrain your webpages to the specification for valid AMP, such as if you need to use custom JS or some unsupported advertising unit, you’ll still be able to use AMP components. This initiative has been called “Bento AMP” and it recently entered developer preview. We’ll be fully supporting the use of such Bento AMP web components in the WordPress plugin later this year.
Our goal is for you to be able to use Bento AMP web components to build themes and plugins, with packages installable from npm and distributed with the theme/plugin. Then if you want to also serve pages as valid AMP, we’ll make it seamless for you to do so. The key thing here is that you’ll not have to worry about creating two versions of interactive site features, like a non-AMP mobile nav menu which uses jQuery and an AMP version that uses
amp-sidebar: you’d be able to the same web component in both the AMP and non-AMP versions alike.Thanks for engaging and happy to discuss further!
Thanks Weston. Who knows, we might be talking more about this in the future. AMP has certainly different layers to discuss – like an onion. Thanks for sharing your particular thoughts and keep up the good work.