{"id":13944,"date":"2015-04-06T05:02:43","date_gmt":"2015-04-05T19:02:43","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=13944"},"modified":"2015-04-06T05:02:43","modified_gmt":"2015-04-05T19:02:43","slug":"css-body-border-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/css-body-border-primer-tutorial\/","title":{"rendered":"CSS Body Border Primer Tutorial"},"content":{"rendered":"
\"CSS<\/a>

CSS Body Border Primer Tutorial<\/p><\/div>\n

The CSS we show today, thanks in huge part to the excellent advice of this wonderful link<\/a>, is both about putting a border around the body<\/i> of a web page (even though we never, once, refer to the “body” element as such) and also an exercise in conditional CSS.<\/p>\n

So what is “conditional CSS”? We talk about it here as the way in CSS you can differentiate between the mobile platforms and the non-mobile platforms, and in today’s case, also, the difference between Internet Explorer versions before 6, and the rest. Life in the CSS world can be quite complex if you try to cater for lots of platforms, but the Internet and the search engines are here to help … we got onto our useful link via the Google search …<\/p>\n

\nhttps:\/\/www.google.com.au\/?gfe_rd=cr&ei=R0ogVe7WA83u8wf064HYDg&gws_rd=ssl#q=%22warm+glowing+body+border%22+css<\/a>\n<\/p><\/blockquote>\n

Today we show the basic CSS work involved, and tomorrow we show some once a day Linux Crontab Curl “smarts” for a bit of variety regarding this (with CSS Body Border Linux Crontab Curl Tutorial<\/a>), which involves the use of external CSS files, via the header.php changes (number 1 below) outlined below being reduced to the simple (between <head> and <\/head>) …
\n
\n<link rel='stylesheet' type='text\/css' href='\/\/www.rjmprogramming.com.au\/HTMLCSS\/body_border.css' \/>
\n<\/code><\/p>\n

So let’s look at how the WordPress “good ‘ol” header.php changed for this, in its first principles, in bold<\/b> as two sections …<\/p>\n

    \n
  1. … around the “style” bits (and like it says, thanks to this very useful link<\/a>) …
    \n
    \n<style>
    \n
    \n#btop, #bbottom, #bleft, #bright { \/* thanks to https:\/\/css-tricks.com\/body-border\/ *\/
    \n\tbackground: gold; \/* #a5ebff; *\/
    \n\tposition: fixed;
    \n\t}
    \n\t#bleft, #bright {
    \n\t\ttop: 0; bottom: 0;
    \n\t\twidth: 5px; \/* 15px; *\/
    \n\t\t}
    \n\t\t#bleft { left: 0; }
    \n\t\t#bright { right: 0; }
    \n\t#btop, #bbottom {
    \n\t\tleft: 0; right: 0;
    \n\t\theight: 5px; \/* 15px; *\/
    \n\t\t}
    \n\t\t#btop { top: 0; }
    \n\t\t#bbottom { bottom: 0; }
    \n<\/style>
    \n<!--[if lte IE 6]>
    \n\t<style>#btop, #bbottom, #bleft, #bright { display: none; }<\/style>
    \n<![endif]-->
    \n<style>
    \n@media
    \n\/* Fairly small screens including iphones *\/
    \nonly screen and (max-width: 500px),
    \n\/* iPads *\/
    \nonly screen and (min-device-width: 768px) and (max-device-width: 1024px)
    \n{
    \n\t#btop, #bbottom, #bleft, #bright { display: none; }
    \n}
    \n<\/b>
    \n\/* ... *\/
    \n\/* ... *\/
    \n\/* ... *\/
    \n\/* ... *\/
    \n<\/style>
    \n<\/code>\n<\/li>\n
  2. … at the end …
    \n
    \n\t<\/div><!-- #header -->
    \n
    \n<div id=\"bleft\"><\/div>
    \n<div id=\"bright\"><\/div>
    \n<div id=\"btop\"><\/div>
    \n<div id=\"bbottom\"><\/div>
    \n<\/b>
    \n\t<div id=\"main\">
    \n<\/code>\n<\/li>\n<\/ol>\n

    Maybe you can try the leads that these ideas could give you regarding a small “makeover” to your webpages.<\/p>\n

    Did you know?<\/i><\/b><\/p>\n

    The investigations and analysis of HTML required by this “DIY” HTML\/CSS were facilitated by the use of the Firefox<\/a> web browser and a very useful add-on called Firebug<\/a> which you may want more information about here<\/a>, and which is commonly used to debug client-side Javascript and HTML. As for today’s usage, Firebug is also extremely useful in deconstructing how a web page was created. The other simple wonderful tool for this is the web browser’s equivalent menu command like View->Page Source (or sometimes equivalent of right-click Page Source). Firebug has a sister product called FirePHP<\/a> which helps debug server-side PHP and Ajax work<\/a>. Please don’t mind me … am sold on Firebug with Firefox, but there are many alternatives (eg. Safari and Inspector (built into Safari) via Develop->Show Web Inspector) … and there are others (with other web browsers).<\/p>\n

    If this was interesting you may be interested in this<\/a> too.<\/p>\n