Question

I am creating my portfolio site and I am wanting to include the head section as a php include on my page. Reason being is because the site will have a fair few pages and I will want to make changes later on to things later on like tidying up the css files.

For example;

<head>
    <?php include('head.php'); ?>
</head>

as opposed to all this below being shown on each and every page:

    <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
    <title></title>
    <meta name="description" content="">
    <meta name="viewport" content="width=device-width">

    <link rel="stylesheet" href="css/normalize.css">
    <link rel="stylesheet" href="css/main.css">
    <link rel="stylesheet" href="css/1140.css">
    <link rel="stylesheet" href="css/ie.css">
    <script src="js/vendor/modernizr-2.6.1.min.js"></script>
</head>

I just didn't know if this was good practice to do, as with this being my portfolio site, I need the code to be correct from the start also as they will probably look into the standard of it also.

What are your opinions and advice people? Thanks.

Was it helpful?

Solution

Yep, it's quite standard. But instead of writing:

<head>
    <?php include('head.php'); ?>
</head>

you should put the tags inside head.php. I say it's better because what's inside head.php has no sense without the head tags, so they are kinda linked together. It's good practice to join things so linked into a single file without having to repeat open and close head tags for each page.

Actually, it's even good practice (and commonly used) to have header.php, body.php and footer.php files that has respectively:

header.php

<html>
<head>
...
</head>
<body>

body.php

...

footer.php

</body>
</html>

OTHER TIPS

I'm doing that in my application but I've found that it's not a good idea, because you have many of your stylesheets, javascripts, etc in a php file including the head section and you'll have problems with including it in php files in nested folders. this problem is because of relative paths. If you can use absolute paths then it's ok otherwise it's not a good idea ...

PHP Includes are used like this all the time. Any time that you have content that will be the exact same on every page, it is very helpful to use an include

This is an old topic but I use

    <?php include_once("phpinclude/head.txt"); ?>

phpinclude is it's own folder and I keep the footer, header, and common place info in that folder. .js, and .css has it's own as well.

Edit: I use require now. I would rather have a code fail and die rather than give some random string. They are the same except one dies and the other will print out an error or random code. This is for people learning PHP, not old heads.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top