- https://github.com/congtrieu112/phim
- https://github.com/shaddyy21/Lavish-Lawn
- https://github.com/sohilgupta/datamelons
- https://github.com/jtebeau/mmm
- https://github.com/mohitkr05/_wplove
- https://github.com/jimchristie/dev_jimchristie_me
- https://github.com/vee879/wordpress_4_3_1
- https://github.com/hamedb89/wp-theme-boilerplate
- https://github.com/master2be1/redux-framework
- https://github.com/DarrenJansen/Sites
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
<?php | |
/** | |
* Get an array of gravity forms. | |
* | |
* @since 1.0.0 | |
* | |
* @return void | |
*/ | |
function jdn_gf_options() { | |
$form_array = array(); |
I have made this function using the WP_Image_Editor class and I have filtered through the "wp_generate_attachment_metadata" hook. You can modify the "theme" namespace into function names with your theme name or in anyway you like.
Applying the filter directly to wp_generate_attachment_metadata the image placeholders are auto added into WordPress metadata, so when your add/modify/delete an image (or regenerate it via a plugin), it accomplishes to modify also to the image placeholders.
The use of the native theme support can prevent the generation of lqip or target specific image sizes to generate.
It contains an hook filter lqip_quality to modify the quality without have to modify the function.
/* | |
##Device = Desktops | |
##Screen = 1281px to higher resolution desktops | |
*/ | |
@media (min-width: 1281px) { | |
/* CSS */ | |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
,elem.offsetTop
,elem.offsetWidth
,elem.offsetHeight
,elem.offsetParent
/* iPhone 6 landscape */ | |
@media only screen and (min-device-width: 375px) | |
and (max-device-width: 667px) | |
and (orientation: landscape) | |
and (-webkit-min-device-pixel-ratio: 2) | |
{ } | |
/* iPhone 6 portrait */ | |
@media only screen | |
and (min-device-width: 375px) |
// This leaks insane amounts of memory | |
var fetchCallback = function(resolve, reject) { | |
resolve({'some':'test'}) | |
} | |
var fetch = function() { | |
return new Promise(fetchCallback) | |
} | |