# GeekLog Costomization Guide

- Overview
- Customization
- Support

## Overview

GeekLog was developed for the Security Geeks web site and has been released under the GNU GPL for use by others. Configuring GeekLog is meant to be an easy process though it will require you to have access to several components of your system.

This document is still evolving, so there may be unintended omissions or various steps may be over or under explained. It's assumed that you have some working experience with some form of Apache, SQL databases, and PHP.

## Customization

Customizing GeekLog is fairly easy, but not automated... Yet... My suggestion when working with customizing GeekLog is to take it slow, make one change at a time and always backup your your work!

There are three main files to customize the look of Geeklog:

File | Description
public_html/layout/style.css | Here you can change font's, colors, borders or anything that CSS can do.
public_html/layout/header.inc | This is the header that formats the layout for the page. Be careful in here as there are some PHP calls as well, but this is the base HTML layout for the site.
public_html/layout/footer.inc | This is the corresponding footer to the header file. Be careful in here as well.

Additionally some HTML has been moved in to layout blocks which you can edit though the user interface. Right now this is limited to the block functions (blockheader and blockfooter) but customizing this will go a long way to making your site look unique!

Certain tags are supported in the layout blocks, these are:

Row | Description
%title | Will print the title for the block that is supplied when the block is called.
%help | Will print a ? and link to a help file for this block.

## Support

- Bug reports - Submit bug reports at SourceForge.
- Mailing lists - Join the mailing list.
- Patches - Please submit patches at SourceForge.
- General Help - A better place for general "I can't do it!" help is the mailing list. Stuff that may be of more general interest is welcome here; but you will probably get better help on the lists.
- Link submissions - Use the contribute link link to tell us about your new site running GeekLog.
- Story submissions - Use the contribute news link to tell us your ideas for the GeekLog site and questions. DO NOT use this for bug reports. Use SourceForge for bug reports. Also try not to use it for general "I can't do this!" help; you'll get a much better response for those on the mailing list.
- Feature requests - Where to send feature requests depends a bit on what the request is. In general, the mailing list is a decent place, and if it is something significant, you may want to send it in as a story submission. You may also want to go over to SourceForge and submit it as a bug report (make sure you select "Feature Request" for the "Group"), so we can have it filed and we can track it easily.

Tony Bibbs (tony@tonybibbs.com)
Last Updated: September 18, 2000