“Mosaico is a JavaScript library (or maybe a single page application) supporting the editing of email templates.

The great thing is that Mosaico itself does not define what you can edit or what styles you can change: this is defined by the template.

This makes Mosaico very flexible.”

GitHub

IDE – Integrated development environment

1. Koder is still my main solution, with a bunch of features I do not want to miss on the go.
   • Syntax Highlighting
   • Code Autocomplete
   • Code Function list
   • Access and Manage your Dropbox, (S)FTP, webdav and local files easily
   • Built In Terminal (SSH Client)
   • Built In Snippet Manager
   • Tabbed editing
   • Extra Keyboard with Custom Key
   • iOS8 Document Picker Support to open/import/export other app files from/to Koder
   • Find and replace code
   • Previewer Browser with Firebug Support + View Source function
   • Editor theme with Custom Theme Editor
   • Extra Key / Additional Keys on Virtual Keyboard with open+close brackets keys
   • Screen
   • Lock, Manual and Auto Lock
   • Extracting Zip File on Local project
   • Sophisticated File Browser
   • iOS “Open In” support, from Koder to other app
   • vice versa
   • Change file/folder permission (CHMOD) on FTP/SFTP projects
   • Folder Synchronization between Local Project and FTP Project
   • Uploading files from desktop from browser or iTunes sharing
   • Expandable editing space
   • Bluetooth Keyboard Support
   • and many more
2. DraftCode PHP IDE is a complete PHP and webserver environment that works offline on your iPad or iPhone
3. Coda is powerful, and portable text editor.
   • A stunningly full
   • featured text editor
   • Works on both the iPhone or iPad
   • Editor features Clips, Find & Replace (with placeholder!), Context Keys, Super Loupe, much more.
   • Syntax highlighting for Apache, C, CSS, Diff, Go, Haml, HTML, INI, Java, JavaScript, LESS, Lua, Markdown, Perl, PHP, Python, Ruby, Sass, Scheme, Shell, SQL, Swift, XML and YAML
   • Local or Remote file management
   • Remote protocols include FTP, WebDAV, Amazon S3, DreamObjects, and FTP (Plain, TLS, SSL) support
   • Preview
   • Air Preview for use with Coda for Mac
   • Playgrounds
   • SSH Terminal
   • Much more!
4. Textastic is an advanced code editor for iPad with support for syntax highlighting, (S)FTP and Dropbox.

FTP

1. FTPOnTheGo – A desktop class, award winning FTP client
2. iTransfer
3. FTP Client Pro

SSH Terminal

1. iTerminal – SSH Telnet Client
2. SSH Terminal
3. Serverauditor – SSH Shell / Console / Terminal

DOCUMENTATION

1. Dash is an API Documentation Browser that gives your iPad and iPhone instant offline access to 150+ API documentation sets.

REPOSITORIES

1. CodeBucket is the best way to browse and maintain your Bitbucket repositories on any iPhone, iPod Touch, and iPad
2. Git2Go is the first app which unleashes your full development productivity from everywhere.
3. GitLab Control is the best way to manage your GitLab projects on any iPhone, iPod Touch and iPad device

Enjoy coding …

okayNav aims to progressively collapse navigation links into an off-screen navigation, instead of doing it for all the links at the same time.

okayNav@GitHub

Again another Google AMP article, this time dealing with Syntax Highlighting. If you have a code centric website, this is important.

In one of my last articles I talked about a Generic Syntax Highlighter.   This time I want to show you, how to add Syntax Highlighting with GeSHi to a custom template in AMP-WP.

FIRST SOME RESOURCES

Please read up on documentation, as I am not diving into every detail.

1. AMP-WP – github.com/Automattic/amp-wp / Documentation
   The WordPress AMP integration. We will be using a custom template for our AMP pages.
2. Crayon Syntax Highlighter – github.com/aramk/crayon-syntax-highlighter
   I am using this for Syntax Highlighting on none AMP pages. It adds specific language classes to the code / pre areas, that I am using to configure GeSHi.
3. GeSHi – github.com/GeSHi/geshi-1.0
   The Syntax Highlighter
4. phpQuery – github.com/punkave/phpQuery
   DOM Document transversal & modification simplified. You should be able to apply the things below with any other tool as well.
5. My tweaks on GitHub

ADDING GESHI TO AMP-WP

