Our Do Not Call Promise

solarbluseth / October 7, 2026

Our Do Not Call Promise

If your number is on the Do Not Call list, SolarBlu.net will not call you. No exceptions, no loopholes, no arguing about whether it’s a business line.

We make outbound calls to local businesses about websites, hosting and internet services. We know how it feels to get a call you didn’t ask for, so here’s exactly how we handle it.

What we do before we ever dial

Every month, as federal law requires, we download the latest National Do Not Call Registry for every area code we call and load it into our own system. That fresh list then gets passed down the line, and every calling list we use is checked against it. Nothing in our pipeline skips that step.

Any number that shows up on the registry comes off our lists that same day. It doesn’t get set aside for later. It gets deleted.

On the list? We don’t call. Period.

Plenty of small business owners list their personal cell on their Facebook page or Google listing. Lots of those cells were put on the Do Not Call list years ago.

Some companies will tell you that a business listing makes it fair game. We don’t play that game. If the number is on the list, we treat it as off-limits, whether it’s a personal line, a business line, or both.

That way, if you ever get a call from us, we can say with certainty that your number was not on the Do Not Call list when we dialed it.

Ask us to stop and we stop

You don’t have to be on any registry to stop hearing from us. Tell whoever calls “please don’t call me again,” and that’s the end of it.

We’ll take you right off the list and move on with our lives. No pushback, no “just one more minute,” and no follow-up call next month.

A tip for business owners: get a business line

If your personal cell is the number on your business listing, you’re mixing two lives on one phone. Customers call it at 9pm on a Sunday, and legitimate companies that follow the rules may never call you at all.

A separate business number fixes both. A free Google Voice number or a cheap second line that rings your cell keeps your personal number private. It also lets you set business hours, and it looks more professional on your website.

We practice what we preach. As a technology company, we answer hosting support calls around the clock, and those calls still come in on a business line, not anyone’s personal cell.

The bottom line

We’d rather lose a lead than make a call we shouldn’t. If you’re on the list, we won’t call. If you ask us to stop, we stop. Questions about how we handle calls? Reach out at solarblu.net and we’ll tell you straight.

Custom PHP Development

Header Glow-Up, Mobile Fixes & a Little Rocket

solarbluseth / October 6, 2026

Dev Log · Advanced Themer 13

Header Glow-Up, Mobile Fixes & a Little Rocket

Today was a big one for Advanced Themer 13. We rebuilt how the header is put together so it can carry a real logo, gave the phone number a proper home, got everything behaving on phones, and added a floating admin launcher for editing on the fly. Oh, and we upgraded to the newest WordPress the same afternoon. No pressure.

October 6, 2026 · WordPress 7.1.2 · Astra 4.13 · SolarBluSeth

Header logo slot

Fixed

Phone placement

3 bugs

Squashed on mobile

7 links

In the Advt Admin menu

7.1.2

WordPress, still compatible

A real logo, right before the title

Header Options now has a Logo field with a Media Library picker and a height slider, plus a live preview at the top of the settings page. Rather than squeezing an extra <img> into the markup, we feed the logo into the theme's own logo slot. That way Astra handles placement, it stays accessible, and it doesn't break on the next theme update.

The trick is that WordPress lets you filter any theme mod on the way out. Here's the general pattern (simplified):

// Point the theme's custom_logo at an image chosen in our own settings.
add_filter( 'theme_mod_custom_logo', function ( $value ) {
    $url = get_option( 'my_plugin_logo' );
    return $url ? attachment_url_to_postid( $url ) : $value;
} );

Docs: theme_mod_{$name} · attachment_url_to_postid() · get_custom_logo

Lesson of the day: "Why won't it save?!"

The first version of the logo field showed up fine but quietly refused to save. The culprit: the new option was registered in an older copy of a settings file that the plugin doesn't actually load anymore. When you post to options.php, WordPress only saves options it knows about through register_setting(). Anything else is dropped without an error. Moral: when a field won't stick, check where it's registered, not just whether it is.

The phone number found its seat

