Template for Styleguide Template
A Pen by Matt Harris on CodePen.
A simple single-page styleguide template to get started with theming and/or documenting your styles.
<?php | |
/** | |
* Custom WordPress configurations on "wp-config.php" file. | |
* | |
* This file has the following configurations: MySQL settings, Table Prefix, Secret Keys, WordPress Language, ABSPATH and more. | |
* For more information visit {@link https://codex.wordpress.org/Editing_wp-config.php Editing wp-config.php} Codex page. | |
* Created using {@link http://generatewp.com/wp-config/ wp-config.php File Generator} on GenerateWP.com. | |
* | |
* @package WordPress | |
* @generator GenerateWP.com |
<?php | |
/** | |
* php-ansi-color | |
* | |
* Original | |
* https://github.com/loopj/commonjs-ansi-color | |
* | |
* @code | |
* <?php | |
* require_once "ansi-color.php"; |
Template for Styleguide Template
A Pen by Matt Harris on CodePen.
A simple single-page styleguide template to get started with theming and/or documenting your styles.
--- | |
parser: espree | |
env: | |
amd: false | |
browser: false | |
es6: false | |
jasmine: false | |
jquery: false | |
meteor: false | |
mocha: false |
#!/bin/sh | |
# | |
# a simple way to parse shell script arguments | |
# | |
# please edit and use to your hearts content | |
# | |
ENVIRONMENT="dev" |
Standard Readme Style
Your README file is normally the first entry point to your code. It should tell people why they should use your module, how they can install it, and how they can use it. Standardizing how you write your README makes creating and maintaining your READMEs easier. Great documentation takes work!
This repository contains:
The standard code style linter is a great tool by Feross - check it out!
Remove trailing semicolons:
find . -path ./node_modules -prune -o -type f -name '*.js' -exec sed -i '' -e 's/;$//' {} \;
Ensure space between function
and opening bracket:
// THE URL FOR THE MAIN INSTAGRAM IMAGE DOES NOT TRIGGER THE DOWNLOAD EVENT | |
// INSTEAD IT OPENS THE IMAGE IN A NEW TAB | |
// RUNNING THE SCRIPT THE SECOND TIME TRIGGERS THE DOWNLOAD EVENT | |
// KEYBOARD SHORTCUT MAKES THIS TWO STEP PROCESS VERY QUICK | |
// Step 1: `ctrl`+`shift`+`i` -> `ctrl`+`enter` | |
// Step 2: `ctrl`+`enter` | |
var filename = ''; | |
var target = ''; |
//// | |
/// @group layout | |
//// | |
/// | |
/// @name max_width | |
/// @description Insert media content when less than target width | |
/// @param {number} $width [max width value] | |
@mixin max_width($width) { | |
@media screen and (max-width: #{$width}) { |