Project 1 Update: The Functions File Diet Plan

Written by

WAV DIGITAL

in

,

Remember our promise to build a WordPress theme that wouldn’t make developers cry? Well, we’re back with update, and it’s all about putting functions.php on a strict diet. Not WordPress’s version of a diet, mind you – where they generously include every feature you never asked for – but an actual, meaningful reduction in digital bloat.

First things first: our file structure. We’ve kept it minimalist – no fancy bells and whistles, just the essentials:

404.php         functions.php    js/
archive.php     header.php       page.php
footer.php      index.php        single.php
                                template-parts/

Beautiful, isn’t it? Like a capsule wardrobe for your WordPress theme. No drawers full of unused templates collecting digital dust.

Now, let’s dive into functions.php, where we’re doing the equivalent of spring cleaning (in February, because who follows rules anymore?). First up, we’re adding support for the features we actually want:

add_theme_support('title-tag');
add_theme_support('post-thumbnails');
add_theme_support('custom-logo');
add_theme_support('html5', array('navigation','style'));
add_theme_support('automatic-feed-links');
add_theme_support('post-formats', array(
    'aside','gallery','link','image',
    'quote','status','video','audio','chat'
));
add_theme_support('custom-background');
add_theme_support('menus');

Yes, we’re keeping title tags (because SEO is still a thing), post thumbnails (because we’re not savages), and menus (because even minimalists need navigation). We’re even throwing in post formats – call us generous.

For navigation, we’re setting up a proper menu structure:

register_nav_menus(array(
    'primary' => __('Primary Menu', 'lowvol-25'),
    'secondary'  => __('Secondary Menu', 'lowvol-25'),
    'tertiary'  => __('Tertiary Menu', 'lowvol-25'), 
));

But here’s where it gets fun. WordPress, in its infinite wisdom, loves to include things you never asked for. So we’re channeling our inner Marie Kondo and asking, “Does this spark joy?” Spoiler alert: most of it doesn’t.

wp_dequeue_style('classic-theme-styles');
wp_dequeue_style('wp-block-library');
wp_dequeue_style('global-styles');
wp_dequeue_style('core-block-supports');

Goodbye, unnecessary style blocks. You won’t be missed.

And because we live in 2025, not 1995, we’re also saying farewell to some… interesting default features:

remove_action('wp_head', 'print_emoji_detection_script', 7);
remove_action('wp_print_styles', 'print_emoji_styles');
remove_action('wp_head', 'wp_print_auto_sizes_contain_css_fix', 1);

Yes, WordPress still thinks we’re printing websites. Save a tree, use a screenshot instead. And those emoji scripts? Unless your client is a 13-year-old’s diary blog, you probably don’t need those loading on every. single. page.

The result? A functions file that doesn’t make your browser cry for mercy. It’s like going from a “War and Peace”-sized manuscript to a concise haiku. Sure, we might add more features later, but they’ll be features we actually want, not just digital breadcrumbs WordPress scattered around because it felt like being helpful.

Stay tuned for our next update, where we’ll tackle something equally thrilling. After all, there’s still plenty of WordPress quirks left to untangle.

More posts