The phone number used to live in a separate row under the menu, where it ended up stranded with odd spacing. Funny thing: adding it to the menu by hand always looked right. So we did the same thing in code. The plugin now adds the phone (and the CTA button) to the end of the primary menu, so it sits in its own slot at the far right with a subtle divider.

add_filter( 'wp_nav_menu_items', function ( $items, $args ) {
    if ( 'primary' !== $args->theme_location ) return $items;
    return $items . '<li class="menu-item my-phone">…</li>';
}, 10, 2 );

Docs: wp_nav_menu_items. It still pulls from the Header Options settings, so editing the number updates desktop and mobile at once.

Mobile: three gremlins, three fixes

The invisible hamburger

CSS

The menu toggle was there the whole time, just drawn in the theme's default blue on top of a dark banner. It now uses the header text and hover colors, so it shows up on any banner.

The "every page ever" menu

MenusFallback

Astra's mobile header uses its own menu location. With nothing assigned there, WordPress fell back to listing every single page on the site, test pages included. Now, if the mobile slot is empty, it mirrors the primary menu automatically, CTA and phone included.

Client Logo

Responsive

A big logo plus a 34px title on a 375px screen meant the site name wrapped one syllable per line. On smaller screens the logo and title now scale down so they fit neatly beside the toggle.

Debugging tip: if a theme seems to ignore your wp_nav_menu_args filter, it may be skipping wp_nav_menu() entirely and calling the fallback itself when has_nav_menu() comes back false. A quick temporary log of the arguments tells you which path you're on. That's what pointed us to the fix.

Meet "Advt Admin"

New this round is a little rocket button pinned to the bottom-right corner of the front end. Tap it and a menu pops up with everything we reach for most:

Edit in place

Edit this page, with the page ID shown right in the label
Edit with Composer (Visual Composer / WPBakery)
Edit with Elementor

Create something new

Add new media
Add new page
Add new post

Polite by design

Only logged-in editors ever see it
Each link checks current_user_can()
Hides inside page-builder previews
Everything opens in a new tab, and Esc closes the menu

It hooks into wp_footer, so it works with any theme, not just Astra. It also politely moves the theme's scroll-to-top arrow out of its way.

Upgrade day: WordPress 7.1.2

We also moved the dev site to the latest WordPress today, mid-sprint, because why not. Advanced Themer 13 loaded cleanly, settings saved, and the header, menus and admin launcher all behaved. We'll keep watching it over the next few days, but so far so good.

WordPress 7.1.2Updated today · running clean

Astra 4.13Header builder · desktop + mobile

Advanced Themer 13Compatible · no errors

Keeping an eye on itReal-world testing continues

Today at a glance

Step 1

Logo field: Media Library picker, height control, live preview, wired into the theme's logo slot.

Step 2

Save bug: tracked down to an option registered in a file that isn't loaded. Moved it to the right place.

Step 3

Phone number: moved from its own row into the menu, in its own slot on the right.

Step 4

Full-width containers: the header and content can now use the whole width of the screen.

Step 5

Mobile: a visible toggle, the real menu, and a title that fits.

Step 6

Advt Admin: the rocket launcher, with Composer and Elementor shortcuts.

Step 7

WordPress 7.1.2: upgraded, tested, still compatible.

More soon. Advanced Themer keeps getting better one dev log at a time.
Built with , WordPress hooks, and stubbornness by SolarBluSeth.

Custom PHP Development

Building SETHaoke26 with Claude AI

solarbluseth / September 21, 2026

🚀 Project Overview

SETHaoke26 is a comprehensive, production-grade karaoke management system built with Claude AI to power professional streaming sessions. Featuring a 73,000+ song library with intelligent queue management, MIDI backing tracks, sound effects, and seamless OBS streaming integration, this system transforms how karaoke is managed and performed live.

⚡ Built with Claude AI
This entire system was architected and implemented using Claude AI, reducing development time and creating a clean, maintainable codebase that blends PHP backend power with modern frontend interactivity.

73,039

Total Songs in Library

13,777

Artists Catalogued

3,663

Lines of Production Code

🛠 Technology Stack

SETHaoke26 leverages a modern tech stack optimized for performance and reliability:

PHP 7.4+

MySQL

jQuery

JSON API

HTML5

CSS3

JavaScript

