HockeyPulse

Keeping you on the Pulse of Australian Ice Hockey

NEWSFLASH
A Facelift for HockeyPulse? » HockeyPulse is undergoing a facelift. 
AIHL July 11/12 » Northstars 7 Adrenaline 5, Tongues 3 Knights 1, Bears 3 Dogs 5, Tongues 5 Knights 1, Northstars 5 Ice 2
AIHL Upcoming Sat 18 July » Tongues @ Adrenaline (4:30pm), Ice @ Northstars (5pm)
AIHL Upcoming Sun 19 July » Tongues @ Adrenaline (3:15pm), Knights @ Bears (5pm), Ice @ Ice Dogs (5pm)
 

Becsta's Blog

Welcome to Becsta's BLOG.  Here you can read all about my adventures during my illustrious (umm... infamous) career as a wannabe Ice Hockey player, and intrepid HockeyPulse Administrator!

I hereby order you to kick back, pick up that hockey stick, lace up those skates, velcro up the 'ole pads, and slap on the brain protector, 'coz a slapshot is heading your way!



CSS Nightmares

Ever since acquiring HockeyPulse from Rowan, I've been busy reworking the site, because I didn't like the format of the '08 site.  HP08 (and previous years) was built using the Joomla CMS framework, and I've decided to stick with it at least for another year.  I've detailed in a previous article about being forced to know the innards of Jooma, because I quickly discovered that I couldn't just upload a template, and add articles to it.

Joomla is a classic PHP-based content management system, integrating CSS, HTML, images, and a database backend.  Move beyond the basic template (which is the "theme" for the site), and I've been mired in CSS.  I've spent more time tweaking and being frustrated by CSS than writing PHP code or HTML snippets.  I thought CSS was supposed to make things easy!?

Here I am, about to relegate HP08 to the backups, and implement HP09.

 
Playing around with Joomla

My personal website (www.becsta.com) is built using Wordpress, which I'm reasonably familiar with.  Wordpress is fairly straight-forward and simple.  It has a home page driven by PHP scripts, and formatted by CSS styles.  There are static pages, and dynamic articles, which form blog-like pages.  The placement of "modules" is also fairly straight forward, because the module code is placed directly into the page (well, most of the time a hook to some module code is placed in the page).

Joomla is quite a different beast entirely.  The main page is formed by blocks of module positions, and maybe an article or two.  Each module position is exactly that, just a position.  There's a very brief mention of the position name in the PHP code, which Joomla parses during page streaming, and running each of the modules in turn, which are responsible for outputing whatever they need to output.  

From a layout perspective, CSS is responsible for positioning each module block on the final page, so it becomes quite difficult for a punter like me to program a new module position.  It's pure trial and error!

So far, my bacon has been saved many times by a Firefox plugin called "Firebug".  It's just _awesome_ for discovering how pages are laid out, and great for on-the-fly CSS changes.  I can change colours of individual sections to see how they look before committing them to the CSS style sheets.  Great stuff.

Well, that's about it for now.

 


Banner