?

Log in

No account? Create an account
I know it's wonky and I don't care [entries|archive|friends|userinfo]
Kake

[ website | My Website ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Links
[Links:| Randomness Guide to London | Open Guide to Cambridge | Snake Soup | KakeFlickr ]

Wanted — someone to do some web stuff. [May. 18th, 2008|05:14 pm]
Kake
[Tags|]

The OpenGuides website needs an overhaul, and I've been blocking on it for so long that I decided it was time to try and throw some money at the problem. Not a lot of money, because it's coming out of my pocket; I was thinking of about £50, so obviously we need someone who'll do it at mates' rates rather than market rates.

The problem with the current site is that it's too hard to update (as you can see from the date of the "Latest project news"...) It's overcomplicated, for one thing, and it assumes that it lives at the server root, so it's a pain in the ass to check out, modify, and test. What we'd like is for someone to rewrite it using nothing other than HTML and SSI; no Perl, no PHP, etc.

Other requirements:

  • No duplication anywhere; menus, footer, navbar, etc should be defined exactly once and then included with SSI where required.
  • It should always be possible to check the site out of svn and amend and test it without it necessarily being at the document root.
  • Any design/appearance stuff should be done with CSS, and the CSS classes should be compatible with those used by OpenGuides itself so when we start shipping a default CSS file with the OpenGuides distribution we can have a consistent look with the OpenGuides website.

The svn repo for the current site is at http://dev.openguides.org/browser/website.

Note: I'm not looking for someone to work on the OpenGuides application (well, I'm always looking for new OpenGuides developers, but that's not what this post is about). I'm looking for someone to overhaul the website at http://openguides.org/ which describes what OpenGuides is about, links to the various Guides, and has project news etc.

Anyone interested?

LinkReply

Comments:
[User Picture]From: caramel_betty
2008-05-19 03:14 pm (UTC)
I wasn't 100% sure if nou was referencing the fact that you have to be careful when using relative paths within the SSI.

e.g. SSI header lives in /includes/header.inc, and you want to include a logo from /images/logo.png, so you include a bit of code that says <img src="../images/logo.png">. This would work fine for /index.htm and /guides/faq.htm, but wouldn't when it was included for /news/archive/2006.htm

I may have misunderstood and/or be on crack. Your country may be at risk if you rely on this information.
(Reply) (Parent) (Thread)
[User Picture]From: nou
2008-05-19 03:28 pm (UTC)
Yes, I think the problem was something along these lines.
(Reply) (Parent) (Thread)
[User Picture]From: therealdrhyde
2008-05-19 09:02 pm (UTC)
Would a solution that involved playing evil games with <!--#exec cmd="..." --> be acceptable?
(Reply) (Parent) (Thread)
[User Picture]From: nou
2008-05-20 10:26 am (UTC)
I think Dom (who'll be hosting the site) would consider SSI exec to be a security hole.
(Reply) (Parent) (Thread)
From: mooism
2008-05-31 12:24 am (UTC)
Would a solution that involved running a perl script (or even a shell script) after doing a svn export be acceptable? i.e. is it ok to run code if it’s not in response to a web request?
(Reply) (Parent) (Thread)
[User Picture]From: nou
2008-05-31 03:00 pm (UTC)
If that's the least complicated solution that would work then yes, that's fine. katstevens has the job now though!
(Reply) (Parent) (Thread)