Yes, that's right, I recall it now. I'll move the front-end work over and pick up where we left off there. Sorry for my confusion.


---- On Sun, 01 Apr 2018 03:55:21 -0400 Erik Huelsmann <ehuels@gmail.com> wrote ----

Hi Cheryl, Mark,

On Sun, Apr 1, 2018 at 9:38 AM, Mark Evenson <evenson@panix.com> wrote:

Indeed for me it is a higher priority to remove the Ruby dependency and be able to generate the site from Lisp than it is to have a new site.

--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.


> On Apr 1, 2018, at 01:08, Cheryl Yang <lisp@cheryllium.com> wrote:
>
> Hello everyone, long time no talk!
>
> I hope everyone has been well. I've had... a hectic time of it but I'm settling down finally.
>
> I should apologize for how MIA and hard-to-reach I have been.
> Hopefully now that things are more stable in my personal life, I can give more time to CL and other projects.
>
> As a start, I've written a basic design update for Common-Lisp.net. You can view and comment on the code for it here: https://gitlab.common-lisp.net/clo/site/merge_requests/1
>
> This features actual mobile responsiveness (yes, the last design had an embarrassing mistake, I know!) and removes the mtime dependency that was preventing us from upgrading Ruby on CLnet's servers. I think we're still on a very old Ruby version, hopefully this will allow us to upgrade it, or at least remove one more barrier.
>
> Please take your time to review it at your leisure; I know I'm sort of surprising everyone with this.
> I've attached a few screenshots so you can see what it looks like at a glance.
>
> Thank you,
> - C. Yang

I thought the plan was to port the current site over to a non-Ruby version in https://gitlab.common-lisp.net/clo/cl-site and then change that one?

It would be considerably easier for the operators to get rid of the Ruby dependency.