You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want functions.php itself to still be somewhere junior devs can copy/paste functions from google and have them work the way they're expecting. But I also want to separate out all of the reusable parts into a more logical structure.
So file structure would be: functions.php, in the root, and then a /functions/ directory, with files in that can be included.
e.g. functions.php:
<?php
include_once 'functions/theme-config.php'; // setup theme, thumbnail sizes, register nav menus, widgets etc.
include_once 'functions/stylesheets.php'; // attach CSS
include_once 'functions/js.php'; // attach JS
include_once 'functions/shortcodes.php'; // theme specific shortcodes
include_once 'functions/login.php'; // override login styling
include_once 'functions/google-analytics.php';
// Misc theme functions can be added after here:
The text was updated successfully, but these errors were encountered:
mike-source
changed the title
Functions.php is starting to get clutterred
Functions.php is starting to get cluttered
Jul 10, 2015
I want functions.php itself to still be somewhere junior devs can copy/paste functions from google and have them work the way they're expecting. But I also want to separate out all of the reusable parts into a more logical structure.
So file structure would be: functions.php, in the root, and then a /functions/ directory, with files in that can be included.
e.g. functions.php:
The text was updated successfully, but these errors were encountered: