Google's AMP Project - January 2016

Hilarious. Publishers need to rely on other companies to serve fast web pages on mobile. That's because publishers create some of the worst designed and most bloated websites on the internet.

Here's how to speed up an article page:

• use no javascript
• cache the page

I'll have to see if AMP speeds up an article page that is produced by my Grebe, Scaup, and Veery web publishing apps.

• http://toledowinter.com - built with Grebe
• http://babyutoledo.com - built with Grebe
• http://crochet.soupmode.com - built with Scaup
• http://veeryclientperl.soupmode.com - built with Veery

I use memcached to cache article pages and page one of the home page stream. That means that a user will interact only with Nginx and memcached.

If the page is not cached, or the user hits page 2 or higher of the home page stream, or the user conducts a search, then my apps pull the content from a database, such as MySQL or CouchDB.

If it's an article page that is not cached, then my code knows that and places the article into cache. A refresh would get the article from memcached.

Veery and maybe Scaup will cache page one of the home page stream if it was not cached. For Grebe, page one of the home page stream gets cached when an article page is created or updated.

When I'm logged into one of my web publishing apps, then each article page is dynamically created by being retrieved from the database.

And when I'm logged in, I access JavaScript only when I use the browser-based JavaScript editor, which is what I'm using right now to create this post in my Junco app.

Junco does not cache content.

I love, actually thoroughly enjoy writing on the web by using this JavaScript editor that I "created" by downloading someone else's code and greatly modifying it.

The editor that I downloaded was a Textile live preview editor