mirror of
https://github.com/inretio/WordPress-Plugin-Boilerplate
synced 2025-04-19 05:35:36 +03:00
Remove .org parent folder structure
Flattening the folder structure for a bit easier auto-inclusion into projects and local development. See: https://github.com/DevinVinson/WordPress-Plugin-Boilerplate/issues/295
This commit is contained in:
parent
3d3f181924
commit
5391e0ca27
27 changed files with 8 additions and 51 deletions
32
plugin-name/public/js/plugin-name-public.js
Normal file
32
plugin-name/public/js/plugin-name-public.js
Normal file
|
@ -0,0 +1,32 @@
|
|||
(function( $ ) {
|
||||
'use strict';
|
||||
|
||||
/**
|
||||
* All of the code for your public-facing JavaScript source
|
||||
* should reside in this file.
|
||||
*
|
||||
* Note that this assume you're going to use jQuery, so it prepares
|
||||
* the $ function reference to be used within the scope of this
|
||||
* function.
|
||||
*
|
||||
* From here, you're able to define handlers for when the DOM is
|
||||
* ready:
|
||||
*
|
||||
* $(function() {
|
||||
*
|
||||
* });
|
||||
*
|
||||
* Or when the window is loaded:
|
||||
*
|
||||
* $( window ).load(function() {
|
||||
*
|
||||
* });
|
||||
*
|
||||
* ...and so on.
|
||||
*
|
||||
* Remember that ideally, we should not attach any more than a single DOM-ready or window-load handler
|
||||
* for any particular page. Though other scripts in WordPress core, other plugins, and other themes may
|
||||
* be doing this, we should try to minimize doing that in our own work.
|
||||
*/
|
||||
|
||||
})( jQuery );
|
Loading…
Add table
Add a link
Reference in a new issue