Community Support for OpenDocMan (Deprecated)
Customising CSS, Images and Feel - Printable Version

+- Community Support for OpenDocMan (Deprecated) (
+-- Forum: OpenDocMan Community Discussion (
+--- Forum: OpenDocMan Support - Community Based (
+--- Thread: Customising CSS, Images and Feel (/thread-143.html)

Customising CSS, Images and Feel - Stephen - 01-13-2010

2007-07-24 12:00:50 PDT
Just wondering if there is a guide for customising the feel of the site, or building my own theme. I could easily edit the code but dont want to compramise any future upgrades? What is the best way to do this to ensure no change to the site when future versions are released?

2007-07-24 12:47:37 PDT
I knew someone was going to eventually ask this...

Editing the CSS should be simple... just save your changes before upgrading.
Replacing the icons should be simple... again, save your copies before upgrading.

but, there is alot of color stuff that is embedded within the PHP files. I've thought about this, and I think it either needs to get pulled out into a single config file, or somehow rolled into the CSS file.

2007-07-24 14:07:47 PDT
look at templates/default/ for an example. Copy this folder to something new and edit the config_local.php to change the "theme" variable from "default" to your new theme. You can then customize it.

In the future you will be able to customize more of the internal content using your own themes.


2007-07-26 10:36:28 PDT
But the only things in the templates defaults directory are the header and footer scripts with nothing that really changes the feel eg. table bg colours, fonts etc ...this is what is needed if people want to integrate odm into their preexisting site.

Editing the raw php is easy enough, but Im worried that future upgrades will over write my changes. IMHO all these things should be in css of which the default can be overwritten in a similar way as the config file.

Does that make sense?

2007-07-26 10:52:39 PDT
Agreed. I have not used CSS enough to know if some of the colors that are used dynamically can be migrated into the CSS file.

2007-07-26 14:40:35 PDT
As I said... "In the future". As of now, the HTML is still embedded in the PHP code. The separation of HTML from the PHP is currently in the planning stages.


2007-07-27 09:58:41 PDT
Cool, I think it is quite an important thing to do, ad I'm happy to help if I can. I dont know a huge amount about programming (at least about how this program has been written) but do know a lot about website design.

In its current format I simply can not use this program / offer it to clients, it renders badly, and the variation between serif and sans serif fonts looks very bad. Simple things can make a huge differnce.

2007-07-30 06:43:56 PDT
Hi -

Steve may have a different opinion, based on the work he's doing or planning to separate the PHP and HTML.

It would be helpful to better define what "renders badly" means, and to point out specific issues. I know what you mean about variation in fonts, but I can't seem to see where in ODM this happens... purhaps it has something to do with browser defaults so some people see the variation, and some don't.

2007-07-30 12:29:15 PDT
I just included a new css file in the header which has a .body style so everything renders in arial ... very simple change in the css massively improves the rendering.
eg. a quick screen shot. Still very much a work in progress, but you get the idea.
<!-- m --><a class="postlink" href=""></a><!-- m -->

The rendering should be browser independent, if it isnt it is bad html.

2007-07-31 04:30:33 PDT
Hi -

I looked at the screenshot... maybe it's just me, but the page "rendered" the same way, just with a different font. Not worse, not better, just different.

But I do agree that it should be easy for the end user to customize.