OBS Bridge

Architecture Highlights

PDO MySQL — Type-safe parameterized queries preventing SQL injection
AJAX Layer — Real-time interactions (delete, queue, mark played)
RESTful API — JSON responses for all data operations
File Streaming — Direct MP3/CDG serving for playback
CDG.js — Karaoke graphics synchronization
OBS Integration — HTML overlays for streaming displays

📊 Core Features

1. Song Library Interface

Browse and manage your entire collection with powerful search, filtering by artist, and quick play/queue actions:

Main Song Library: 73,039 songs with instant search, favorites, CDG indicators, and queue management

2. Singer Queue Management

Real-time queue management for coordinating tonight's karaoke rotation. Add singers, reorder queue, mark songs complete, and sync to OBS overlay:

Singer Queue: Manage rotation, track CDG status, and coordinate with streaming overlay

3. MIDI File Management

Direct MIDI file support for backing tracks and musical arrangements. Scan, organize, and play MIDI files seamlessly integrated with the main library.

4. Sound Effects Library

Categorized sound effects for transitions, alerts, and streaming enhancement. Quick-access buttons for live show operations.

5. Play Logging & Analytics

Track every song played with CSV logging (play_log.csv). Monitor play counts, artist popularity, and build performance analytics.

6. OBS Streaming Integration

Custom HTML overlays for OBS Studio including multi-platform alert system and audience counters for real-time engagement tracking.

💻 Technical Deep Dive

Database Schema

Clean, normalized MySQL structure with dynamic column management:

-- Songs table with flexible attributes
CREATE TABLE songs (
  id INT PRIMARY KEY AUTO_INCREMENT,
  artist VARCHAR(255),
  title VARCHAR(255),
  mp3_path VARCHAR(500),
  cdg_path VARCHAR(500),
  source VARCHAR(100),
  favorite TINYINT DEFAULT 0,
  active TINYINT DEFAULT 1,
  play_count INT DEFAULT 0
);
  

API Architecture (api.php)

RESTful API handling song deletion, artist removal, play tracking, and queue management:

// AJAX API endpoint for real-time interactions
$action = $_GET['action'] ?? '';

if ($action === 'delete_song') {
  // Remove song and linked CDG/MP3 files
  $pdo->prepare("DELETE FROM songs WHERE id=?")->execute([$id]);
}

if ($action === 'played') {
  // Increment play count, log to CSV
  $pdo->prepare("UPDATE songs SET play_count=play_count+1")->execute([$id]);
  // Write to play_log.csv for analytics
}
  

Frontend Interactivity (jQuery)

Smooth user experience with jQuery-powered AJAX calls, no page reloads:

// jQuery AJAX for delete without refresh
$('.delete-btn').click(function() {
  var songId = $(this).data('id');
  $.ajax({
    url: 'api.php?action=delete_song&id=' + songId,
    type: 'GET',
    success: function() {
      // Remove from DOM
      location.reload(); // Soft refresh
    }
  });
});
  

CDG Graphics (cdg.js)

JavaScript implementation for karaoke graphics synchronization, displaying lyrics and backgrounds in real-time with audio sync.

OBS Bridge

HTML overlays (obs_multi_alert_system.html, obs_overlay.html) embedded directly in OBS as browser sources for seamless streaming integration.

📈 Performance Metrics

25+

PHP Module Files

315

Lines in api.php

424

Lines in index.php

The system is optimized for speed with database indexing on artist/title, AJAX pagination limiting results to 50 items per page, and file system caching for CDG graphics.

🎯 Why Claude AI?

Claude AI made this project possible. Instead of months of solo development, we leveraged Claude's understanding of database architecture, API design, and JavaScript interactivity to build a cohesive system in days. The result is clean, maintainable code that blends:

Robust PHP/MySQL backend with proper parameterization
Modern jQuery frontend with real-time AJAX
RESTful JSON API design
Streaming platform integration (OBS)
Production-ready error handling and logging

Claude understood the full context of karaoke system requirements and produced code that handles edge cases, manages file systems safely, and provides an intuitive UX for live performance scenarios.

📺 OBS Streaming Overlay

One of the most powerful features of SETHaoke26 is its seamless OBS Studio integration. The system includes a purpose-built HTML overlay that displays real-time information directly on your stream, keeping your audience engaged and informed.

The Now Playing Overlay

A clean, professional browser source overlay that displays the current song status. The overlay features:

Live Status Display — Shows "Now Playing", "Loading", or current song info
Artist & Title — Full song information with singer attribution
Chat Commands — Displays !sr command for song requests
Responsive Design — Adapts to any stream resolution (720p, 1080p, 4K)
Beautiful Gradient UI — Professional light-blue aesthetic with smooth animations

OBS Overlay: "Now Playing — SETHaoke" with song request command (!sr) visible to chat

Integration with OBS Studio

Setting up the overlay in OBS is straightforward:

Open OBS Studio
Click "+" in Sources → Browser
Point to: /sethaoke26/obs_overlay.html
Set Resolution: 1920x1080 (or your stream size)
Enable Browser source refresh
Position overlay on your scene (corner recommended)
  

Real-Time Song Updates

The overlay includes JavaScript that can connect to your sethaoke26 backend to display live data:

// Fetch current track from your system
fetch('/sethaoke26/logs/current_track.json')
  .then(r => r.json())
  .then(data => {
    // Update overlay with:
    // - Artist name
    // - Song title
    // - Singer/performer name
    // - CDG status indicator
  });
  

Multi-Platform Streaming

The OBS overlay system also includes the obs_multi_alert_system.html file, a comprehensive alert system that:

Multi-Platform Support — Twitch, Kick, YouTube, and custom webhooks
Real-Time Notifications — Follows, subscriptions, donations, raids
Customizable Alerts — Sound effects, animations, and text overlays
Viewer Counter — Live audience size display
Engagement Tracking — Monitor chat activity and metrics

Why This Matters for Karaoke

For live karaoke streaming, the overlay serves critical functions:

Clarity — Viewers instantly know whose turn it is and what's playing
Engagement — The !sr command drives audience participation and song requests
Professionalism — Branded overlays elevate production value
Analytics — Track which songs get requested vs. performed
Accessibility — Closed captions and text-based information for all viewers

HTML & CSS Architecture

The overlay is built with clean, lightweight HTML and CSS for optimal performance:

