Yipper Posted 4 hours ago Share Posted 4 hours ago Hi everyone, I just started using ProcessWire this weekend and try to get an overview over everything. I'm a bit confused about output strategies and markup regions, because I saw a lot of different approaches and couldn't really tell which the current recommended one is. Somehow I ended up like this: _main.php <body class=""> <!-- Header --> <?php include "_header.php"; ?> <!-- Navigation --> <?php include "_navigation.php"; ?> <!-- Main --> <main class=""> <?= $content ?> </main> <!-- Footer --> <?php include "_footer.php"; ?> </body> _header.php - ..and on the other layout _*.php files, just using HTML inline php like this: <header class=""> <a href="<?= $home->url; ?>"> </a> </header 1-home.php for the home page template 2-about.php for an about page template - numbered for better overview - using $content .="" for markup regions <?php namespace ProcessWire; $content .= "<h1 class=''>{$page->title}</h1>"; $content .= "<div class=''>{$page->introduction}</div>"; 1. Can you please tell me if this is a good way (in late 2024) to structure templates? 2. A problem that I have with the $content .="" approach is that code highlighting and automatic code formatting doesn't really work in VS Code for me then (could be a setup problem). Thanks in advance for tips and best practices Link to comment Share on other sites More sharing options...
bernhard Posted 1 hour ago Share Posted 1 hour ago Hello and welcome to processwire! The short answer is there is no recommended way. Processwire leaves that completely open to the user. Some like markup regions, I don't. Some use template engines like latte or twig, others don't. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now