1. Upload GeSHi and phpQuery to your desired location on your webserver.
2. Call the custom template for AMP-WP in your functions.php
   
   PHP

   add_filter( 'amp_post_template_file', 'xyz_amp_set_custom_template', 10, 3 ); function xyz_amp_set_custom_template( $file, $type, $post ) { if ( 'single' === $type ) { $file = dirname( __FILE__ ) . '/templates/my-amp-template.php'; } return $file; }

   1 2 3 4 5 6 7 8

   add_filter( 'amp_post_template_file', 'xyz_amp_set_custom_template', 10, 3 );   function xyz_amp_set_custom_template( $file, $type, $post ) {     if ( 'single' === $type ) {         $file = dirname( __FILE__ ) . '/templates/my-amp-template.php';     }     return $file; }

   
   I have an example stored on GitHub
3. Create a custom template in your themes folder.We could use the following filters, but its easier to use the custom template, due to the GeSHi style setup. The problem is, that the style action is called before the content action within the template. But I am planning to build a TWIG template for myself, as I am running Timber everywhere. That will detach logic and content completely, allowing to rethink some of these things and make styling a lot easier :) So watch out for my next article!
   
   add_action( 'pre_amp_render_post', 'xyz_amp_add_custom_actions' ); add_action( 'amp_post_template_css', 'xyz_amp_my_additional_css_styles' );

   1 2	add_action( 'pre_amp_render_post', 'xyz_amp_add_custom_actions' ); add_action( 'amp_post_template_css', 'xyz_amp_my_additional_css_styles' );

   
   Add this to the top of your custom template:
   
   PHP

   // Load phpQuery require ('my-libs/phpQuery/phpQuery.php'); // Load GesSHi require ('my-libs/geshi/geshi.php'); // Get AMP content and add it to phpQuery $doc = phpQuery::newDocumentHTML($this->get('post_amp_content')); $highlight = array(); // Loop through the code snippets (pre tags) foreach(pq('pre') as $snippet) { // Get classes of tag $class = pq($snippet)->attr("class"); // Check for Crayon Syntax Highlighter Class if (strpos($class, "lang:") !== false && strpos($class, "lang:default") === false) { preg_match("/lang:(?P<lang>\w+)/", $class, $catch); } else { // Fallback, if no language is detected $catch['lang'] = "php"; } // New Syntax Highlighter for each code snippet, with the correct language set // Storing for later stylesheet output. This makes also sure that stylesheets are only loaded once. $highlight[$catch['lang']] = new GeSHi(pq($snippet)->text() , $catch['lang']); // Uses Classes and no inlien styles $highlight[$catch['lang']]->enable_classes(); // Update code snippet $html = pq($snippet)->html($highlight[$catch['lang']]->parse_code()); }

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

   // Load phpQuery require ('my-libs/phpQuery/phpQuery.php');   // Load GesSHi require ('my-libs/geshi/geshi.php');   // Get AMP content and add it to phpQuery   $doc = phpQuery::newDocumentHTML($this->get('post_amp_content')); $highlight = array();   // Loop through the code snippets (pre tags)   foreach(pq('pre') as $snippet) {   // Get classes of tag   $class = pq($snippet)->attr("class");   // Check for Crayon Syntax Highlighter Class   if (strpos($class, "lang:") !== false && strpos($class, "lang:default") === false) { preg_match("/lang:(?P<lang>\w+)/", $class, $catch); } else {   // Fallback, if no language is detected   $catch['lang'] = "php"; }   // New Syntax Highlighter for each code snippet, with the correct language set // Storing for later stylesheet output. This makes also sure that stylesheets are only loaded once.   $highlight[$catch['lang']] = new GeSHi(pq($snippet)->text() , $catch['lang']);   // Uses Classes and no inlien styles   $highlight[$catch['lang']]->enable_classes();   // Update code snippet   $html = pq($snippet)->html($highlight[$catch['lang']]->parse_code()); }

   
   I have an example stored on GitHub. The above works, if you are using Crayon Syntax Highlighter for standard pages.
   If you use something else, this needs to be changed.
