<div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, null given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3601</p>

</div><div style="border:1px solid #990000;padding-left:20px;margin:0 0 10px 0;">

<h4>A PHP Error was encountered</h4>

<p>Severity: 4096</p>
<p>Message:  Argument 1 passed to DOMNode::appendChild() must be an instance of DOMNode, string given, called in /mnt/local/home/sbre/ooyes.net/system2/application/controllers/rss.php on line 27 and defined</p>
<p>Filename: models/content_model.php</p>
<p>Line Number: 3579</p>

</div><?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:g="http://base.google.com/ns/1.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Website design - Blog</title>
    <webMaster>info@ooyes.net (Website design)</webMaster>
    <generator>Content Menagement System Ooyes CMS (http://www.ooyes.net)</generator>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <lastBuildDate>Wed, 20 Aug 2008 01:06:36 -0700</lastBuildDate>
    <ttl>60</ttl>
    <managingEditor>info@ooyes.net (Website design)</managingEditor>
    <copyright>Copyright OOYES.NET - MASS MEDIA GROUP LTD</copyright>
    <description>Web Design and outsourcing company, tutorials and resources - Blog</description>
    <link>http://ooyes.net/</link>
    <atom:link href="http://ooyes.net/rss/feed/71/blog" rel="self" type="application/rss+xml"/>
    <item>
      <title>Studio Hybrid</title>
      <author>info@ooyes.net (Website design)</author>
      <description>More flexible than a typical PC, the Dell Studio Hybrid is an anywhere-you-want-it-desktop. Our smallest desktop, it looks great in the living room, on the desk, or anywhere else space is at a premium. </description>
      <content:encoded>More flexible than a typical PC, the Dell Studio Hybrid is an anywhere-you-want-it-desktop. Our smallest desktop, it looks great in the living room, on the desk, or anywhere else space is at a premium. </content:encoded>
      <pubDate>Thu, 14 Aug 2008 06:34:19 -0700</pubDate>
      <link>http://ooyes.net/studio-hybrid</link>
      <guid isPermaLink="true">http://ooyes.net/studio-hybrid</guid>
    </item>
    <item>
      <title>Design of the homepage</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Designing a homepage is an exercise in discriminate puzzle solving. You have a list of possible
design elements, widgets, and marketing pieces that can eventually make an appearance.
Some are critical, others optional. All of them have a certain value.</description>
      <content:encoded>Designing a homepage is an exercise in discriminate puzzle solving. You have a list of possible
design elements, widgets, and marketing pieces that can eventually make an appearance.
Some are critical, others optional. All of them have a certain value.</content:encoded>
      <pubDate>Tue, 22 Jul 2008 05:21:59 -0700</pubDate>
      <link>http://ooyes.net/design-of-the-homepage</link>
      <guid isPermaLink="true">http://ooyes.net/design-of-the-homepage</guid>
    </item>
    <item>
      <title>Corporate Blog</title>
      <author>info@ooyes.net (Website design)</author>
      <description>For years, many modern businesses have recognized the value of communicating with
their customers about events, news, policy updates, changes in leadership, and other significant
happenings within their organization. In fact, some of that communication has
been made mandatory by law—any publicly traded company, for instance, is required to
provide quarterly financial information. Over the years, marketing and public relations
departments have seen the tremendous benefits of maintaining an open line of communication
with the public. On a basic level, this transparency builds customer trust, which
builds brand loyalty, which can be gasoline for the word-of-mouth marketing fire.</description>
      <content:encoded>For years, many modern businesses have recognized the value of communicating with
their customers about events, news, policy updates, changes in leadership, and other significant
happenings within their organization. In fact, some of that communication has
been made mandatory by law—any publicly traded company, for instance, is required to
provide quarterly financial information. Over the years, marketing and public relations
departments have seen the tremendous benefits of maintaining an open line of communication
with the public. On a basic level, this transparency builds customer trust, which
builds brand loyalty, which can be gasoline for the word-of-mouth marketing fire.</content:encoded>
      <pubDate>Tue, 22 Jul 2008 03:24:04 -0700</pubDate>
      <link>http://ooyes.net/corporate-blog</link>
      <guid isPermaLink="true">http://ooyes.net/corporate-blog</guid>
    </item>
    <item>
      <title>Web Site Marketing</title>
      <author>info@ooyes.net (Website design)</author>
      <description>No business can survive without marketing. Not my business. Not your
business. Marketing brings in clients. And clients bring in the money that keeps
your business alive.
As Webmasters, we sharpen our design skills constantly and try to keep up with
new developments in the field -- trends, new tools, etc. However, for many of us,
our understanding of marketing theory is less refined.</description>
      <content:encoded>No business can survive without marketing. Not my business. Not your
business. Marketing brings in clients. And clients bring in the money that keeps
your business alive.
As Webmasters, we sharpen our design skills constantly and try to keep up with
new developments in the field -- trends, new tools, etc. However, for many of us,
our understanding of marketing theory is less refined.</content:encoded>
      <pubDate>Tue, 22 Jul 2008 03:08:08 -0700</pubDate>
      <link>http://ooyes.net/web-site-marketing</link>
      <guid isPermaLink="true">http://ooyes.net/web-site-marketing</guid>
    </item>
    <item>
      <title>Website Desgn - The User Test</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The whole point of user testing is to catch the usability problems of your
design before you go into production. Therefore, you must be mentally prepared
for the feedback that comes out — it may not be pretty. In some cases,
you may be faced with a substantial redesign if user after user can’t figure
out your interface.</description>
      <content:encoded>The whole point of user testing is to catch the usability problems of your
design before you go into production. Therefore, you must be mentally prepared
for the feedback that comes out — it may not be pretty. In some cases,
you may be faced with a substantial redesign if user after user can’t figure
out your interface.</content:encoded>
      <pubDate>Mon, 21 Jul 2008 01:06:34 -0700</pubDate>
      <link>http://ooyes.net/website-desgn-the-user-test</link>
      <guid isPermaLink="true">http://ooyes.net/website-desgn-the-user-test</guid>
    </item>
    <item>
      <title>Website design - Asymmetrical Balance</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Asymmetrical balance, or informal balance, is a little more abstract, and generally more
visually interesting, than symmetrical balance. Rather than having mirror images on either
side of the layout, asymmetrical balance involves objects of differing size, shape, tone, or
placement. These objects are arranged so that, despite their differences, they equalize the
weight of the page. If you have a large object on one side of a page, and you partner it with
several smaller items on the other side, the composition can still feel balanced.</description>
      <content:encoded>Asymmetrical balance, or informal balance, is a little more abstract, and generally more
visually interesting, than symmetrical balance. Rather than having mirror images on either
side of the layout, asymmetrical balance involves objects of differing size, shape, tone, or
placement. These objects are arranged so that, despite their differences, they equalize the
weight of the page. If you have a large object on one side of a page, and you partner it with
several smaller items on the other side, the composition can still feel balanced.</content:encoded>
      <pubDate>Thu, 10 Jul 2008 01:53:41 -0700</pubDate>
      <link>http://ooyes.net/website-design-asymmetrical-balance</link>
      <guid isPermaLink="true">http://ooyes.net/website-design-asymmetrical-balance</guid>
    </item>
    <item>
      <title>Website Design - Designing For Success</title>
      <author>info@ooyes.net (Website design)</author>
      <description>When inexperienced designers start a Web site design, they typically begin by
laying out the major functional blocks of the home page or by doing a color and
graphic layout. But designing a site is just the same as building a house. You have to start with
the foundation and work up.</description>
      <content:encoded>When inexperienced designers start a Web site design, they typically begin by
laying out the major functional blocks of the home page or by doing a color and
graphic layout. But designing a site is just the same as building a house. You have to start with
the foundation and work up.</content:encoded>
      <pubDate>Thu, 10 Jul 2008 00:59:14 -0700</pubDate>
      <link>http://ooyes.net/website-design-designing-for-success</link>
      <guid isPermaLink="true">http://ooyes.net/website-design-designing-for-success</guid>
    </item>
    <item>
      <title>Web design - Web Site Marketing Secrets</title>
      <author>info@ooyes.net (Website design)</author>
      <description>No business can survive without marketing. Not my business. Not your
business. Marketing brings in clients. And clients bring in the money that keeps
your business alive. As Webmasters, we sharpen our design skills constantly and try to keep up with
new developments in the field -- trends, new tools, etc. However, for many of us,
our understanding of marketing theory is less refined.</description>
      <content:encoded>No business can survive without marketing. Not my business. Not your
business. Marketing brings in clients. And clients bring in the money that keeps
your business alive. As Webmasters, we sharpen our design skills constantly and try to keep up with
new developments in the field -- trends, new tools, etc. However, for many of us,
our understanding of marketing theory is less refined.</content:encoded>
      <pubDate>Thu, 10 Jul 2008 00:50:03 -0700</pubDate>
      <link>http://ooyes.net/web-design-web-site-marketing-secrets</link>
      <guid isPermaLink="true">http://ooyes.net/web-design-web-site-marketing-secrets</guid>
    </item>
    <item>
      <title>Web Design - Creating Nice User Pathways</title>
      <author>info@ooyes.net (Website design)</author>
      <description>In terms of a Web site’s “flip factor,’’ auditing, wireframing, and prototyping all
lead us to the shaping of our site’s architecture and, ultimately, the site’s usability
and content design. We’re creating the interface between a site’s technical backend
and its welcoming front-end. If a book, which is a mostly linear medium, can
benefit from user pathways, so can aWeb site. What’smore, because different types
of people use navigation schemes and site entry points in different ways, creating
a variety of pathways to information is a necessity.</description>
      <content:encoded>In terms of a Web site’s “flip factor,’’ auditing, wireframing, and prototyping all
lead us to the shaping of our site’s architecture and, ultimately, the site’s usability
and content design. We’re creating the interface between a site’s technical backend
and its welcoming front-end. If a book, which is a mostly linear medium, can
benefit from user pathways, so can aWeb site. What’smore, because different types
of people use navigation schemes and site entry points in different ways, creating
a variety of pathways to information is a necessity.</content:encoded>
      <pubDate>Wed, 09 Jul 2008 07:06:17 -0700</pubDate>
      <link>http://ooyes.net/web-design-creating-nice-user-pathways</link>
      <guid isPermaLink="true">http://ooyes.net/web-design-creating-nice-user-pathways</guid>
    </item>
    <item>
      <title>Website design - Architecting Your Information</title>
      <author>info@ooyes.net (Website design)</author>
      <description>How information is designed both from a conceptual and technical standpoint
immediately impacts the short- and long-term evolution of a site.
Understanding what information is available, how to structure it in such a way
that makes sense both to the end-user and the behind-the-scenes interrelationship
of other documents within theWeb site, and managing growth effectively can
be extremely helpful in avoiding problems down the road.</description>
      <content:encoded>How information is designed both from a conceptual and technical standpoint
immediately impacts the short- and long-term evolution of a site.
Understanding what information is available, how to structure it in such a way
that makes sense both to the end-user and the behind-the-scenes interrelationship
of other documents within theWeb site, and managing growth effectively can
be extremely helpful in avoiding problems down the road.</content:encoded>
      <pubDate>Wed, 09 Jul 2008 06:37:54 -0700</pubDate>
      <link>http://ooyes.net/website-design-architecting-your-information</link>
      <guid isPermaLink="true">http://ooyes.net/website-design-architecting-your-information</guid>
    </item>
    <item>
      <title>Street Art</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Amazing Street Art</description>
      <content:encoded>Amazing Street Art</content:encoded>
      <pubDate>Wed, 09 Jul 2008 06:02:54 -0700</pubDate>
      <link>http://ooyes.net/street-art</link>
      <guid isPermaLink="true">http://ooyes.net/street-art</guid>
    </item>
    <item>
      <title>Preview of the First Rotating Skyscraper on the world</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The Dubai skyline will be constantly changing after plans for the world's first rotating tower were unveiled.</description>
      <content:encoded>The Dubai skyline will be constantly changing after plans for the world's first rotating tower were unveiled.</content:encoded>
      <pubDate>Fri, 27 Jun 2008 08:03:17 -0700</pubDate>
      <link>http://ooyes.net/preview-of-the-first-rotating-skyscraper-on-the-world</link>
      <guid isPermaLink="true">http://ooyes.net/preview-of-the-first-rotating-skyscraper-on-the-world</guid>
    </item>
    <item>
      <title>Funny motivational posters</title>
      <author>info@ooyes.net (Website design)</author>
      <description>A collection of motivation posters with a difference</description>
      <content:encoded>A collection of motivation posters with a difference</content:encoded>
      <pubDate>Fri, 27 Jun 2008 01:25:51 -0700</pubDate>
      <link>http://ooyes.net/funny-motivational-posters</link>
      <guid isPermaLink="true">http://ooyes.net/funny-motivational-posters</guid>
    </item>
    <item>
      <title>Wild animals by Nick Brent</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Wild animals by Nick Brent</description>
      <content:encoded>Wild animals by Nick Brent</content:encoded>
      <pubDate>Thu, 26 Jun 2008 03:47:39 -0700</pubDate>
      <link>http://ooyes.net/wild-animals-by-nick-brent</link>
      <guid isPermaLink="true">http://ooyes.net/wild-animals-by-nick-brent</guid>
    </item>
    <item>
      <title>Art Posters - Photography Design</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Art Posters - Photography Design</description>
      <content:encoded>Art Posters - Photography Design</content:encoded>
      <pubDate>Wed, 25 Jun 2008 05:23:07 -0700</pubDate>
      <link>http://ooyes.net/art-posters-photography-design</link>
      <guid isPermaLink="true">http://ooyes.net/art-posters-photography-design</guid>
    </item>
    <item>
      <title>Futuristic Car Design</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Futuristic Car Design</description>
      <content:encoded>Futuristic Car Design</content:encoded>
      <pubDate>Wed, 25 Jun 2008 04:48:17 -0700</pubDate>
      <link>http://ooyes.net/futuristic-car-design</link>
      <guid isPermaLink="true">http://ooyes.net/futuristic-car-design</guid>
    </item>
    <item>
      <title>Javascript Canvas - Cool Libraries</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Javascript Canvas - cool libraries, some of the best </description>
      <content:encoded>Javascript Canvas - cool libraries, some of the best </content:encoded>
      <pubDate>Tue, 24 Jun 2008 07:43:52 -0700</pubDate>
      <link>http://ooyes.net/javascript-canvas-cool-libraries</link>
      <guid isPermaLink="true">http://ooyes.net/javascript-canvas-cool-libraries</guid>
    </item>
    <item>
      <title>Funny Flash Game</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Funny Flash Game - Launch Hedgehog into space</description>
      <content:encoded>Funny Flash Game - Launch Hedgehog into space</content:encoded>
      <pubDate>Tue, 24 Jun 2008 02:12:08 -0700</pubDate>
      <link>http://ooyes.net/funny-flash-game</link>
      <guid isPermaLink="true">http://ooyes.net/funny-flash-game</guid>
    </item>
    <item>
      <title>Creative Photos</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Creative Photos</description>
      <content:encoded>Creative Photos</content:encoded>
      <pubDate>Mon, 23 Jun 2008 00:52:59 -0700</pubDate>
      <link>http://ooyes.net/creative-photos</link>
      <guid isPermaLink="true">http://ooyes.net/creative-photos</guid>
    </item>
    <item>
      <title>Who loves Pixar</title>
      <author>info@ooyes.net (Website design)</author>
      <description>A new video clip from Pixar’s WALL-E was shown during ABC’s airing of Finding Nemo. The scene involves Eve placing our favorite little trash compacting robot in a shuttle back to earth. But things aren’t as they first appear, and WALL-E ends up in explosive situation.</description>
      <content:encoded>A new video clip from Pixar’s WALL-E was shown during ABC’s airing of Finding Nemo. The scene involves Eve placing our favorite little trash compacting robot in a shuttle back to earth. But things aren’t as they first appear, and WALL-E ends up in explosive situation.</content:encoded>
      <pubDate>Fri, 20 Jun 2008 06:21:39 -0700</pubDate>
      <link>http://ooyes.net/who-loves-pixar</link>
      <guid isPermaLink="true">http://ooyes.net/who-loves-pixar</guid>
    </item>
    <item>
      <title>HTML Code - Stick To The Markup Style</title>
      <author>info@ooyes.net (Website design)</author>
      <description>One of the biggest headaches in managing the code side of Web design is the
variations that exist in how markup is formatted. I don’t mean how it will look on
display, but how the code itself is formatted behind the scenes.</description>
      <content:encoded>One of the biggest headaches in managing the code side of Web design is the
variations that exist in how markup is formatted. I don’t mean how it will look on
display, but how the code itself is formatted behind the scenes.</content:encoded>
      <pubDate>Fri, 20 Jun 2008 01:41:18 -0700</pubDate>
      <link>http://ooyes.net/html-code-stick-to-the-markup-style</link>
      <guid isPermaLink="true">http://ooyes.net/html-code-stick-to-the-markup-style</guid>
    </item>
    <item>
      <title>Web Project Management</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Project management is an art and soft science that has had hundreds—if not
thousands—of years to emerge. The process—whether it be for huge industrial
construction projects, humanitarian endeavors, or even the day-to-day management
and workflow of a fast-food restaurant—of managing a given task from
fruition through to completion has been undertaken hundreds of millions of
times.</description>
      <content:encoded>Project management is an art and soft science that has had hundreds—if not
thousands—of years to emerge. The process—whether it be for huge industrial
construction projects, humanitarian endeavors, or even the day-to-day management
and workflow of a fast-food restaurant—of managing a given task from
fruition through to completion has been undertaken hundreds of millions of
times.</content:encoded>
      <pubDate>Thu, 19 Jun 2008 08:25:44 -0700</pubDate>
      <link>http://ooyes.net/web-project-management</link>
      <guid isPermaLink="true">http://ooyes.net/web-project-management</guid>
    </item>
    <item>
      <title>DOM Inspectors Overview</title>
      <author>info@ooyes.net (Website design)</author>
      <description>DOM inspection is one of the most useful but underused tools available to a JavaScript developer.
DOM inspection can be thought of as an advanced version of viewing a page’s source
code, allowing you to see the current state of a page after your code has already modified its
contents.</description>
      <content:encoded>DOM inspection is one of the most useful but underused tools available to a JavaScript developer.
DOM inspection can be thought of as an advanced version of viewing a page’s source
code, allowing you to see the current state of a page after your code has already modified its
contents.</content:encoded>
      <pubDate>Thu, 19 Jun 2008 08:11:26 -0700</pubDate>
      <link>http://ooyes.net/dom-inspectors-overview</link>
      <guid isPermaLink="true">http://ooyes.net/dom-inspectors-overview</guid>
    </item>
    <item>
      <title>Prototype Library</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Prototype is a JavaScript library that was developed to work in conjunction with the popular
Ruby on Rails web framework.</description>
      <content:encoded>Prototype is a JavaScript library that was developed to work in conjunction with the popular
Ruby on Rails web framework.</content:encoded>
      <pubDate>Thu, 19 Jun 2008 07:50:24 -0700</pubDate>
      <link>http://ooyes.net/prototype-library</link>
      <guid isPermaLink="true">http://ooyes.net/prototype-library</guid>
    </item>
    <item>
      <title>Jquery Filtering Methods</title>
      <author>info@ooyes.net (Website design)</author>
      <description>These methods remove elements from the set matched by a jQuery object.</description>
      <content:encoded>These methods remove elements from the set matched by a jQuery object.</content:encoded>
      <pubDate>Thu, 19 Jun 2008 07:19:42 -0700</pubDate>
      <link>http://ooyes.net/jquery-filtering-methods</link>
      <guid isPermaLink="true">http://ooyes.net/jquery-filtering-methods</guid>
    </item>
    <item>
      <title>Jquery DOM Manipulation Methods</title>
      <author>info@ooyes.net (Website design)</author>
      <description>All of the methods in this chapter manipulate the DOM in some manner. A few of them simply change one of the attributes of an element, while others set an element's style properties. Still others modify entire elements (or groups of elements) themselves—inserting, copying, removing, and so on.</description>
      <content:encoded>All of the methods in this chapter manipulate the DOM in some manner. A few of them simply change one of the attributes of an element, while others set an element's style properties. Still others modify entire elements (or groups of elements) themselves—inserting, copying, removing, and so on.</content:encoded>
      <pubDate>Thu, 19 Jun 2008 06:56:11 -0700</pubDate>
      <link>http://ooyes.net/jquery-dom-manipulation-methods</link>
      <guid isPermaLink="true">http://ooyes.net/jquery-dom-manipulation-methods</guid>
    </item>
    <item>
      <title>Firefox 3</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Firefox 3 - overview, features, tips and tricks</description>
      <content:encoded>Firefox 3 - overview, features, tips and tricks</content:encoded>
      <pubDate>Thu, 19 Jun 2008 03:46:02 -0700</pubDate>
      <link>http://ooyes.net/firefox-3</link>
      <guid isPermaLink="true">http://ooyes.net/firefox-3</guid>
    </item>
    <item>
      <title>Funny Signs</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Funny Signs</description>
      <content:encoded>Funny Signs</content:encoded>
      <pubDate>Wed, 18 Jun 2008 04:09:04 -0700</pubDate>
      <link>http://ooyes.net/funny-signs</link>
      <guid isPermaLink="true">http://ooyes.net/funny-signs</guid>
    </item>
    <item>
      <title>CSS navigaton Lists</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Lists for navigation make sense, because navigation boils down to being a list of
links, no matter how it appears visually on the page.</description>
      <content:encoded>Lists for navigation make sense, because navigation boils down to being a list of
links, no matter how it appears visually on the page.</content:encoded>
      <pubDate>Tue, 17 Jun 2008 06:12:59 -0700</pubDate>
      <link>http://ooyes.net/css-navigaton-lists</link>
      <guid isPermaLink="true">http://ooyes.net/css-navigaton-lists</guid>
    </item>
    <item>
      <title>CSS Layout Basics </title>
      <author>info@ooyes.net (Website design)</author>
      <description>Several terms and concepts are referred to throughout this chapter, so it’s good to
let you know them up front</description>
      <content:encoded>Several terms and concepts are referred to throughout this chapter, so it’s good to
let you know them up front</content:encoded>
      <pubDate>Tue, 17 Jun 2008 05:13:21 -0700</pubDate>
      <link>http://ooyes.net/css-layout-basics</link>
      <guid isPermaLink="true">http://ooyes.net/css-layout-basics</guid>
    </item>
    <item>
      <title>CMS - Overview</title>
      <author>info@ooyes.net (Website design)</author>
      <description>CMS - Overview. Main things you need to know about the Content Management Systems and list of most famous of them.</description>
      <content:encoded>CMS - Overview. Main things you need to know about the Content Management Systems and list of most famous of them.</content:encoded>
      <pubDate>Mon, 16 Jun 2008 02:38:47 -0700</pubDate>
      <link>http://ooyes.net/cms-overview</link>
      <guid isPermaLink="true">http://ooyes.net/cms-overview</guid>
    </item>
    <item>
      <title>Creative Advertisements</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Creative Advertisements</description>
      <content:encoded>Creative Advertisements</content:encoded>
      <pubDate>Thu, 12 Jun 2008 07:15:06 -0700</pubDate>
      <link>http://ooyes.net/creative-advertisements</link>
      <guid isPermaLink="true">http://ooyes.net/creative-advertisements</guid>
    </item>
    <item>
      <title>SSI - Server Side Includes, Full Description</title>
      <author>info@ooyes.net (Website design)</author>
      <description>SSI (Server Side Includes) are directives that are placed in HTML pages, and evaluated on the server while the pages are being served. They let you add dynamically generated content to an existing HTML page, without having to serve the entire page via a CGI program, or other dynamic technology.</description>
      <content:encoded>SSI (Server Side Includes) are directives that are placed in HTML pages, and evaluated on the server while the pages are being served. They let you add dynamically generated content to an existing HTML page, without having to serve the entire page via a CGI program, or other dynamic technology.</content:encoded>
      <pubDate>Thu, 05 Jun 2008 00:58:53 -0700</pubDate>
      <link>http://ooyes.net/ssi-server-side-includes-full-description</link>
      <guid isPermaLink="true">http://ooyes.net/ssi-server-side-includes-full-description</guid>
    </item>
    <item>
      <title>Logo and Slogan Parodies</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Logo and Slogan Parodies</description>
      <content:encoded>Logo and Slogan Parodies</content:encoded>
      <pubDate>Mon, 02 Jun 2008 03:55:11 -0700</pubDate>
      <link>http://ooyes.net/logo-and-slogan-parodies</link>
      <guid isPermaLink="true">http://ooyes.net/logo-and-slogan-parodies</guid>
    </item>
    <item>
      <title>Bringing CSS and XHTML Together</title>
      <author>info@ooyes.net (Website design)</author>
      <description>I've mentioned that HTML and XHTML documents have an inherent structure, and that's a point worth repeating. In fact, that's part of the problem with web pages of old: too many of us forgot that documents are supposed to have an internal structure, which is altogether different than a visual structure. In our rush to create the coolest-looking pages on the Web, we bent, warped, and generally ignored the idea that pages should contain information with some structural meaning.</description>
      <content:encoded>I've mentioned that HTML and XHTML documents have an inherent structure, and that's a point worth repeating. In fact, that's part of the problem with web pages of old: too many of us forgot that documents are supposed to have an internal structure, which is altogether different than a visual structure. In our rush to create the coolest-looking pages on the Web, we bent, warped, and generally ignored the idea that pages should contain information with some structural meaning.</content:encoded>
      <pubDate>Mon, 02 Jun 2008 01:08:01 -0700</pubDate>
      <link>http://ooyes.net/bringing-css-and-xhtml-together</link>
      <guid isPermaLink="true">http://ooyes.net/bringing-css-and-xhtml-together</guid>
    </item>
    <item>
      <title>Javascript lightboxes</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Lightbox is a JavaScript application used to display large images using modal dialogs. Here i will describe list with the famous lightboxes</description>
      <content:encoded>Lightbox is a JavaScript application used to display large images using modal dialogs. Here i will describe list with the famous lightboxes</content:encoded>
      <pubDate>Fri, 30 May 2008 07:44:15 -0700</pubDate>
      <link>http://ooyes.net/javascript-lightboxes</link>
      <guid isPermaLink="true">http://ooyes.net/javascript-lightboxes</guid>
    </item>
    <item>
      <title>Javascript Tooltips. Some of the best tootips</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The tooltip is a common graphical user interface element. It is used in conjunction with a cursor, usually a mouse pointer. The user hovers the cursor over an item, without clicking it, and a small box appears with supplementary information regarding the item being hovered over.</description>
      <content:encoded>The tooltip is a common graphical user interface element. It is used in conjunction with a cursor, usually a mouse pointer. The user hovers the cursor over an item, without clicking it, and a small box appears with supplementary information regarding the item being hovered over.</content:encoded>
      <pubDate>Fri, 30 May 2008 05:09:09 -0700</pubDate>
      <link>http://ooyes.net/javascript-tooltips-some-of-the-best-tootips</link>
      <guid isPermaLink="true">http://ooyes.net/javascript-tooltips-some-of-the-best-tootips</guid>
    </item>
    <item>
      <title>Website Design for Long Term Success</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The World Wide Web is in fact a global environment, with many languages
as well as religions, customs, and ways of life. Creating visually stimulating
designs that work for your clients—no matter how near or far they might be
requires an understanding of a variety of practices: excellent Web graphic design
skills and an awareness of the psychology of color and space.</description>
      <content:encoded>The World Wide Web is in fact a global environment, with many languages
as well as religions, customs, and ways of life. Creating visually stimulating
designs that work for your clients—no matter how near or far they might be
requires an understanding of a variety of practices: excellent Web graphic design
skills and an awareness of the psychology of color and space.</content:encoded>
      <pubDate>Thu, 29 May 2008 05:34:40 -0700</pubDate>
      <link>http://ooyes.net/website-design-for-long-term-success</link>
      <guid isPermaLink="true">http://ooyes.net/website-design-for-long-term-success</guid>
    </item>
    <item>
      <title>Wonderful nature</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Our Wonderful nature</description>
      <content:encoded>Our Wonderful nature</content:encoded>
      <pubDate>Thu, 29 May 2008 04:28:06 -0700</pubDate>
      <link>http://ooyes.net/wonderful-nature</link>
      <guid isPermaLink="true">http://ooyes.net/wonderful-nature</guid>
    </item>
    <item>
      <title>Canvas API, 3D rendering with javascript</title>
      <author>info@ooyes.net (Website design)</author>
      <description>It was initially introduced by Apple for use inside their own Mac OS X WebKit component, powering applications like Dashboard widgets and the Safari browser. Later, it was adopted by Gecko browsers (notably Mozilla and Firefox) and Opera, and standardized by the WHATWG on new proposed specifications for next generation web technologies. Novell manufactures an XForms processor plugin for Internet Explorer, which also provides support for the canvas element. Independent efforts to support the canvas feature on Internet Explorer do not require plugins and are based solely on VML and JavaScript. Google has also begun a project to add canvas abilities to Internet Explorer using the same techniques.</description>
      <content:encoded>It was initially introduced by Apple for use inside their own Mac OS X WebKit component, powering applications like Dashboard widgets and the Safari browser. Later, it was adopted by Gecko browsers (notably Mozilla and Firefox) and Opera, and standardized by the WHATWG on new proposed specifications for next generation web technologies. Novell manufactures an XForms processor plugin for Internet Explorer, which also provides support for the canvas element. Independent efforts to support the canvas feature on Internet Explorer do not require plugins and are based solely on VML and JavaScript. Google has also begun a project to add canvas abilities to Internet Explorer using the same techniques.</content:encoded>
      <pubDate>Thu, 29 May 2008 02:30:12 -0700</pubDate>
      <link>http://ooyes.net/canvas-api-3d-rendering-with-javascript</link>
      <guid isPermaLink="true">http://ooyes.net/canvas-api-3d-rendering-with-javascript</guid>
    </item>
    <item>
      <title>Jquery Mouse Events</title>
      <author>info@ooyes.net (Website design)</author>
      <description>List of Jquery's events that are triggered by mouse movement and button presses.</description>
      <content:encoded>List of Jquery's events that are triggered by mouse movement and button presses.</content:encoded>
      <pubDate>Wed, 28 May 2008 08:56:08 -0700</pubDate>
      <link>http://ooyes.net/jquery-mouse-events</link>
      <guid isPermaLink="true">http://ooyes.net/jquery-mouse-events</guid>
    </item>
    <item>
      <title>CSS for Non-Screen Media</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Not everyone who accesses the Web can see the effects we've discussed in this book. Some 1.1 million people in the United States are blind, and they have a very different experience of the Web than sighted persons.
Fortunately, CSS is not silent on the matter of non-visual access. CSS2 included the ability to apply styles in nonlo-screen media. While most of the Web's evolution has taken place on monitorsthat is to say, in a visual mediumCSS2 can be used in non-visual media, assuming that the user agent has proper support.

</description>
      <content:encoded>Not everyone who accesses the Web can see the effects we've discussed in this book. Some 1.1 million people in the United States are blind, and they have a very different experience of the Web than sighted persons.
Fortunately, CSS is not silent on the matter of non-visual access. CSS2 included the ability to apply styles in nonlo-screen media. While most of the Web's evolution has taken place on monitorsthat is to say, in a visual mediumCSS2 can be used in non-visual media, assuming that the user agent has proper support.

</content:encoded>
      <pubDate>Wed, 28 May 2008 08:05:04 -0700</pubDate>
      <link>http://ooyes.net/css-for-non-screen-media</link>
      <guid isPermaLink="true">http://ooyes.net/css-for-non-screen-media</guid>
    </item>
    <item>
      <title>Jquery ajax utility function - $.ajax()</title>
      <author>info@ooyes.net (Website design)</author>
      <description>For those times when we want or need to exert a fine-grained level of control over
how we make Ajax requests, jQuery provides a general utility function for making
Ajax requests named $.ajax(). Under the covers, all other jQuery features that
make Ajax requests eventually use this function to initiate the request.</description>
      <content:encoded>For those times when we want or need to exert a fine-grained level of control over
how we make Ajax requests, jQuery provides a general utility function for making
Ajax requests named $.ajax(). Under the covers, all other jQuery features that
make Ajax requests eventually use this function to initiate the request.</content:encoded>
      <pubDate>Wed, 28 May 2008 04:10:24 -0700</pubDate>
      <link>http://ooyes.net/jquery-ajax-utility-function-ajax</link>
      <guid isPermaLink="true">http://ooyes.net/jquery-ajax-utility-function-ajax</guid>
    </item>
    <item>
      <title>Jquery Fade Animation - Fast Overview</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Fading elements into and out of existence. If you watched the operation of the show() and hide() effects carefully, you noted
that they scaled the size of the elements (either up or down as appropriate) and
adjusted the opacity of the elements as they grew or shrank.</description>
      <content:encoded>Fading elements into and out of existence. If you watched the operation of the show() and hide() effects carefully, you noted
that they scaled the size of the elements (either up or down as appropriate) and
adjusted the opacity of the elements as they grew or shrank.</content:encoded>
      <pubDate>Wed, 28 May 2008 03:00:53 -0700</pubDate>
      <link>http://ooyes.net/jquery-fade-animation-fast-overview</link>
      <guid isPermaLink="true">http://ooyes.net/jquery-fade-animation-fast-overview</guid>
    </item>
    <item>
      <title>Javascript in Modern Browsers</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Of all the possible browsers available on the Internet, there are only a few that keep up to date with the latest technologies, and even fewer that push the boundaries of what’s possible
with a browser. In the end, the browsers you choose to support will most likely depend on who your audience is and how much time you’re willing to put into making your applications
work right for everyone.</description>
      <content:encoded>Of all the possible browsers available on the Internet, there are only a few that keep up to date with the latest technologies, and even fewer that push the boundaries of what’s possible
with a browser. In the end, the browsers you choose to support will most likely depend on who your audience is and how much time you’re willing to put into making your applications
work right for everyone.</content:encoded>
      <pubDate>Wed, 28 May 2008 02:33:40 -0700</pubDate>
      <link>http://ooyes.net/javascript-in-modern-browsers</link>
      <guid isPermaLink="true">http://ooyes.net/javascript-in-modern-browsers</guid>
    </item>
    <item>
      <title>Canvas API, Web Applications 1.0</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The second specification that is pushing forward JavaScript development is that of the
WHAT-WG (Web Hypertext Application Technology Working Group) in creating the new
Web Applications 1.0 specification. This specification goes in a number of different directions,
adding numerous additions to HTML, the DOM, and JavaScript as a whole. Many consider the
work going into this specification is what will become HTML 5. Thankfully, unlike new versions
of JavaScript, implementations of (portions of) this specification are much easier to
come by.</description>
      <content:encoded>The second specification that is pushing forward JavaScript development is that of the
WHAT-WG (Web Hypertext Application Technology Working Group) in creating the new
Web Applications 1.0 specification. This specification goes in a number of different directions,
adding numerous additions to HTML, the DOM, and JavaScript as a whole. Many consider the
work going into this specification is what will become HTML 5. Thankfully, unlike new versions
of JavaScript, implementations of (portions of) this specification are much easier to
come by.</content:encoded>
      <pubDate>Wed, 28 May 2008 02:01:09 -0700</pubDate>
      <link>http://ooyes.net/canvas-api-web-applications-10</link>
      <guid isPermaLink="true">http://ooyes.net/canvas-api-web-applications-10</guid>
    </item>
    <item>
      <title>Fun Moments in Sports</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Funniest Moments In Sports Captured On Camera</description>
      <content:encoded>Funniest Moments In Sports Captured On Camera</content:encoded>
      <pubDate>Wed, 28 May 2008 01:16:21 -0700</pubDate>
      <link>http://ooyes.net/fun-moments-in-sports</link>
      <guid isPermaLink="true">http://ooyes.net/fun-moments-in-sports</guid>
    </item>
    <item>
      <title>Custom jQuery selectors</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The CSS selectors give us a great deal of power and flexibility to match the
desired DOM elements, but sometimes we’ll want to select elements based on a
characteristic that the CSS specification did not anticipate.</description>
      <content:encoded>The CSS selectors give us a great deal of power and flexibility to match the
desired DOM elements, but sometimes we’ll want to select elements based on a
characteristic that the CSS specification did not anticipate.</content:encoded>
      <pubDate>Tue, 27 May 2008 08:17:21 -0700</pubDate>
      <link>http://ooyes.net/custom-jquery-selectors</link>
      <guid isPermaLink="true">http://ooyes.net/custom-jquery-selectors</guid>
    </item>
    <item>
      <title>What happened to the Food</title>
      <author>info@ooyes.net (Website design)</author>
      <description>What happened to the Food</description>
      <content:encoded>What happened to the Food</content:encoded>
      <pubDate>Tue, 27 May 2008 01:19:57 -0700</pubDate>
      <link>http://ooyes.net/what-happened-to-the-food</link>
      <guid isPermaLink="true">http://ooyes.net/what-happened-to-the-food</guid>
    </item>
    <item>
      <title>Pictures of missing objects</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Pictures of missing objects</description>
      <content:encoded>Pictures of missing objects</content:encoded>
      <pubDate>Mon, 26 May 2008 07:12:23 -0700</pubDate>
      <link>http://ooyes.net/pictures-of-missing-objects</link>
      <guid isPermaLink="true">http://ooyes.net/pictures-of-missing-objects</guid>
    </item>
    <item>
      <title>Singing Ringing Tree</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The Singing Ringing Tree is a musical sculpture set in the landscape of the Pennines overlooking Burnley, in Lancashire.
Completed in 2006, it is part of the series of four sculptures within the Panopticons arts and regeneration project. The project "was set up to erect a series of 21st-century landmarks, or Panopticons (structures providing a comprehensive view), across East Lancashire as symbols of the renaissance of the area.</description>
      <content:encoded>The Singing Ringing Tree is a musical sculpture set in the landscape of the Pennines overlooking Burnley, in Lancashire.
Completed in 2006, it is part of the series of four sculptures within the Panopticons arts and regeneration project. The project "was set up to erect a series of 21st-century landmarks, or Panopticons (structures providing a comprehensive view), across East Lancashire as symbols of the renaissance of the area.</content:encoded>
      <pubDate>Mon, 26 May 2008 06:14:39 -0700</pubDate>
      <link>http://ooyes.net/singing-ringing-tree</link>
      <guid isPermaLink="true">http://ooyes.net/singing-ringing-tree</guid>
    </item>
    <item>
      <title>Obama vs Hillary cartoons</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Funny cartoons of Obama vs Hillary</description>
      <content:encoded>Funny cartoons of Obama vs Hillary</content:encoded>
      <pubDate>Sat, 24 May 2008 07:34:00 -0700</pubDate>
      <link>http://ooyes.net/obama-vs-hillary-cartoons</link>
      <guid isPermaLink="true">http://ooyes.net/obama-vs-hillary-cartoons</guid>
    </item>
    <item>
      <title>The document ready handler of jquery</title>
      <author>info@ooyes.net (Website design)</author>
      <description>When embracing Unobtrusive JavaScript, behavior is separated from structure,
so we’ll be performing operations on the page elements outside of the document
markup that creates them. In order to achieve this, we need a way to wait until
the DOM elements of the page are fully loaded before those operations execute.
In the zebra-striping example, the entire table must load before striping can
be applied.</description>
      <content:encoded>When embracing Unobtrusive JavaScript, behavior is separated from structure,
so we’ll be performing operations on the page elements outside of the document
markup that creates them. In order to achieve this, we need a way to wait until
the DOM elements of the page are fully loaded before those operations execute.
In the zebra-striping example, the entire table must load before striping can
be applied.</content:encoded>
      <pubDate>Fri, 23 May 2008 02:14:25 -0700</pubDate>
      <link>http://ooyes.net/the-document-ready-handler-of-jquery</link>
      <guid isPermaLink="true">http://ooyes.net/the-document-ready-handler-of-jquery</guid>
    </item>
    <item>
      <title>Post-Processing Form Data with onsubmit</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Apowerful application of JavaScript event handlers is to process form data before it is submitted to ensure the validity of the data. Using this, you can ensure that required fields have been completed and that fields contain valid types of data (for instance, if you are asking for a phone number in a text field, it shouldn’t contain a generic string). By validating data in the client with JavaScript, you can prompt the user to fix the problems before submitting the form and thus eliminate an unnecessary transaction with the server, which consumes bandwidth and server resources.</description>
      <content:encoded>Apowerful application of JavaScript event handlers is to process form data before it is submitted to ensure the validity of the data. Using this, you can ensure that required fields have been completed and that fields contain valid types of data (for instance, if you are asking for a phone number in a text field, it shouldn’t contain a generic string). By validating data in the client with JavaScript, you can prompt the user to fix the problems before submitting the form and thus eliminate an unnecessary transaction with the server, which consumes bandwidth and server resources.</content:encoded>
      <pubDate>Fri, 23 May 2008 01:55:28 -0700</pubDate>
      <link>http://ooyes.net/post-processing-form-data-with-onsubmit</link>
      <guid isPermaLink="true">http://ooyes.net/post-processing-form-data-with-onsubmit</guid>
    </item>
    <item>
      <title>Investor relations</title>
      <author>info@ooyes.net (Website design)</author>
      <description>A company is either going to have a section of their website dedicated to investors or they’re not, and that decision largely depends on whether they are publicly traded. For American companies, laws exist that demand certain types of filings with the SEC be made public on a company’s website, so this section may be mandatory. For others, the simple desire to communicate avidly with stakeholders (or future stakeholders if the company is ramping up to go public) drives the need for this section. 

Because this material usually appears on sites for larger corporations, drawing best practices and common design solutions is difficult because the sample pool is smaller. For instance, even the naming of the section varies, although the word “investor” is the primary term used to flag down interested parties. Some variations found across the Web are as follows: </description>
      <content:encoded>A company is either going to have a section of their website dedicated to investors or they’re not, and that decision largely depends on whether they are publicly traded. For American companies, laws exist that demand certain types of filings with the SEC be made public on a company’s website, so this section may be mandatory. For others, the simple desire to communicate avidly with stakeholders (or future stakeholders if the company is ramping up to go public) drives the need for this section. 

Because this material usually appears on sites for larger corporations, drawing best practices and common design solutions is difficult because the sample pool is smaller. For instance, even the naming of the section varies, although the word “investor” is the primary term used to flag down interested parties. Some variations found across the Web are as follows: </content:encoded>
      <pubDate>Fri, 23 May 2008 01:30:07 -0700</pubDate>
      <link>http://ooyes.net/investor-relations</link>
      <guid isPermaLink="true">http://ooyes.net/investor-relations</guid>
    </item>
    <item>
      <title>Event Accessibility</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The final piece to take into consideration when developing a purely unobtrusive web application
is to make sure that your events will work even without the use of a mouse. By doing this,
you help two groups of people: those in need of accessibility assistance (vision-impaired users),
and people who don’t like to use a mouse. (Sit down one day, disconnect your mouse from
your computer, and learn how to navigate the Web using only a mouse.</description>
      <content:encoded>The final piece to take into consideration when developing a purely unobtrusive web application
is to make sure that your events will work even without the use of a mouse. By doing this,
you help two groups of people: those in need of accessibility assistance (vision-impaired users),
and people who don’t like to use a mouse. (Sit down one day, disconnect your mouse from
your computer, and learn how to navigate the Web using only a mouse.</content:encoded>
      <pubDate>Thu, 22 May 2008 07:21:19 -0700</pubDate>
      <link>http://ooyes.net/event-accessibility</link>
      <guid isPermaLink="true">http://ooyes.net/event-accessibility</guid>
    </item>
    <item>
      <title>Fast CSS selectors tutorial</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Selectors are one of the most important aspects of CSS as they are used to "select" elements on an HTML page so that they can be styled.  Selectors are only case-sensitive if the document language is also case-sensitive (eg: HTML: not case-sensitive, XML: case-sensitive), ID selectors have a higher cascade specificity than an equivalent attribute selector (eg: the selector '#foo' has a higher specificity than '*[id="foo"]' </description>
      <content:encoded>Selectors are one of the most important aspects of CSS as they are used to "select" elements on an HTML page so that they can be styled.  Selectors are only case-sensitive if the document language is also case-sensitive (eg: HTML: not case-sensitive, XML: case-sensitive), ID selectors have a higher cascade specificity than an equivalent attribute selector (eg: the selector '#foo' has a higher specificity than '*[id="foo"]' </content:encoded>
      <pubDate>Thu, 22 May 2008 03:49:28 -0700</pubDate>
      <link>http://ooyes.net/fast-css-selectors-tutorial</link>
      <guid isPermaLink="true">http://ooyes.net/fast-css-selectors-tutorial</guid>
    </item>
    <item>
      <title>Javascript Conversions</title>
      <author>info@ooyes.net (Website design)</author>
      <description>One of the most important features of any programming language is the capability to convert between
types, and javascript provides developers with a number of easy conversion routines. Most types
contain methods that provide for simple conversion, and several global methods are available for more
complex conversion. In either case, type conversion is a short, one-step process in javascript.</description>
      <content:encoded>One of the most important features of any programming language is the capability to convert between
types, and javascript provides developers with a number of easy conversion routines. Most types
contain methods that provide for simple conversion, and several global methods are available for more
complex conversion. In either case, type conversion is a short, one-step process in javascript.</content:encoded>
      <pubDate>Thu, 22 May 2008 05:28:30 -0700</pubDate>
      <link>http://ooyes.net/javascript-conversions</link>
      <guid isPermaLink="true">http://ooyes.net/javascript-conversions</guid>
    </item>
    <item>
      <title>Object Oriented Javascript</title>
      <author>info@ooyes.net (Website design)</author>
      <description>From a language perspective, there is absolutely nothing modern about object-oriented
programming or object-oriented JavaScript; JavaScript was designed to be a completely
object-oriented language from the start. However, as JavaScript has “evolved” in its use and
acceptance, programmers of other languages (such as Ruby, Python, and Perl) have taken
note and begun to bring their programmatic idioms over to JavaScript.</description>
      <content:encoded>From a language perspective, there is absolutely nothing modern about object-oriented
programming or object-oriented JavaScript; JavaScript was designed to be a completely
object-oriented language from the start. However, as JavaScript has “evolved” in its use and
acceptance, programmers of other languages (such as Ruby, Python, and Perl) have taken
note and begun to bring their programmatic idioms over to JavaScript.</content:encoded>
      <pubDate>Thu, 22 May 2008 05:06:20 -0700</pubDate>
      <link>http://ooyes.net/object-oriented-javascript</link>
      <guid isPermaLink="true">http://ooyes.net/object-oriented-javascript</guid>
    </item>
    <item>
      <title>CSS pseudo selectors</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Pseudo-Classes and Pseudo-Elements.These kind of selectors allow that styles are applied to pieces of a document, based on something else than the structure of the document. The styles are based on circumstances that can not be predicted in advance. Pseudo-classes and pseudo-elements can be used in CSS selectors, but do not exist in the HTML source.</description>
      <content:encoded>Pseudo-Classes and Pseudo-Elements.These kind of selectors allow that styles are applied to pieces of a document, based on something else than the structure of the document. The styles are based on circumstances that can not be predicted in advance. Pseudo-classes and pseudo-elements can be used in CSS selectors, but do not exist in the HTML source.</content:encoded>
      <pubDate>Thu, 22 May 2008 04:38:44 -0700</pubDate>
      <link>http://ooyes.net/css-pseudo-selectors</link>
      <guid isPermaLink="true">http://ooyes.net/css-pseudo-selectors</guid>
    </item>
    <item>
      <title>Real-world accessibility</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The WCAG contains many valuable strategies for opening your site’s doors as widely as possible. But they do not always map to common, real-world scenarios. Designers and developers often find themselves following the spirit of accessibility without adhering to every letter of the law, because at the end of the day, common sense will dictate what is in the best interest of your visitors. 

Some Priority Level 3 requirements are as easy and useful to implement as Level 1, just as some Level 1 requirements are nearly impossible to objectively quantify. For instance, checkpoint 14.1, required for Level 1 compliance—“Use the clearest and simplest language appropriate for a site’s content”—is an area where many feel the W3C itself falls short. They might disagree, and how could you argue with them if they did? What quantifiable measuring sticks do web developers have to rate content? 

It’s important to dispel the myth that accessible sites must be ugly. Too many designers equate accessibility with all-text documents without visual formatting or decorative images. This could not be further from the truth. Ninety-nine percent of accessibility is achieved within the markup (the one notable exception being accommodating the visually impaired with wise color choices), so even the most beautiful sites can welcome all visitors. 

The bolt tightening and pipe cleaning that needs to be done under a corporate website’s hood is usually quite minimal. The value that a few pieces of additional markup brings to the table is enormous. If Target had put just a few extra hours of spit and polish into their HTML, they might have completely avoided a costly and widely publicized lawsuit. The rest of this chapter will explore some tactics for better real-world accessibility—changes that will directly benefit visitors without getting hung up on explicit WCAG compliance. </description>
      <content:encoded>The WCAG contains many valuable strategies for opening your site’s doors as widely as possible. But they do not always map to common, real-world scenarios. Designers and developers often find themselves following the spirit of accessibility without adhering to every letter of the law, because at the end of the day, common sense will dictate what is in the best interest of your visitors. 

Some Priority Level 3 requirements are as easy and useful to implement as Level 1, just as some Level 1 requirements are nearly impossible to objectively quantify. For instance, checkpoint 14.1, required for Level 1 compliance—“Use the clearest and simplest language appropriate for a site’s content”—is an area where many feel the W3C itself falls short. They might disagree, and how could you argue with them if they did? What quantifiable measuring sticks do web developers have to rate content? 

It’s important to dispel the myth that accessible sites must be ugly. Too many designers equate accessibility with all-text documents without visual formatting or decorative images. This could not be further from the truth. Ninety-nine percent of accessibility is achieved within the markup (the one notable exception being accommodating the visually impaired with wise color choices), so even the most beautiful sites can welcome all visitors. 

The bolt tightening and pipe cleaning that needs to be done under a corporate website’s hood is usually quite minimal. The value that a few pieces of additional markup brings to the table is enormous. If Target had put just a few extra hours of spit and polish into their HTML, they might have completely avoided a costly and widely publicized lawsuit. The rest of this chapter will explore some tactics for better real-world accessibility—changes that will directly benefit visitors without getting hung up on explicit WCAG compliance. </content:encoded>
      <pubDate>Thu, 22 May 2008 04:24:03 -0700</pubDate>
      <link>http://ooyes.net/real-world-accessibility</link>
      <guid isPermaLink="true">http://ooyes.net/real-world-accessibility</guid>
    </item>
    <item>
      <title>Simple javascript treeview</title>
      <author>info@ooyes.net (Website design)</author>
      <description>The Treeview is one of the easiest and fastest site navigation menus. This page offers some tips on how to make the best of it. Very light and semantic way to make treeview navigation with javascript. And it is supported for all browsers. </description>
      <content:encoded>The Treeview is one of the easiest and fastest site navigation menus. This page offers some tips on how to make the best of it. Very light and semantic way to make treeview navigation with javascript. And it is supported for all browsers. </content:encoded>
      <pubDate>Thu, 22 May 2008 04:10:21 -0700</pubDate>
      <link>http://ooyes.net/simple-javascript-treeview</link>
      <guid isPermaLink="true">http://ooyes.net/simple-javascript-treeview</guid>
    </item>
    <item>
      <title>Consider accessibility from the beginning</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Building accessible websites is a habit. It’s a mindset that should be adopted from the first day of planning to the last hour of quality assurance. An architect plans the wheelchair ramps from the first building blueprints; a developer should always reference a mental checklist of accessibility considerations from the first wireframes and comps in Photoshop. 

The rest of this chapter explores two key aspects of accessibility. First, it covers the legal requirements for corporations and web developers. This varies from country to country and occasionally changes, but we’ll do our best to navigate those thorny paths. Second, it covers what you can do—today—to apply unobtrusive accessibility tactics to your site without disrupting the design or architecture. Even the smallest improvements in the markup can have tremendous benefits to a significant number of users, and we’ll cover the critical basics before establishing a roadmap for future learning. </description>
      <content:encoded>Building accessible websites is a habit. It’s a mindset that should be adopted from the first day of planning to the last hour of quality assurance. An architect plans the wheelchair ramps from the first building blueprints; a developer should always reference a mental checklist of accessibility considerations from the first wireframes and comps in Photoshop. 

The rest of this chapter explores two key aspects of accessibility. First, it covers the legal requirements for corporations and web developers. This varies from country to country and occasionally changes, but we’ll do our best to navigate those thorny paths. Second, it covers what you can do—today—to apply unobtrusive accessibility tactics to your site without disrupting the design or architecture. Even the smallest improvements in the markup can have tremendous benefits to a significant number of users, and we’ll cover the critical basics before establishing a roadmap for future learning. </content:encoded>
      <pubDate>Thu, 22 May 2008 03:30:43 -0700</pubDate>
      <link>http://ooyes.net/consider-accessibility-from-the-beginning</link>
      <guid isPermaLink="true">http://ooyes.net/consider-accessibility-from-the-beginning</guid>
    </item>
    <item>
      <title>System Fonts and Colors</title>
      <author>info@ooyes.net (Website design)</author>
      <description>There may be times when you want your document to mimic the user's computing environment as closely as possible. An obvious example is if you're creating web-based applications, where the goal is to make the web component seem like a part of the user's operating system. While CSS2 doesn't make it possible to reuse every last aspect of the operating system's appearance in your documents, you can choose from a wide variety of colors and a short list of fonts.</description>
      <content:encoded>There may be times when you want your document to mimic the user's computing environment as closely as possible. An obvious example is if you're creating web-based applications, where the goal is to make the web component seem like a part of the user's operating system. While CSS2 doesn't make it possible to reuse every last aspect of the operating system's appearance in your documents, you can choose from a wide variety of colors and a short list of fonts.</content:encoded>
      <pubDate>Thu, 22 May 2008 03:30:39 -0700</pubDate>
      <link>http://ooyes.net/system-fonts-and-colors</link>
      <guid isPermaLink="true">http://ooyes.net/system-fonts-and-colors</guid>
    </item>
    <item>
      <title>Length Units</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Length Units
Many CSS properties, such as margins, depend on length measurements to properly display various page elements. It's no surprise, then, that there are a number of ways to measure length in CSS.

All length units can be expressed as either positive or negative numbers followed by a label (although some properties will accept only positive numbers). You can also use real numbersthat is, numbers with decimal fractions, such as 10.5 or 4.561. All length units are followed by a two-letter abbreviation that represents the actual unit of length being specified, such as in (inches) or pt (points). The only exception to this rule is a length of 0 (zero), which need not be followed by a unit.
</description>
      <content:encoded>Length Units
Many CSS properties, such as margins, depend on length measurements to properly display various page elements. It's no surprise, then, that there are a number of ways to measure length in CSS.

All length units can be expressed as either positive or negative numbers followed by a label (although some properties will accept only positive numbers). You can also use real numbersthat is, numbers with decimal fractions, such as 10.5 or 4.561. All length units are followed by a two-letter abbreviation that represents the actual unit of length being specified, such as in (inches) or pt (points). The only exception to this rule is a length of 0 (zero), which need not be followed by a unit.
</content:encoded>
      <pubDate>Thu, 22 May 2008 03:08:35 -0700</pubDate>
      <link>http://ooyes.net/length-units</link>
      <guid isPermaLink="true">http://ooyes.net/length-units</guid>
    </item>
    <item>
      <title>Accessibility benefits everyone</title>
      <author>info@ooyes.net (Website design)</author>
      <description>It is probably true that the majority of a corporation’s website visitors will have passable vision, no significant learning disabilities, and not suffer from epilepsy. It’s even common for businesses to think people with those inhibitions will never visit their site because “that’s not our target audience.” But remember that a target audience is not the only audience, and disabilities are more common than most believe (remember, about 32 million in the United States alone). Beyond designing for that significant slice of the population, there are many reasons to consider accessibility in a corporate web project. </description>
      <content:encoded>It is probably true that the majority of a corporation’s website visitors will have passable vision, no significant learning disabilities, and not suffer from epilepsy. It’s even common for businesses to think people with those inhibitions will never visit their site because “that’s not our target audience.” But remember that a target audience is not the only audience, and disabilities are more common than most believe (remember, about 32 million in the United States alone). Beyond designing for that significant slice of the population, there are many reasons to consider accessibility in a corporate web project. </content:encoded>
      <pubDate>Thu, 22 May 2008 02:42:43 -0700</pubDate>
      <link>http://ooyes.net/accessibility-benefits-everyone</link>
      <guid isPermaLink="true">http://ooyes.net/accessibility-benefits-everyone</guid>
    </item>
    <item>
      <title>CSS inheritance</title>
      <author>info@ooyes.net (Website design)</author>
      <description>As important as specificity may be to understanding how declarations are applied to a document, another key concept is inheritance. Inheritance is the mechanism by which styles are applied not only to a specified element, but also to its descendants. If a color is applied to an H1 element, for example, then that color is applied to all text in the h1, even the text enclosed within child elements of that h1.</description>
      <content:encoded>As important as specificity may be to understanding how declarations are applied to a document, another key concept is inheritance. Inheritance is the mechanism by which styles are applied not only to a specified element, but also to its descendants. If a color is applied to an H1 element, for example, then that color is applied to all text in the h1, even the text enclosed within child elements of that h1.</content:encoded>
      <pubDate>Thu, 22 May 2008 02:40:12 -0700</pubDate>
      <link>http://ooyes.net/css-inheritance</link>
      <guid isPermaLink="true">http://ooyes.net/css-inheritance</guid>
    </item>
    <item>
      <title>Accessibility is not just for the blind </title>
      <author>info@ooyes.net (Website design)</author>
      <description>While the design industry is slowly becoming more educated through the evangelism of Joe Clark1 and sites like Ian Lloyd’s Accessify,2 many web designers still incorrectly equate “disabled” with “blind.” While it is true that the Web plays host to a significant number of people with visual impairments, to slice the definition of disability so narrow is a disservice to the millions of users with other handicaps. </description>
      <content:encoded>While the design industry is slowly becoming more educated through the evangelism of Joe Clark1 and sites like Ian Lloyd’s Accessify,2 many web designers still incorrectly equate “disabled” with “blind.” While it is true that the Web plays host to a significant number of people with visual impairments, to slice the definition of disability so narrow is a disservice to the millions of users with other handicaps. </content:encoded>
      <pubDate>Thu, 22 May 2008 02:24:02 -0700</pubDate>
      <link>http://ooyes.net/accessibility-is-not-just-for-the-blind</link>
      <guid isPermaLink="true">http://ooyes.net/accessibility-is-not-just-for-the-blind</guid>
    </item>
    <item>
      <title>First-child issue</title>
      <author>info@ooyes.net (Website design)</author>
      <description>This pseudo-class matches an element only if it’s the first child element of its parent element. For instance, li:first-child matches the first list item in an ol or ul element. It doesn’t match the first child of a list item. Requires Windows Internet Explorer 7 or later but altho there is a way to make it internet explorer 6.
.</description>
      <content:encoded>This pseudo-class matches an element only if it’s the first child element of its parent element. For instance, li:first-child matches the first list item in an ol or ul element. It doesn’t match the first child of a list item. Requires Windows Internet Explorer 7 or later but altho there is a way to make it internet explorer 6.
.</content:encoded>
      <pubDate>Thu, 22 May 2008 02:18:22 -0700</pubDate>
      <link>http://ooyes.net/first-child-issue</link>
      <guid isPermaLink="true">http://ooyes.net/first-child-issue</guid>
    </item>
    <item>
      <title> fixed position for msie6 with no hacks</title>
      <author>info@ooyes.net (Website design)</author>
      <description>An element with position: fixed is positioned at the specified coordinates relative to the browser window. The element's position is specified with the "left", "top", "right", and "bottom" properties. The element remains at that position regardless of scrolling. Works in IE7 (strict mode)</description>
      <content:encoded>An element with position: fixed is positioned at the specified coordinates relative to the browser window. The element's position is specified with the "left", "top", "right", and "bottom" properties. The element remains at that position regardless of scrolling. Works in IE7 (strict mode)</content:encoded>
      <pubDate>Thu, 22 May 2008 01:47:25 -0700</pubDate>
      <link>http://ooyes.net/fixed-position-for-msie6-with-no-hacks</link>
      <guid isPermaLink="true">http://ooyes.net/fixed-position-for-msie6-with-no-hacks</guid>
    </item>
    <item>
      <title>Attribute selector issue</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Attribute selectors have two parts. The first part is a selector that identifies an element - it might be a type selector, or a more specific kind of selector such as a descendant selector. The second part specifies a condition for the attributes of the element.</description>
      <content:encoded>Attribute selectors have two parts. The first part is a selector that identifies an element - it might be a type selector, or a more specific kind of selector such as a descendant selector. The second part specifies a condition for the attributes of the element.</content:encoded>
      <pubDate>Thu, 22 May 2008 01:25:46 -0700</pubDate>
      <link>http://ooyes.net/attribute-selector-issue</link>
      <guid isPermaLink="true">http://ooyes.net/attribute-selector-issue</guid>
    </item>
    <item>
      <title>Cross-Browser Indentation in Lists</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Writing Cross-Browser Indentation in Lists. Different browsers use different methods to pad or indent a list. Mozilla and Netscape 6+ browsers indent a list on the padding, while Internet Explorer and Opera pad a list through the margin of a list.</description>
      <content:encoded>Writing Cross-Browser Indentation in Lists. Different browsers use different methods to pad or indent a list. Mozilla and Netscape 6+ browsers indent a list on the padding, while Internet Explorer and Opera pad a list through the margin of a list.</content:encoded>
      <pubDate>Tue, 20 May 2008 06:41:08 -0700</pubDate>
      <link>http://ooyes.net/cross-browser-indentation-in-lists</link>
      <guid isPermaLink="true">http://ooyes.net/cross-browser-indentation-in-lists</guid>
    </item>
    <item>
      <title>Design considerations for content</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Some web designers may think they are perfectly justified in glazing over this chapter. It is after all, about content, not design, or even traditional information architecture. But the reality is that the two elements are fundamentally bound, like hydrogen and oxygen atoms in a water molecule. In fact, their symbiosis is driving many designers to become increasingly conscious of web content—what messaging works and what doesn’t, how people react to typography decisions, how people scan content within a page, and so forth. Every day new research offers deeper insight into how the masses interact with content. Those theories and best practices filter down and permeate the decisions driving how interfaces, navigation elements, body text, and more are actually designed. </description>
      <content:encoded>Some web designers may think they are perfectly justified in glazing over this chapter. It is after all, about content, not design, or even traditional information architecture. But the reality is that the two elements are fundamentally bound, like hydrogen and oxygen atoms in a water molecule. In fact, their symbiosis is driving many designers to become increasingly conscious of web content—what messaging works and what doesn’t, how people react to typography decisions, how people scan content within a page, and so forth. Every day new research offers deeper insight into how the masses interact with content. Those theories and best practices filter down and permeate the decisions driving how interfaces, navigation elements, body text, and more are actually designed. </content:encoded>
      <pubDate>Wed, 21 May 2008 09:27:12 -0700</pubDate>
      <link>http://ooyes.net/design-considerations-for-content</link>
      <guid isPermaLink="true">http://ooyes.net/design-considerations-for-content</guid>
    </item>
    <item>
      <title>To be found, you need to say something</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Here’s the reality: people search with words that make sense to them. For most people, that means plain, short, common words, not the oblique marketing speak so prevalent on the Web. 

Too many corporate sites (and the technology sector is by far the most consistent offender) feature marketing messages so pregnant with buzzwords, made-up phrases, and convoluted clauses that it’s questionable whether the original writer has any clue what he was trying to communicate. 

The company that speaks in everyday vernacular will simply appeal to a wider customer base. For instance, people will not type “integrated premises-based ECM solution” into a search engine. So if your site says that, you are missing a disproportionately large segment of your target audience. Someone might type in “content management for accounts payable.” Maybe. More likely, that person will search for “software to organize invoices,” and then find the company that solves this problem without talking about all of that ECM mumbo jumbo. </description>
      <content:encoded>Here’s the reality: people search with words that make sense to them. For most people, that means plain, short, common words, not the oblique marketing speak so prevalent on the Web. 

Too many corporate sites (and the technology sector is by far the most consistent offender) feature marketing messages so pregnant with buzzwords, made-up phrases, and convoluted clauses that it’s questionable whether the original writer has any clue what he was trying to communicate. 

The company that speaks in everyday vernacular will simply appeal to a wider customer base. For instance, people will not type “integrated premises-based ECM solution” into a search engine. So if your site says that, you are missing a disproportionately large segment of your target audience. Someone might type in “content management for accounts payable.” Maybe. More likely, that person will search for “software to organize invoices,” and then find the company that solves this problem without talking about all of that ECM mumbo jumbo. </content:encoded>
      <pubDate>Wed, 21 May 2008 08:57:27 -0700</pubDate>
      <link>http://ooyes.net/to-be-found-you-need-to-say-something</link>
      <guid isPermaLink="true">http://ooyes.net/to-be-found-you-need-to-say-something</guid>
    </item>
    <item>
      <title>Website platforms </title>
      <author>info@ooyes.net (Website design)</author>
      <description>There are numerous platforms on which to develop a corporate website—some are turnkey (meaning that everything works right out of the box), and others are customizable solutions ranging from small, free, and open source to large, expensive, and proprietary. Some websites are built entirely in Flash, others in static HTML, and others in closed platforms like Lotus Notes and Domino. 

HTML vs. Flash 

Flash has grown from crude animation software to a mature application development environment. Many design agencies specialize in Flash websites, and their creations are often rich interactive experiences built to wow the audience. While it is possible to build a corporate website entirely in Flash, there are several key disadvantages to the platform: </description>
      <content:encoded>There are numerous platforms on which to develop a corporate website—some are turnkey (meaning that everything works right out of the box), and others are customizable solutions ranging from small, free, and open source to large, expensive, and proprietary. Some websites are built entirely in Flash, others in static HTML, and others in closed platforms like Lotus Notes and Domino. 

HTML vs. Flash 

Flash has grown from crude animation software to a mature application development environment. Many design agencies specialize in Flash websites, and their creations are often rich interactive experiences built to wow the audience. While it is possible to build a corporate website entirely in Flash, there are several key disadvantages to the platform: </content:encoded>
      <pubDate>Wed, 21 May 2008 08:30:57 -0700</pubDate>
      <link>http://ooyes.net/website-platforms</link>
      <guid isPermaLink="true">http://ooyes.net/website-platforms</guid>
    </item>
    <item>
      <title>Redesigning your site</title>
      <author>info@ooyes.net (Website design)</author>
      <description>While there are many people reading this book interested in building a new company’s website, chances are there are just as many people looking to improve an old one. Redesigning can be a major undertaking. Depending on the magnitude, it can be as challenging as a brand new design. But listing the reasons for the revamp and the goals the site will accomplish, and then selling the whole idea to your management team, can help make your site better than ever. 

It can be assumed that any business that wishes to compete in the globalized world market has a website. The medium has been mature for over a decade. College dorm startups, old-world companies (think Ford or Coca-Cola), small businesses, and worldwide mega-corporations have all benefited from and praised the return on investment that a strong Internet presence brings. </description>
      <content:encoded>While there are many people reading this book interested in building a new company’s website, chances are there are just as many people looking to improve an old one. Redesigning can be a major undertaking. Depending on the magnitude, it can be as challenging as a brand new design. But listing the reasons for the revamp and the goals the site will accomplish, and then selling the whole idea to your management team, can help make your site better than ever. 

It can be assumed that any business that wishes to compete in the globalized world market has a website. The medium has been mature for over a decade. College dorm startups, old-world companies (think Ford or Coca-Cola), small businesses, and worldwide mega-corporations have all benefited from and praised the return on investment that a strong Internet presence brings. </content:encoded>
      <pubDate>Wed, 21 May 2008 08:14:39 -0700</pubDate>
      <link>http://ooyes.net/redesigning-your-site</link>
      <guid isPermaLink="true">http://ooyes.net/redesigning-your-site</guid>
    </item>
    <item>
      <title>Simple Hover for ie6</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Simple Hover for ie6 for every elements.
Most modern browsers support the :hover selector for any html element. This is cool, because it enables you to, for instance, apply a mouseover effect to table rows  using only CSS. IE however, with a market share of &gt; 90%, does not natively support :hover on elements other than links , rendering the entire :hover concept useless. Or does it?</description>
      <content:encoded>Simple Hover for ie6 for every elements.
Most modern browsers support the :hover selector for any html element. This is cool, because it enables you to, for instance, apply a mouseover effect to table rows  using only CSS. IE however, with a market share of &gt; 90%, does not natively support :hover on elements other than links , rendering the entire :hover concept useless. Or does it?</content:encoded>
      <pubDate>Tue, 20 May 2008 06:09:11 -0700</pubDate>
      <link>http://ooyes.net/simple-hover-for-ie6</link>
      <guid isPermaLink="true">http://ooyes.net/simple-hover-for-ie6</guid>
    </item>
    <item>
      <title>Positioning</title>
      <author>info@ooyes.net (Website design)</author>
      <description>There are four types of positioning: static, relative, absolute, fixed. The element's box is generated as normal. Block-level elements generate a rectangular box that is part of the document's flow, and inline-level boxes cause the creation of one or more line boxes that are flowed within their parent element.</description>
      <content:encoded>There are four types of positioning: static, relative, absolute, fixed. The element's box is generated as normal. Block-level elements generate a rectangular box that is part of the document's flow, and inline-level boxes cause the creation of one or more line boxes that are flowed within their parent element.</content:encoded>
      <pubDate>Tue, 20 May 2008 06:50:30 -0700</pubDate>
      <link>http://ooyes.net/positioning</link>
      <guid isPermaLink="true">http://ooyes.net/positioning</guid>
    </item>
    <item>
      <title>What your website should do </title>
      <author>info@ooyes.net (Website design)</author>
      <description>Traditionally, corporate websites have been offensive, built to sell. But offense is not enough. In sports, there are three facets to every successful team: offense, defense, and coaching. The most effective websites have a similar three-pronged approach: marketing to new customers (offense), supporting existing customers (defense), and providing general corporate information that supports the other two (coaching). Let’s examine these three key tiers more closely. </description>
      <content:encoded>Traditionally, corporate websites have been offensive, built to sell. But offense is not enough. In sports, there are three facets to every successful team: offense, defense, and coaching. The most effective websites have a similar three-pronged approach: marketing to new customers (offense), supporting existing customers (defense), and providing general corporate information that supports the other two (coaching). Let’s examine these three key tiers more closely. </content:encoded>
      <pubDate>Wed, 21 May 2008 08:00:50 -0700</pubDate>
      <link>http://ooyes.net/what-your-website-should-do</link>
      <guid isPermaLink="true">http://ooyes.net/what-your-website-should-do</guid>
    </item>
    <item>
      <title>SEO tactics</title>
      <author>info@ooyes.net (Website design)</author>
      <description>Once the optimization strategy is defined, it’s a matter of tactical execution. In SEO, there are many, many things that can be done to support the campaign, from internal content tweaking to external link building to continued keyword research and competitive analysis. Successful campaigns are a blend of these channels—relying on any single device is like driving an 18-wheel truck on only one tire. 

Methods for SEO can be placed into one of two broad categories: SEO-specific tweaks made to the website itself (internal), and tactics outside the domain (external). Beyond that, it’s just a cycle of research, strategy evaluation, and campaign monitoring to ensure the effort is actually driving desired marketing results, not just upping the number of visitors.</description>
      <content:encoded>Once the optimization strategy is defined, it’s a matter of tactical e