Peter Wilson peterwilsoncc

## phpversion.sh
#!/bin/sh

printf "Switching php to version 7.1 with symlinks.\n"
printf "Press any key to continue...\n"

read CONTINUE

printf "Creating backups..."

# Backup original binaries

## functions.php
<?php
/*
 * mytheme_form_submit_button
 *
 * Filter the Gravity Forms button type to change it to a proper button
 */
function mytheme_form_submit_button( $button, $form ) {
	$button = str_replace( "input", "button", $button );
	$button = str_replace( "/", "", $button );
	$button .= "{$form['button']['text']}</button>";

## frontendplugins.md

      
              1 file
            
          
              2 forks
            
          
              44 comments
            
          
              41 stars
            
          
                chriscoyier
                / frontendplugins.md
            
            
              Last active
              March 3, 2021 17:31
            
              
                How WordPress Plugins Should Handle Front End Resources
              
          
      View frontendplugins.md
  
      
    How WordPress Plugins Should Handle Front End Resources

This is a WORK IN PROGRESS intended for fleshing out and feedback

It's very common for people to be unhappy with how a WordPress plugin adds front end resources to their site. If a plugin needs CSS, the plugin will add a <link> element to that CSS. If the plugin needs JavaScript, it will add a <script> to that JavaScript.
Plugins do this because it works. It's damn important for a WordPress plugin to work, even in adverse conditions. They rightfully want good ratings and little customer support.
But this comes at the cost of additional HTTP requests. In optimizing front end performance of a site, reducing the number of HTTP requests is a huge thing. Front end developers want to decide and control how front end resources are being handled, and WordPress plugins don't typically make this easy on them.

  
## noncritcss.md

      
              1 file
            
          
              10 forks
            
          
              44 comments
            
          
              215 stars
            
          
                scottjehl
                / noncritcss.md
            
            
              Last active
              August 12, 2023 16:57
            
              
                Comparing two ways to load non-critical CSS
              
          
      View noncritcss.md
  
      
    I wanted to figure out the fastest way to load non-critical CSS so that the impact on initial page drawing is minimal.
TL;DR: Here's the solution I ended up with: https://github.com/filamentgroup/loadCSS/

For async JavaScript file requests, we have the async attribute to make this easy, but CSS file requests have no similar standard mechanism (at least, none that will still apply the CSS after loading - here are some async CSS loading conditions that do apply when CSS is inapplicable to media: https://gist.github.com/igrigorik/2935269#file-notes-md ).
Seems there are a couple ways to load and apply a CSS file in a non-blocking manner:

  
## criticalcss-bookmarklet-devtool-snippet.js
(function() {
  var CSSCriticalPath = function(w, d, opts) {
    var opt = opts || {};
    var css = {};
    var pushCSS = function(r) {
      if(!!css[r.selectorText] === false) css[r.selectorText] = {};
      var styles = r.style.cssText.split(/;(?![A-Za-z0-9])/);
      for(var i = 0; i < styles.length; i++) {
        if(!!styles[i] === false) continue;
        var pair = styles[i].split(": ");

## css.css
#js-mediaquery {
  overflow: hidden;
  width: 1px;
  height: 1px;
  position: absolute;
  top: -999999em;
  left: auto;
  clip: rect(1px 1px 1px 1px); /* IE6, IE7 */
  clip: rect(1px, 1px, 1px, 1px);
}

## gist:2628225
#!/bin/bash
# cd into the directory
cd ~/gitsync/github-wordpress-sync/;
# Make sure we are not already running
if [ -f .sync-running ];then
	if test ! `find ".sync-running" -mmin +10`;then
		# Currently running, but not stuck
		exit 1;
	fi
fi;

## normalized.html
<!doctype html>

<html>
  <head>
    <!-- Encoding -->
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    <!-- Always force latest IE rendering engine (even in intranet) & Chrome Frame -->
    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"></meta>


## README.md

      
              2 files
            
          
              52 forks
            
          
              21 comments
            
          
              355 stars
            
          
                necolas
                / README.md
            
            
              Last active
              April 29, 2023 14:59
            
              
                Experimenting with component-based HTML/CSS naming and patterns
              
          
      View README.md
  
      
    NOTE I now use the conventions detailed in the SUIT framework
Template Components
Used to provide structural templates.
Pattern
t-template-name


## ie-css-hacks.css
/*
 * Property prefix hacks
 */

/* IE6 only - any combination of these characters */

_ - £ ¬ ¦

/* IE6/7 only - any combination of these characters */
	#!/bin/sh

	printf "Switching php to version 7.1 with symlinks.\n"
	printf "Press any key to continue...\n"

	read CONTINUE

	printf "Creating backups..."

	# Backup original binaries
	<?php
	/*
	* mytheme_form_submit_button
	*
	* Filter the Gravity Forms button type to change it to a proper button
	*/
	function mytheme_form_submit_button( $button, $form ) {
	$button = str_replace( "input", "button", $button );
	$button = str_replace( "/", "", $button );
	$button .= "{$form['button']['text']}</button>";
	(function() {
	var CSSCriticalPath = function(w, d, opts) {
	var opt = opts \|\| {};
	var css = {};
	var pushCSS = function(r) {
	if(!!css[r.selectorText] === false) css[r.selectorText] = {};
	var styles = r.style.cssText.split(/;(?![A-Za-z0-9])/);
	for(var i = 0; i < styles.length; i++) {
	if(!!styles[i] === false) continue;
	var pair = styles[i].split(": ");
	#js-mediaquery {
	overflow: hidden;
	width: 1px;
	height: 1px;
	position: absolute;
	top: -999999em;
	left: auto;
	clip: rect(1px 1px 1px 1px); /* IE6, IE7 */
	clip: rect(1px, 1px, 1px, 1px);
	}
	#!/bin/bash
	# cd into the directory
	cd ~/gitsync/github-wordpress-sync/;
	# Make sure we are not already running
	if [ -f .sync-running ];then
	if test ! `find ".sync-running" -mmin +10`;then
	# Currently running, but not stuck
	exit 1;
	fi
	fi;
	<!doctype html>

	<html>
	<head>
	<!-- Encoding -->
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

	<!-- Always force latest IE rendering engine (even in intranet) & Chrome Frame -->
	<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"></meta>
	/*
	* Property prefix hacks
	*/

	/* IE6 only - any combination of these characters */

	_ - £ ¬ ¦

	/* IE6/7 only - any combination of these characters */