4. Add the GeSHi styles to the amp-custom style tag
   
   
   PHP

   <style amp-custom> <?php $this->load_parts( array( 'style' ) ); ?><?php do_action( 'amp_post_template_css', $this ); // Load Stylesheets for highlighted languages foreach($highlight as $store){ echo $store->get_stylesheet(); } ?> </style>

   1 2 3 4 5 6 7 8 9 10 11 12

   <style amp-custom> <?php $this->load_parts( array( 'style' ) ); ?><?php do_action( 'amp_post_template_css', $this );      // Load Stylesheets for highlighted languages foreach($highlight as $store){   echo $store->get_stylesheet(); } ?> </style>

   
   I have an example stored on GitHub.
5. Output updated amp-wp-content
   
   
   PHP

   <div class="amp-wp-content"> <h1 class="amp-wp-title"><?php echo wp_kses_data( $this->get( 'post_title' ) ); ?></h1> <ul class="amp-wp-meta"> <?php $this->load_parts( apply_filters( 'amp_post_template_meta_parts', array( 'meta-author', 'meta-time', 'meta-taxonomy' ) ) ); ?> </ul> <?php echo $doc->html(); // amphtml content; no kses ?> </div>

   1 2 3 4 5 6 7

   <div class="amp-wp-content"> <h1 class="amp-wp-title"><?php echo wp_kses_data( $this->get( 'post_title' ) ); ?></h1> <ul class="amp-wp-meta"> <?php $this->load_parts( apply_filters( 'amp_post_template_meta_parts', array( 'meta-author', 'meta-time', 'meta-taxonomy' ) ) ); ?> </ul> <?php  echo  $doc->html();  // amphtml content; no kses ?> </div>

   
   I have an example stored on GitHub.
6. Save and check that your AMP page validates, by adding #development=1 to the end of the url. Check the console for errors.
   Show this page as AMP

Enjoy coding …

The AMP (Accelerated Mobile Pages Project) plugin for WordPress is still pretty young and under heavy development.

There are little things that can help to fix current validation problems. I have a couple of fresh AMP pages, that are already indexed by Google.

0. RESOURCES

• AMP HTML
• AMP-WP
• Allowed HTML Tags
• Allowed Tags & Attributes
• Validation Errors

1. MISSING IMAGE (schema.org-NewsArticle)

The currently registered Microformats template (schema.org-NewsArticle) requires an image.
The AMP-WP documentation explains how to add a featured image to your pages (documentation).

I extended that a bit,  to link a default attachment image, I uploaded before. This needs to be added to your themes functions.php.

Next we adjust the Microformats definition. This needs to be added to your themes functions.php.

2. ADD YOUR OWN AMP TEMPLATE

Read the AMP-WP documentation first :) This forces AMP-WP to override the core template with your own. Use the default template as a reference.

3. REMOVE NONE VALIDATING CONTENT

Normally the core sanitizer should take care of that.  I am sure a filter will be added in the future. For now, this is a quick workaround. You can use a RegExp or DOMDocument to alter the amp-content in your custom template and filter things that break validation.

I am using phpQuery for now, as it allows me to add quick fixes. DOMNode or QueryPath works nicely as well :) Will be looking at the core sanitizer and options later this week. All of this is currently added to the custom template.

1. Remove REL attributes that are not allowed. Only registered Microformat rel attributes are allowed.
   
   $doc['.prettyphoto']->removeAttr("rel");

   1	$doc['.prettyphoto']->removeAttr("rel");

2. Remove attribute ALIGN
   
   $doc['*']->removeAttr("align");

   1	$doc['*']->removeAttr("align");

3. Fix TARGET Attribute
   
   $doc['a[target="new"]']->attr("target","_blank");

   1	$doc['a[target="new"]']->attr("target","_blank");

Finally output the fixed content as HTML.

The above examples need to be tweaked to your specific content requirements.

The custom template “post_amp_content” before:

The custom template “post_amp_content” after:

4. ADD PREVIOUS & NEXT POST NAVIGATION

From the AMP specification :”Note, that AMP document may also be linked to directly…”

This is being added to the custom template as well.

Next:

Previous:

5. SYNTAX HIGHLIGHTING

You can find a simple pure PHP highlighter here. Not perfect, but a start. Don not forget to include the CSS :)

I will extend on this as new validation errors or tweaks come up. The core sanitizer of AMP-WP still needs some work and should allow us to do some of the above directly, when the content is parsed / converted for AMP.

 6. OTHER AMP ARTICLES

Make Syntax Highlighting work in AMP-WP using GeSHi

Time to get AMP ready

Enjoy coding …