AMP Website Conversion Complete – Look at the New Design
Yes, my conversion from a standard WordPress site to an AMP website is complete. It took me more than two days, but only a couple of extra hours. As I expected, I had to fiddle with certain things to get each page to display the way I wanted it to. In case you’re wondering, you’re looking at it.
The best part about all of this is that I get to work with a standard WordPress website on my local computer while you get to see only the AMP website online. I only have to look at a completed page at the online website once when I first publish it. After that, I never have to look at it again (unless I want to).
The WordPress Plugins I used for the AMP Website
I could get into every plugin I use, but I won’t. I’m only concerned with the plugins I specifically used for this project, even if I was already using one or two.
I won’t link to plugins like some people do because the WordPress plugin interface is pretty good. It doesn’t do any good to send a non-WordPress user somewhere else needlessly.
I turned this website into a completely static website more than four months ago. One or more of these plugins helped me to turn it into an AMP website. Here’s the list, alphabetically:
- Add Any Extension to Pages
- AMP (the official WordPress plugin)
- AMP for WP – Accelerated Mobile Pages
- Code Snippets
- Contextual Related Posts
- Yoast SEO
I didn’t need the “Glue for Yoast SEO & AMP” plugin because the AMP for WP plugin does the same things. Well, at least the things I need.
A Completely Static AMP Website
One of the advantages of having a background in programming, especially in PHP, is that allows me to do things like this. For the average Joe Blogger, digging into PHP is out of the question.
I have Linux Mint set up on my laptop and I have Nginx (the web server), PHP and MySQL (the database server) set up on it. I do many of my WordPress-related tasks from a sudo su terminal command line.
I use a “.local” domain name on the web server. A PHP script loads and saves every page as a file ending in “.html”. In the process, I have it change some of the things I need to change, like the domain name everywhere it shows up in the text. Those things are nearly impossible to do from within WordPress.
Although everything looks good with my AMP website at this point, it isn’t even close to being perfect. I had to forsake a contact form and a comment area. I’m sure I’ll eventually do something about both of those things, but I’m limited by the state of software and my knowledge of WordPress internals. AMP is a relatively new thing (less than two years old) and it’s slowly getting to the point where it works well enough for me to play with it.
AMP is a Google product. They’ve been known to shutter useful services in the past. If AMP doesn’t meet their expectations, it could easily end up on a chopping block in just a few years. This is why I’m glad I created the static website software first. I have something to fall back to if Google gets antsy.