theming

I develop or alter a lot of themes / templates for Drupal, Wordpress, Joomla and will add an new section for each of these soon.
While Most of these template are aimed at one CMS system it is usually quite easy to alter for any of the major CMS platforms so I will create a version for the three  big ones (Joomla, Wordpress, Drupal even DotNetNuke when possible) and offer them for download GPL License or Creative Commens License depending upon the Template.
Check back for another source of templates or themes soon.
 

Most of the default Drupal Themes display a simple list of the last 10 entries with pagination if needed.

Some of my first custom front pages involved writing sql and laying out the results within the page-front.tpl. While this worked great and made it easy to control exactly what and where things appear.

But later on when the owner wanted mild changes it required digging back into a complex template file instead of just making alterations from within the Drupal Admin area.

I like how the see also box is working / looking but want more choices when writing something.

I've added a single line text field to allow for the header text which before was hard coded into the tpl file to 'See Also' , and added a full text field to display below the links  within the same div to allow for a short text blurb and perhaps any external links which aren't possible in the node reference field. ( I might add one above or perhaps some sort of flag to choose where the text appears, either above or below the links)

In the previous meta description entries  I created a meta description field for my content type, altered my page.tpl to show the meta description if it was available and used the site $mission field to use as the front page meta description.

Now I need to alter it again to use a taxonomies term description as the meta description for those pages. I also added a title alteration for paginated pages.

 The goal was to use Google CSE on drupal, and while I got it working it was not near as easy as I would have liked.

At first it seemed simple, google provides two pieces of code; One to build the search form, and one to display the results within your own page.

I added a block for the Google search form which was quite simple. After creating the block I removed Drupals search block and added the new Google search block. (On creating the search engine I gave it the url of http://cross-tags.com/search-result for the results to appear).

Now I want to be able to add a floating block similar to the related content block I added earlier. But I also want to be able to add as blocks as I want and control where at in the entry it appears.

So instead I used css and some images to create one the author could create when and where needed. (The author must be able to use the full html input format or the code will not come through)

While taxonomy and views can be used prived a list of related entries, it lacks the ability for the author to select individual related entries. Such as writing a short series over time and wanting each in the series to display links to the others.

For this purpose I added a new field Node reference to allow the author to add as many references to existing nodes as needed.

I had someone today request that the search form on their site contain the word search and for that word to disappear once the user clicked on it (onfocus). I have set this sites search to do that for now.

On prior plain or other non Drupal sites I'd usually just set the value in the field and add an onfocus to clear it. Not wanting to hook the search form a quick jQuery addition to the template not only worked but didn't have the issues of browsers with out javascript enabled.

Getting my meta description tag working how I wanted went well (Content Type Field Alterations  More meta tag work) until I visited the taxonomy page and any other pages that weren't a normal node or the front page.

Now that I have my main content type collecting a meta description field I have to edit my template (For a few more days using Garland (I should have just copied Garland into the proper directory before I edited it but no worries for now)