As the developers of Open Journal Systems, Open Conference Systems, Open Harvester Systems, and Open Monograph Press, the PKP team are experts in helping journal managers and conference organizers make the most of their online publishing projects. PKP Publishing Services offers support for:

As a customer of PKP Publishing Services, you will not only receive direct, personalized support from the PKP Development Team, but will be contributing to the ongoing development of the PKP applications. All funds raised by PKP Publishing Services go directly toward enhancing our free, open source software. For more information, please contact us.

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

After upgrading to OJS 2.2 I notice the theme system was improved (thanks for it!!) and maybe now is the right moment to upgrade my liquid layout to something stable instead of some template and css hacks: http://psicologiasocial.uab.es/athenea/

So the question is: Is there is any liquid theme example?

If not... is "uncommon" a good theme to start my own?Any tip to overwrite CSS widths and floats in a nice way instead of doing it at "uncommon.css" equivalent?

Regarding the site style: my recommendation would be to replicate the theme structure you see in plugins/themes/uncommon (doesn't have to be uncommon -- you can choose any of those): rename all instances of 'uncommon' to eg. 'liquid' (for example, change UncommonThemePlugin.inc.php to LiquidThemePlugin.inc.php), and move your current stylesheet over. You will most likely have a bunch of fixes to do, especially for the sidebar thanks to the new Blocks system OJS uses. But for future maintenance and compatibility, this would be the easiest way to go.

Regarding the template changes: You'll have to handle the template changes you've made (for example the font-size buttons on the topmost navbar, and associated javascript) a little differently. We've added a block structure to OJS so that new blocks are fairly easy to add; but at the moment this is only available for the sidebar(s). I'd suggest porting your changes over to 2.2's header.tpl and footer.tpl, and anywhere else you've made changes, but ensure that you document your changes for future upgrades etc., and in case we implement the block structure for headers and footers, etc.

FYI, we have a developer just beginning work on a liquid layout. If possible, we'll include it in the next release of OJS. If you're able to come up with one of your own, particularly one that works with one-, two-, and three-column layouts (as configured in Setup page 5), please consider contributing it back to us.

James, thanks a lot to take time to test and thanks again to test it with my magazine original style.I fast checked it and something is not working, but I will be back with feedback tomorrow morning (now here is 23:15 GTM+2).Any case, with our old style we were losing 1/5 of the screen with the logo... so I will try to convince my fellows to renew it all.

Back to the issue: Overwriting CSS on a new theme plugin works quite fine... but the main problem I found is how to deal with a dynamic layout.

I mean, you can easily create a liquid layout if you know how many columns you will have in your magazine, but it's difficult to deal with "%" widths when you don't know if you will have 1, 2 o 3 column layout because as far as I found, I couldn't apply different widths on a plugin-theme to JUST overwrite the appropiate right/left/bothSidebar.css.

I didn't know if I explained myself. My English is really bad.

Any case, for a 3 column layout, this is what I did (reproducing and extending "uncommon" theme):

class AtheneaThemePlugin extends ThemePlugin { /** * Get the name of this plugin. The name must be unique within * its category. * @return String name of plugin */ function getName() { return 'AtheneaThemePlugin'; }

As you can see, at /article/view and /editor/submissions, extra CSS are loaded, letting you play with themes in a very flexible way.

As far as I'm not an OJS developer and I don't know it's API so I'm quite sure there are a couple of ways to do it more elegant, scalable, compatible... so please, let me know if something need/could/should/must be changed.

I'm unsure about this but I think there is no gallery of themes for OJS, and no liquid themes available yet.

After upgrading to OJS 2.2 I notice the theme system was improved (thanks for it!!) and maybe now is the right moment to upgrade my liquid layout to something stable instead of some template and css hacks: http://psicologiasocial.uab.es/athenea/

m.

How did you make the left sidebar solid black with pictures and links???

FYI, I'm gathering requirements for some theme work for the forthcoming OJS 3.0 release. If you're interested in contributing, or want to follow the discussion, please let us know or CC yourself to the following bug entry: