基于Core PHP+Bootstrap的项目从常规编码转模板化设计咨询

Hey there! I get exactly where you're coming from—maintaining mixed PHP/HTML code while handling custom client designs is a total headache. The good news is you don't need to dive into heavy frameworks like Laravel or CodeIgniter to fix this. Let's walk through a simple, template-based approach using just Core PHP (which you already know) to separate your business logic from your HTML.

Step 1: Restructure Your Project Folder #

First, organize your files to clearly separate logic, templates, and static assets. Here's a clean structure to start with:

• app/: Store all your business logic (database queries, form processing, calculations—no HTML here!)
• templates/: Hold all your HTML templates. Split this into subfolders for reusability:
  • templates/layouts/: For shared components like headers, footers, and base page structures
  • templates/pages/: For page-specific content (product pages, checkout, etc.)
  • templates/clients/: Optional, but perfect for storing custom designs per client (e.g., templates/clients/client_a/)
• public/: Static assets (Bootstrap files, custom CSS/JS, images)
• index.php: Your single entry point (routes requests to the right logic and templates)

Step 2: Build a Simple Template Loader Function #

Create a tiny, reusable function to load templates and pass data into them—this is your "mini template engine" that avoids mixed PHP/HTML chaos. Add this to a file like app/helpers.php:

<?php
// app/helpers.php
function load_template($template_path, $data = []) {
    // Extract array keys into variables (so $data['product_name'] becomes $product_name in the template)
    extract($data);
    
    // Start output buffering to capture the template content
    ob_start();
    // Load the template file (adjust the path based on your folder structure)
    include __DIR__ . '/../templates/' . $template_path . '.php';
    // Get the captured content and clean the buffer
    $content = ob_get_clean();
    
    return $content;
}

// Add a helper to safely escape output (prevents XSS attacks)
function e($value) {
    return htmlspecialchars($value, ENT_QUOTES, 'UTF-8');
}
?>

Step 3: Create Reusable Layouts #

Layouts let you avoid repeating header/footer code across every page. For example, make templates/layouts/main.php:

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title><?= e($page_title) ?></title>
    <!-- Load Bootstrap from your public folder -->
    <link rel="stylesheet" href="/public/bootstrap/css/bootstrap.min.css">
    <!-- Optional: Load client-specific CSS if needed -->
    <?php if(isset($client_css)): ?>
        <link rel="stylesheet" href="/public/css/<?= e($client_css) ?>">
    <?php endif; ?>
</head>
<body>
    <!-- Shared Header -->
    <nav class="navbar navbar-expand-lg navbar-dark bg-dark">
        <div class="container">
            <a class="navbar-brand" href="/">Your Script Name</a>
        </div>
    </nav>

    <!-- Page-Specific Content (Inserted here) -->
    <main class="container mt-4">
        <?= $content ?>
    </main>

    <!-- Shared Footer -->
    <footer class="bg-light py-3 mt-5">
        <div class="container text-center">
            <p>&copy; <?= date('Y') ?> Your Business Name</p>
        </div>
    </footer>

    <script src="/public/bootstrap/js/bootstrap.bundle.min.js"></script>
</body>
</html>

Step 4: Write Page-Specific Templates #

Now create templates for your actual pages—no business logic, just HTML with variables. For example, templates/pages/product.php:

<div class="row">
    <div class="col-md-8">
        <h1><?= e($product_name) ?></h1>
        <p class="lead"><?= e($product_description) ?></p>
        <ul class="list-group mt-3">
            <?php foreach($product_features as $feature): ?>
                <li class="list-group-item"><?= e($feature) ?></li>
            <?php endforeach; ?>
        </ul>
    </div>
    <div class="col-md-4">
        <div class="card">
            <div class="card-body">
                <h5 class="card-title">Price: $<?= number_format($product_price, 2) ?></h5>
                <a href="/checkout" class="btn btn-primary w-100">Buy Now</a>
            </div>
        </div>
    </div>
</div>

Step 5: Tie It All Together in Your Entry Point #

Use index.php to handle requests, run your business logic, and load the right templates:

<?php
// index.php
// Include your helper functions
require __DIR__ . '/app/helpers.php';

// Example: Fetch product data (this would live in app/product.php in a real setup)
$product_data = [
    'product_name' => 'Customizable Core PHP Script',
    'product_description' => 'A fully functional script tailored to your needs',
    'product_price' => 99.99,
    'product_features' => ['Custom Design Support', 'Core PHP Base', 'Bootstrap Ready']
];

// Load the page template with product data
$page_content = load_template('pages/product', $product_data);

// Load the main layout, passing the page content and page title
echo load_template('layouts/main', [
    'page_title' => 'Our Premium Script',
    'content' => $page_content
]);
?>

Step 6: Handle Custom Client Designs #

For clients who need unique designs, simply duplicate your template folder structure under templates/clients/client_name/, adjust the HTML/CSS, and modify the template loader to point to their folder. For example:

// In index.php, add a client parameter (could come from a subdomain, URL parameter, etc.)
$client = 'client_a'; // This could be dynamic based on who's accessing the site

// Load the client's page template instead of the default
$page_content = load_template("clients/{$client}/pages/product", $product_data);

Key Rules to Stick To #

• No business logic in templates: Keep database queries, calculations, and form processing strictly in the app/ folder. Templates should only handle display.
• Always escape output: Use the e() helper for all dynamic text to prevent XSS attacks.
• Keep templates clean: Limit PHP in templates to loops, conditionals, and variable outputs—nothing complex.

This approach leverages skills you already have, keeps your code maintainable, and makes custom client designs a breeze (you just swap template files instead of digging through mixed PHP/HTML).

内容的提问来源于stack exchange，提问作者Apple Bux