So where to go from here? By integrating it into a Drupal setup do you
mean only the 'frontpage' or areas, too?
Personally, I don't think a CMS would be needed if only the former
would be dealt with, as it would be a really small-scale project.
BTW, I noticed the #Footer positioning issue and it's fixed on my end.
On May 16, 5:37 am, Diego Iastrubni <
diegoi...@gmail.com> wrote:
> As a proof of concept, I ported that mockup to a Drupal theme. It's a very
> early draft, but it shows that this is possible.
>
> If this project wants to .. "not die" and someone is willing to maintain the
> web site, a CMS is a must, and IMHO, there are worst alternatives then
> Drupal. There is a few hours of work on the theme to be really usable, but
> IMHO this is not impossible to use it even now.
>
> On the left of this screen shot you will see the original HTML and on the
> right, the "drupalified" version I am talking about.
>
> On Mon, May 10, 2010 at 3:50 AM, Adrian <
the.ronin.s...@gmail.com> wrote:
> > I was in brief contact with icefox about this earlier this year, but
> > nothing ever really shot off. Anyway, I've noticed that, although the
> > domain
arora-browser.org is apparently registered, there is no design
> > for an official Arora site, so I figured I would volunteer my 'skills'
> > as a web developer.
>
> > Here's a "working mockup" of sorts that I've come up:
>
> >
http://docs.google.com/leaf?id=0B61iFLEEpyNDZjBhYzMzMzEtYzJjNy00MzM3L...
>
>
>
> arora-page1.png
> 394KViewDownload