Organizing a PHP Project with a Simple Folder Structure

A clear project layout keeps public entry points separate from source, configuration and tests.

What It Does and When to Use It

Separate business logic, input handling and rendering at a clearly identified boundary. Direct PHP code exposes the underlying operation clearly; a framework can supply lifecycle hooks, dependency wiring and retries.

Requirements, Inputs and Expected Behavior

Confirm the runtime, extension, environment variables, and permissions before running the examples in production. Never put .env, Composer cache, or untrusted uploads inside public root.

Example 1: Basic Operation

Separate business logic, input handling and rendering at a clearly identified boundary.

<?php
$folders=['public','src/Controller','src/Service','templates','tests','config'];
foreach ($folders as $directory) echo $directory, PHP_EOL;

Example 2: Behavior and Validation

Use the front controller to select responses while keeping routing separate from models.

<?php
$path=parse_url($_SERVER['REQUEST_URI']??'/',PHP_URL_PATH);
if ($path==='/health') { header('Content-Type: application/json'); echo json_encode(['status'=>'ok']); }
else { http_response_code(404); echo 'Not found'; }

Practical Example: Application Use

Render a trusted template path with controlled data; never derive template paths from user input.

<?php
function render(string $template, array $data): string {
    extract($data, EXTR_SKIP); ob_start();
    try { require $template; return (string)ob_get_clean(); }
    catch(Throwable $e) { ob_end_clean(); throw $e; }
}

Important Behavior and Edge Cases

The second example highlights: Use the front controller to select responses while keeping routing separate from models. The practical example adds: Render a trusted template path with controlled data; never derive template paths from user input.

Comparison with Related Approaches

Common Beginner Mistakes

Key Takeaways

• A clear project layout keeps public entry points separate from source, configuration and tests.
• Render a trusted template path with controlled data; never derive template paths from user input.
• Choose based on deployment requirements and verify actual behavior rather than assuming defaults.