.overlay-container {
  background: linear-gradient(135deg, #8ec5fc 0%, #b8d7f8 100%);
  display: flex;
  align-items: center;
  justify-content: center;
}

.now-playing-box {
  background: linear-gradient(135deg, #7ab8f5 0%, #9fd1ff 100%);
  padding: 40px 50px;
  box-shadow: 0 15px 40px rgba(0, 0, 0, 0.2);
  border-radius: 12px;
}

/* Smooth animations for state changes */
@keyframes pulse {
  0%, 100% { opacity: 1; }
  50% { opacity: 0.7; }
}

.loading { animation: pulse 1.5s ease-in-out infinite; }
  

Future Enhancements

The overlay system is designed to be extensible. Potential features include:

Leaderboard of most-sung artists
Countdown timer to next performance
Singer profile cards with photo/social handles
Integration with Discord bot for moderation
Custom animations and transitions

🚀 What's Next?

SETHaoke26 is actively maintained and ready for streaming. Potential enhancements include:

Web-based remote queue management for audience requests
Discord bot integration for Twitch/Kick chat commands
Playlist scheduling and show templates
Advanced analytics dashboard
Mobile companion app for singers

SETHaoke26 — Powering professional karaoke streams on Twitch, Kick, and beyond.

Built with Claude AI | Made by Seth @ SolarBlu.net

Custom PHP Development

The WordPress Paradox: Why Developers Leave (And Why You Shouldn't)

solarbluseth / September 16, 2026

Published on SolarBlu.net • 8 min read • For Freelance Developers & Agencies

The WordPress Paradox: Why Developers Leave (And Why You Shouldn't)

Master custom HTML templates + "vibe coding" to get the best of WordPress flexibility with full coding freedom

Here's the thing about WordPress: 43% of all websites on the internet run on WordPress. That's not a niche player anymore. That's the entire landscape.Yet developers keep abandoning it. They complain about page builders limiting their vision, plugins bloating sites, themes forcing design decisions, and the inability to write "real code."

The irony? They're leaving the one platform that gives them the most power. They just don't know it yet.

43%

of all websites run on WordPress — 10x more than Shopify, Wix, and Squarespace combined

The Siren Song of "Building From Scratch"

I get it. You want control. You want to write clean code without theme limitations. You want to structure your data exactly how you want. So you pitch clients a custom Next.js build, a Laravel backend, or a React SPA.

And then reality hits:

Day 1-7: Building authentication, user roles, and admin panels you thought would take 2 days
Day 8-21: Creating a simple editor for content that WordPress gave you for free
Week 4-8: Rebuilding what WooCommerce, SEO plugins, and backup systems do automatically
Month 3+: Maintaining a custom system while the client asks "why can't I just add a popup like on that other site?"

Then your client wants a new feature. They Google it. Find a plugin. Get frustrated it won't work with your custom build. Switch platforms.

61,000+

WordPress plugins available — solving nearly every business problem

WordPress plugin submissions doubled in 2025 alone

What You Actually Lose by Leaving WordPress

When you leave WordPress for a custom build, you're not just losing "a platform." You're losing:

Feature	WordPress	Custom Build
Content Management	✓ Built-in, intuitive	✗ Must rebuild
User Management & Roles	✓ Complex permissions included	✗ Major development effort
SEO Optimization	✓ Yoast, Rank Math, built-in	✗ Start from scratch
Security Updates	✓ Auto-updates, huge community	✗ Your responsibility entirely
Backup & Recovery	✓ Dozens of plugins, one-click	✗ Build custom solution
E-commerce	✓ WooCommerce: $0-20k+ setup	✗ $50k-200k+ development
Email Marketing Integration	✓ 100+ plugins ready	✗ API integration work
Future Development	✓ Plugin ecosystem grows daily	✗ 100% custom maintenance
Client can manage it themselves	✓ Familiar interface	✗ Depends on what you build

Enter "Vibe Coding": The Best of Both Worlds

Here's what nobody tells you: You don't have to choose.

WordPress has a superpower that most developers never tap into: custom HTML templates with full PHP control. You can:

Write your own PHP, JavaScript, and CSS — no page builder required
Keep WordPress's content management, user system, and plugin ecosystem
Create truly custom designs and interactions
Charge premium rates because you're solving real problems efficiently
Give clients power to manage content without touching code

This is what I call "Vibe Coding" — building what feels like a custom application, but leveraging WordPress infrastructure. You get the developer satisfaction of writing real code, plus the client satisfaction of true management capabilities.

The Math: Custom build might save you from 2% of development friction, but costs you 300% more in total dev time, maintenance, and client support. WordPress + vibe coding gives you 95% of the freedom at 40% of the effort.

How to Convert Standard HTML Pages to WordPress Templates

Let's get practical. Here's how to take a professionally designed HTML page and integrate it seamlessly into WordPress as a custom template:

Step 1: Prepare Your HTML Page

Start with your standalone HTML file. For this example, let's say it's called homepage.html:

homepage.html

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>My Amazing Website</title>
    <link rel="stylesheet" href="styles.css">
</head>
<body>
    <header class="site-header">
        <nav class="main-nav">
            <a href="/">Home</a>
            <a href="/about">About</a>
            <a href="/services">Services</a>
        </nav>
    </header>

    <main class="content">
        <h1>Welcome to My Site</h1>
        <p>This is placeholder content...</p>
    </main>

    <footer class="site-footer">
        <p>© 2026 My Company</p>
    </footer>
</body>
</html>

Step 2: Split Into Header, Content, and Footer

WordPress uses three template files for the layout:

header.php — Everything from <html> to closing </header>
page.php — Your page/post content (or custom template)
footer.php — Everything after main content to </html>

wp-content/themes/your-theme/header.php

<?php
/**
 * The header for our theme
 */
?>
<!DOCTYPE html>
<html <?php language_attributes(); ?>>
<head>
    <meta charset="<?php bloginfo( 'charset' ); ?>">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title><?php wp_title(); ?></title>
    <?php wp_head(); ?>
</head>
<body <?php body_class(); ?>>
    <header class="site-header">
        <nav class="main-nav">
            <?php
                wp_nav_menu( array(
                    'theme_location' => 'primary',
                    'fallback_cb'    => 'wp_page_menu',
                ) );
            ?>
        </nav>
    </header>

    <main id="main-content" class="main-content">

wp-content/themes/your-theme/footer.php

    </main>

    <footer class="site-footer">
        <p>© <?php echo date( 'Y' ); ?> <?php bloginfo( 'name' ); ?></p>
    </footer>

    <?php wp_footer(); ?>
</body>
</html>

Step 3: Create Your Custom Page Template

For your homepage or any custom page, create a template file:

wp-content/themes/your-theme/page-homepage.php

<?php
/**
 * Template Name: Custom Homepage
 * Description: Our custom vibe-coded homepage
 */

get_header();
?>

<div class="homepage-hero">
    <h1><?php the_title(); ?></h1>
    <?php the_content(); ?>
</div>

<?php
// Query recent posts from a custom post type
$args = array(
    'post_type'      => 'post',
    'posts_per_page' => 3,
    'orderby'        => 'date',
    'order'          => 'DESC',
);

$query = new WP_Query( $args );

if ( $query->have_posts() ) : ?>
    <section class="recent-posts">
        <h2>Latest Updates</h2>
        <div class="posts-grid">
            <?php
            while ( $query->have_posts() ) {
                $query->the_post();
                ?>
                <article class="post-card">
                    <h3><?php the_title(); ?></h3>
                    <div class="post-meta">
                        <?php echo get_the_date( 'F j, Y' ); ?>
                    </div>
                    <div class="post-excerpt">
                        <?php the_excerpt(); ?>
                    </div>
                    <a href="<?php the_permalink(); ?>" class="read-more">Read More →</a>
                </article>
                <?php
            }
            ?>
        </div>
    </section>
    <?php
endif;

wp_reset_postdata();

get_footer();
?>

Step 4: Assign Template to a Page

In the WordPress admin:

Create a new page or edit an existing one
Look for the "Template" dropdown on the right panel
Select "Custom Homepage"
Publish/Update

WordPress will now render that page using your page-homepage.php template. Your design, your code, WordPress's power.

Step 5: Style with Your Own CSS

Add your custom styles to style.css in your theme root. WordPress automatically loads it:

wp-content/themes/your-theme/style.css

/*
Theme Name: Custom Theme
Theme URI: https://example.com
Author: Your Name
Description: Custom vibe-coded theme
Version: 1.0
*/

/* Your custom styles */
.homepage-hero {
    padding: 60px 20px;
    background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);
    color: white;
    text-align: center;
}

.posts-grid {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(300px, 1fr));
    gap: 30px;
    margin-top: 40px;
}

.post-card {
    background: white;
    padding: 25px;
    border-radius: 8px;
    box-shadow: 0 2px 8px rgba(0,0,0,0.1);
    transition: transform 0.3s;
}

.post-card:hover {
    transform: translateY(-5px);
}

/* Add all your custom styles here */

Step 6: Add Custom PHP for Dynamic Features

Need something interactive? You have full PHP at your disposal:

Adding Contact Form Processing

<?php
// Handle form submission
if ( $_SERVER['REQUEST_METHOD'] === 'POST' && isset( $_POST['contact-nonce'] ) ) {
    if ( wp_verify_nonce( $_POST['contact-nonce'], 'contact-form' ) ) {
        $email = sanitize_email( $_POST['email'] );
        $message = sanitize_textarea_field( $_POST['message'] );

        wp_mail(
            get_option( 'admin_email' ),
            'New Contact Form Submission',
            $message . '\n\nFrom: ' . $email
        );

        echo '<div class="success-message">Message sent!</div>';
    }
}
?>

<form method="POST" class="contact-form">
    <?php wp_nonce_field( 'contact-form', 'contact-nonce' ); ?>

    <label for="email">Email:</label>
    <input type="email" name="email" required>

    <label for="message">Message:</label>
    <textarea name="message" required></textarea>

    <button type="submit">Send</button>
</form>

Pro Tip: Use wp_enqueue_script() and wp_enqueue_style() in your theme's functions.php to properly load JavaScript and CSS. This prevents conflicts and keeps WordPress happy:

functions.php snippet

<?php
function my_theme_enqueue_assets() {
    wp_enqueue_style( 'main-styles', get_stylesheet_uri() );
    wp_enqueue_script( 'main-script', get_template_directory_uri() . '/js/main.js', array(), '1.0', true );
}
add_action( 'wp_enqueue_scripts', 'my_theme_enqueue_assets' );
?>

Why This Approach Wins (For You AND Your Clients)

HTML/CSS Design

→

WordPress Theme

→

Custom Admin

→

Happy Client

For You (The Developer):

Fast delivery: Build faster because you're not rebuilding core systems
Real code: Write PHP, JavaScript, CSS with zero limitations
Professional rates: Charge premium because you're solving real business problems
Easy maintenance: WordPress handles updates; you handle features
Scalable toolkit: Reuse your theme approach for 10, 50, 100 client projects

For Your Clients:

Content control: Manage pages, posts, images, users themselves
Full feature library: Access 61,000+ plugins whenever they need functionality
Real support community: WordPress has 10+ million developers; answers for everything
Lower ongoing costs: No need to hire you for every small change
Future-proof: WordPress won't vanish; they can hire anyone to maintain it

The Numbers: Why This Matters

10M+

WordPress developers worldwide — someone will know your code

40%

Average time savings using WordPress + vibe coding vs. custom build

5-10x

More clients you can handle with same time investment

100%

Development freedom — full PHP, JS, CSS control

Common Concerns (And Why They Don't Hold Up)

"Isn't WordPress just for bloggers?"

Not even close. WordPress powers Fortune 500 company websites, complex SaaS platforms, e-commerce shops doing millions in revenue, membership sites, and apps with custom functionality that rivals anything built from scratch. The Economist, Sony Music, Microsoft News, and Mercedes-Benz all run WordPress.

"Won't my design look like every other WordPress site?"

Only if you use pre-built themes. When you're vibe coding, you control 100% of the HTML/CSS. Your site will look exactly like a custom build — because it is a custom build. You just have WordPress handling the hard parts invisibly.

"What if the client outgrows WordPress?"

With 43% of the web on WordPress, they won't outgrow it. But if they do, you can migrate. Your content, users, and data are all portable. Compare that to a custom Next.js app where everything is tied to your architecture.

"Isn't it harder to hire developers who know WordPress?"

WordPress has 10 million developers. That's not "harder." That's easier than finding someone fluent in your custom stack. Plus, any solid PHP developer can learn your approach in an afternoon.

💡 Real Talk: The best developers don't choose based on the platform. They choose based on client outcomes and their own velocity. WordPress + vibe coding delivers both. You finish projects faster, charge more, keep clients happier, and sleep better knowing their site will work for years.

Your Next Move

Here's what separates the $50/hr WordPress developers from the $150+/hr developers building custom solutions for agencies:

They stopped fighting WordPress. They started leveraging it.

Stop rebuilding contact forms, user management, content editors, and backup systems. Start building the features that actually matter — the stuff that makes clients' businesses better.

Stop positioning yourself as "the WordPress person." Start positioning yourself as "the developer who delivers fast, custom websites that clients can actually manage."

That's vibe coding. That's where the money is. That's where the satisfaction is.

Ready to Master WordPress + Custom Code?

Join the developers who are combining WordPress reliability with custom code freedom. Get your next project to launch in 40% less time while charging premium rates.

Start with one site using this approach. You'll see it immediately.

Seth @ SolarBlu.net
Web developer & entrepreneur building 6,000+ custom websites since 1996. I help freelancers and agencies do more with WordPress than they thought possible.

Learn about Child Themes →

Custom PHP Development

Building Faster, Better Websites: Our Rapid Development Template System

solarbluseth / September 14, 2026

Building Faster, Better Websites: Our Rapid Development Template System

We just cracked something we've been working toward for months — a repeatable, scalable system for building WordPress websites faster without sacrificing quality. Today, I want to share what we learned and how it's changing how we approach web design projects.

The Problem We Solved

Every custom WordPress site we build has the same core sections: a hero banner, an about section, a team roster, a location/contact area, maybe an FAQ. But every time we started a new project, we were essentially building these sections from scratch. Sure, we had standards. Yes, our code was clean. But we were recreating the wheel on every project.

We needed a way to go faster without cutting corners.

The Discovery: Elementor v0.4 JSON

A few days ago, we dove deep into Elementor's JSON import format (v0.4). The goal was simple: create templates we could import directly into WordPress instead of rebuilding components every time.

What we found was more valuable than a quick templating solution. We discovered exact specifications for how Elementor structures components, and more importantly, we learned how to build sections that are:

Validation-compliant — No import errors, just clean imports
Responsive by default — Desktop → tablet → mobile, properly tested
CSS-organized — Namespaced styles that don't conflict
Reusable — Drop into any WordPress site without modification

What We Built: Five Base Section Templates

Over the last day, we created five production-ready section templates:

1. Homepage/Resource Hub

Hero banner, resource grid (home repair, insurance, fiber internet, automotive), testimonials, events, rental properties, and footer. One complete homepage you can customize.

2. Team Section

Six-member team grid with headshots, names, positions, and bios. Responsive 3-column layout that stacks to 1 column on mobile. Professional hover effects included.

3. About Us Section

Company logo, image placeholder, multi-paragraph description, and four highlight cards. Two-column layout that adapts beautifully at every breakpoint.

4. Location & Directions

Embedded map (currently using a placeholder for screenshots), contact information, phone number (with tel: links), hours of operation, and a "Get Directions" button. All responsive.

5. FAQ/Accordion

Five questions with expanding answers, styled consistently with the rest of your site. JavaScript toggle function built in, no external dependencies needed.

Why This Changes Everything

Speed: What took 4-6 weeks for a new custom WordPress site now has a solid 2-week foundation. The sections are done, tested, and responsive. Your team focuses on customization and content, not recreating layouts.

Consistency: Every site using these templates maintains the same design language, responsive breakpoints, typography, and color system. Your brand looks cohesive across all projects.

Quality: These sections were built against strict Elementor v0.4 specifications. No import errors, no hidden bugs waiting in production. They're tested and documented.

Scalability: As we add more templates (services grid, pricing tables, testimonials carousel, etc.), every new project gets access to a growing library of battle-tested components.

The Technical Foundation

Each template uses a single-widget pattern with embedded CSS and HTML. Here's what that means:

No complexity bloat — One self-contained widget per section
Easy version control — JSON files are small and clear
CSS namespacing — .rhub, .ts, .ab, .lm, .faq classes keep styles isolated
Consistent breakpoints — Mobile at 600px, tablet at 900px, desktop at full width
Color system — Unified palette across all sections (#1f1f1f primary, #2c3e50 accent, etc.)

What This Means for Our Clients

When you hire us for a custom WordPress site now, you're getting:

Faster delivery — We can launch quality websites in weeks, not months
Proven components — These sections have been tested and documented
Easy updates — Since templates are documented, your team (or our team) can make changes confidently
Built-in responsiveness — Every section works perfectly on phone, tablet, and desktop
Professional results — Consistent design, smooth interactions, clean code

What's Next

We're documenting everything. Our v5 Elementor Template Guide includes:

The exact structure and validation rules we discovered
Best practices for responsive design
A step-by-step guide for creating new sections
All five templates with full documentation

We're also expanding the library. The goal: a comprehensive template system that covers 80% of what a typical WordPress site needs, with customization handling the remaining 20%.

The Bigger Picture

This is what we call rapid development — the ability to build fast without sacrificing quality, consistency, or professionalism. It's the difference between delivering a good website in 2 weeks versus a great website in 6.

For us, it means we can take on more projects, deliver faster, and give our clients the confidence that their WordPress site was built to high standards. For you as a potential client, it means getting a custom WordPress website that's both fast to build and built to last.

Want a custom WordPress site built with our rapid development system? We can build your site faster than you'd expect, with quality you can count on.

Interested in the technical details? We've documented everything in our Elementor v0.4 Template Guide.

Built with rapid development principles at SolarBlu.net